<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Transit-Gateway on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/transit-gateway/</link><description>Recent content in Transit-Gateway on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 24 Oct 2026 14:11:23 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/transit-gateway/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS Transit Gateway and Cloud WAN add managed 1:1 NAT for overlapping CIDRs</title><link>https://curadevops.metacog.co.kr/insights/2026-10-24-aws-transit-gateway-and-aws-cloud-wan-now-support-1-1-nat/</link><pubDate>Sat, 24 Oct 2026 14:11:23 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-24-aws-transit-gateway-and-aws-cloud-wan-now-support-1-1-nat/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> This GA capability eliminates the need for a NAT appliance or IP renumbering when connecting networks with overlapping CIDRs — directly relevant if the org has pending M&amp;amp;A integration, partner VPN, or multicloud connectivity work blocked by address conflicts. Evaluate adding to the network-connectivity pattern for such scenarios this quarter.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Managed 1:1 NAT on Transit Gateway removes the appliance cost and renumbering complexity historically incurred during M&amp;amp;A network integration; worth noting as an option when assessing future acquisition or partner-connectivity scope.&lt;/li>
&lt;/ul></description></item></channel></rss>