AWS DX – DXGW with AWS Transit Gateway, Multi-Regions, and AWS Public Peering - Hybrid Connectivity

AWS DX – DXGW with AWS Transit Gateway, Multi-Regions, and AWS Public Peering

This model is constructed of:

  • Multi AWS Regions.

  • Dual AWS Direct Connect Connections to independent DX locations.

  • Single on-premises data center with dual connections to AWS.

  • AWS DXGW with AWS Transit Gateway.

  • High scale of VPCs per Region.

Figure 9 – AWS DX – DXGW with AWS Transit Gateway, Multi-Regions, and AWS Public VIF

Connectivity model attributes:

  • AWS DX public VIF is used to access AWS public resources such as S3 directly over the AWS DX connections.

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

  • With AWS Transit Gateway connected to VPCs, Full mesh connectivity or partial mesh connectivity can be achieved between the VPCs.

  • Inter-VPC and Inter-Region VPC communication facilitated by AWS Transit Gateway peering.

  • Offers flexible design options to integrate third-party security and SDWAN virtual appliances with AWS Transit Gateway. See: Centralized network security for VPC-to-VPC and on-premises to VPC traffic.

Scale considerations:

  • The number of routes to and from AWS Transit Gateway is limited to the maximum supported number of routes over a Transit VIF (inbound and outbound numbers vary). Refer to the AWS Direct Connect quotas for more information about the scale limits and support number of routes, and VIFs.

  • Scale up to thousands of VPCs per AWS Transit Gateway over a single BGP session to DXGW (assuming the provided performance by the provisioned AWS DX connection(s) is sufficient).

  • Single Transit VIF per AWS DX.

  • Additional AWS DX connection(s) can be added as desired.

Other considerations:

  • Incurs additional AWS Transit Gateway processing cost for data transfer between AWS and on-premises site.

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

  • VPC peering can be use 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 more than three AWS Transit Gateways are required, addition DXGW had to added (refer to the following connectivity mode).