QuestionQ135

Network Design

A company runs its IT infrastructure in an on-premises data center and plans to migrate that infrastructure to the AWS Cloud in phases. A network engineer needs to establish a 10 Gbps AWS Direct Connect dedicated connection between the on-premises data center and VPCs. The company’s network provider requires 3 months to provision the Direct Connect connection.

Meanwhile, the network engineer deploys a temporary AWS Site-to-Site VPN connection that terminates on a virtual private gateway. Despite using a powerful customer gateway device, the engineer finds that the Site-to-Site VPN connection bandwidth is limited to 1.25 Gbps.

What should the network engineer do to increase VPN connection bandwidth before the Direct Connect connection is implemented?

  • A Contact AWS Support to request a bandwidth quota increase for the existing Site-to-Site VPN connection.
  • B Discuss the issue with the hardware vendor. Buy a bigger and more powerful customer gateway device that has faster encryption and decryption capabilities.
  • C Create several additional Site-to-Site VPN connections that terminate on the same virtual gateway. Configure equal-cost multi-path (ECMP) routing to use all the VPN connections simultaneously.
  • D Create a transit gateway. Attach the VPCs to the transit gateway. Create several additional Site-to-Site VPN connections that terminate on the transit gateway. Configure equal-cost multi-path (ECMP) routing to use all the VPN connections simultaneously.
Explanation

Standard AWS Site-to-Site VPN tunnels are limited to up to 1.25 Gbps and this limit is not adjustable. Higher aggregate VPN bandwidth can be achieved by terminating multiple Site-to-Site VPN connections on an AWS Transit Gateway and using dynamic-routing ECMP to distribute traffic across the tunnels. A virtual private gateway does not provide this ECMP aggregation capability.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!