AWS DX – DXGW with VGW, Single Region - Hybrid Connectivity

AWS DX – DXGW with VGW, Single Region

This model is constructed of:

  • Single AWS Region.

  • Dual AWS Direct Connect Connections to independent DX locations.

  • AWS DXGW directly attached to the VPCs using VGW.

  • Optional usage of AWS Transit Gateway for Inter-VPC communication.

Figure 7 – AWS DX – DXGW with VGW, Single AWS Region.

Connectivity model attributes:

  • Provide the ability to connect to VPCs and/or DX connection(s) in other Regions in the future.

  • Offers automated failover, with dynamic routing (BGP).

  • With AWS Transit Gateway connected to VPCs, Full mesh connectivity or partial mesh connectivity can be achieved between the VPCs (with AWS Transit Gateway you can control the desired communication model among the VPCs, for more information refer to How transit gateways work).

Scale considerations:

  • 100 routes per Private VIF.

  • Up to 10 VPCs can be connect per DXGW over s single BGP session, if more VPCs need to be connected, additional DXGWs can be added to facilitate the connectivity at scale.

  • Additional AWS Direct Connect can be added as desired.

  • Refer to the AWS Direct Connect quotas for more information about the scale limits, such number of supported prefixes, number of VIFs per DX connection type (Dedicated, hosted).

Other considerations:

  • Does not incur AWS Transit Gateway related processing cost for data transfer between AWS and on-premises networks.

  • Security groups of a remote VPC cannot be referenced over AWS Transit Gateway (need VPC peering).

  • VPC peering can be used instead of AWS Transit Gateway to facilitate the communication between the VPCs, however, this will add operational complexity to build and manage large number VPC point-to-point peering at scale.

  • If Inter-VPC communication is not required, neither AWS Transit Gateway nor VPC peering is required in this connectivity model.