<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Snat on Wirez</title><link>https://wirez.top/tags/snat/</link><description>Recent content in Snat on Wirez</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 01 May 2026 11:44:06 +0000</lastBuildDate><atom:link href="https://wirez.top/tags/snat/index.xml" rel="self" type="application/rss+xml"/><item><title>Native attachment fixes AWS Client VPN SNAT gaps</title><link>https://wirez.top/posts/native-attachment-fixes-aws-client-vpn-snat-gaps/</link><pubDate>Fri, 01 May 2026 11:44:06 +0000</pubDate><guid>https://wirez.top/posts/native-attachment-fixes-aws-client-vpn-snat-gaps/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">The April 24, 2026 announcement eliminates the dedicated hosting VPC previously required for &lt;strong>centralized remote access&lt;/strong>. This update fundamentally shifts &lt;strong>AWS Client VPN&lt;/strong> from a complex, multi-hop topology to a streamlined &lt;strong>native attachment&lt;/strong> model directly on &lt;strong>Transit Gateway&lt;/strong>. By removing the intermediate VPC layer, organizations can finally discard the operational overhead of managing separate route tables and peering connections that plagued earlier iterations.&lt;/p></description></item></channel></rss>