AWS Client VPN now supports native AWS Transit Gateway integration

Amazon Web Services has launched native integration between AWS Client VPN and AWS Transit Gateway, eliminating the need for intermediate VPCs when providing remote access to multiple virtual private clouds and on-premises networks. The integration addresses previous operational complexity where organizations had to provision and manage additional VPC resources to connect Client VPN across multiple networks, while also resolving source IP visibility issues caused by Source Network Address Translation (SNAT). The new native integration preserves end-user source IP addresses throughout the connection path, enabling IT administrators to create authorization rules based on actual client IPs and trace network traffic back to specific users. This enhancement simplifies security auditing, compliance reporting, and troubleshooting workflows by maintaining connection-level visibility. Transit Gateway flow logs now capture detailed connection information tied to preserved source IPs, providing comprehensive audit trails for security and compliance teams. The integration is available across all AWS regions where Client VPN operates, with no additional charges beyond standard pricing for both services. Organizations can now deploy centralized remote access solutions without the architectural complexity and IP address translation limitations that previously complicated multi-VPC deployments.