Home icon

Introducing AWS Client VPN native AWS Transit Gateway attachment

Networking & Content Delivery Blog



This article announces AWS Client VPN native attachment to AWS Transit Gateway, enabling centralized remote access to multiple VPCs and on-premises networks without requiring a dedicated hosting VPC.

  • Client VPN endpoints now attach directly to Transit Gateway as a central hub
  • Eliminates Source Network Address Translation (SNAT), preserving original client IP addresses
  • Simplifies architecture by removing need for dedicated VPC and intermediate connectivity steps
  • Supports multi-account deployments with Transit Gateway and Client VPN in different accounts
  • Enables centralized security inspection through AWS Network Firewall with client IP-based policies
  • Provides enhanced visibility for security monitoring, compliance auditing, and troubleshooting
  • Step-by-step configuration includes endpoint creation, authorization rules, Transit Gateway routing setup
  • Migration path available from existing VPC-based Client VPN deployments to Transit Gateway model

This native Transit Gateway attachment simplifies remote access architecture while preserving client identity for security and compliance requirements in multi-VPC and hybrid environments.



Go to article

The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.

Related articles

Apr 24
2026
AWS Client VPN now supports native AWS Transit Gateway integration
May 28
2026
Why and how to migrate to a Transit Gateway-attached AWS Network Firewall
Jun 16
2025
AWS Network Firewall now supports AWS Transit Gateway native integration
Apr 28
2025
AWS Client VPN now supports Client Routes Enforcement

The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.