https://wirez.top/tags/attachment/Recent content in Attachment on WirezHugoenFri, 01 May 2026 11:44:06 +0000https://wirez.top/posts/native-attachment-fixes-aws-client-vpn-snat-gaps/Fri, 01 May 2026 11:44:06 +0000https://wirez.top/posts/native-attachment-fixes-aws-client-vpn-snat-gaps/<meta charset="utf-8"> <!-- wp:paragraph {"className":"std-text"} --> <!-- /wp:paragraph --> <!-- wp:paragraph {"className":"std-text"} --> <p class="std-text">The April 24, 2026 announcement eliminates the dedicated hosting VPC previously required for <strong>centralized remote access</strong>. This update fundamentally shifts <strong>AWS Client VPN</strong> from a complex, multi-hop topology to a streamlined <strong>native attachment</strong> model directly on <strong>Transit Gateway</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.</p>https://wirez.top/posts/native-transit-gateway-attachment-fixes-snat-issues/Fri, 01 May 2026 10:45:23 +0000https://wirez.top/posts/native-transit-gateway-attachment-fixes-snat-issues/<meta charset="utf-8"> <!-- wp:paragraph {"className":"std-text"} --> <!-- /wp:paragraph --> <!-- wp:paragraph {"className":"std-text"} --> <p class="std-text">AWS eliminates SNAT for <a href="https://en.wikipedia.org/wiki/IPv4" target="_blank" rel="noopener noreferrer">IPv4</a> connections, preserving original client IP addresses by attaching Client VPN directly to Transit Gateway. This architectural shift replaces the cumbersome VPC association model, which previously forced organizations to deploy dedicated hosting VPCs and obscure user identity through Source Network Address Translation. By enabling <strong>direct attachment</strong>, AWS allows enterprises to centralize remote access without intermediate routing hops, fundamentally simplifying how hybrid networks handle traffic flow.</p>