AWS Client VPN over Direct Connect

Question

IHAC who is looking to implement below architecture -

Customer Office ---(Connected via their own network)———> Customer Data Center ——(Connected via Direct Connect)——> AWS

Customer have some applications in their office which use legacy protocols. They want to connect these applications securely with AWS and would like to leverage AWS Client VPN for end-to-end encryption.

Is this a right architecture pattern or customer should consider other solution?

Answer

Hello.

There is a way to encrypt DirectConnect communication using Site to Site VPN.  
With this setting, no settings are required on the client application side.  
https://aws.amazon.com/jp/blogs/networking-and-content-delivery/introducing-aws-site-to-site-vpn-private-ip-vpns/  
https://docs.aws.amazon.com/whitepapers/latest/aws-vpc-connectivity-options/aws-direct-connect-site-to-site-vpn.html  
> This solution combines the benefits of the end-to-end secure IPsec connection with low latency and increased bandwidth of the AWS Direct Connect to provide a more consistent network experience than internet-based VPN connections. A BGP connection session is established between AWS Direct Connect and your router on the public VIF. Another BGP session or a static route will be established between the virtual private gateway and your router on the IPsec VPN tunnels.

AWS Client VPN over Direct Connect

相關內容