View a markdown version of this page

Hybrid Connectivity to AWS Transit Gateway with AWS Direct Connect - Hybrid Connectivity to AWS Transit Gateway

Hybrid Connectivity to AWS Transit Gateway with AWS Direct Connect

Publication date: August 17, 2022 (Diagram history)

You can use a Transit VIF and a Direct Connect gateway to connect your on-premises environments to AWS. With this, you can benefit from the connectivity to multiple VPCs without the need of several Direct Connect connections. It is recommended to use a second connection (Direct Connect or VPN) for high availability.

Hybrid connectivity with AWS Direct Connect architecture

Architecture diagram showing hybrid connectivity to AWS Transit Gateway using AWS Direct Connect with a Transit VIF and Direct Connect gateway.

The following steps describe the on-premises to AWS traffic flow:

  1. Traffic from the corporate data center destined to the spoke VPC A is forwarded to AWS Transit Gateway through the AWS Direct Connect (DX) link. The Transit Gateway is connected to the Direct Connect link by using a Transit virtual interface (VIF) and a Direct Connect Gateway.

  2. As per the Transit Gateway on-premises route table, the traffic is forwarded to the spoke VPC A attachment.

  3. The Transit Gateway ENI of the spoke VPC A forwards the traffic to the destination.

The following steps describe the AWS to on-premises traffic flow:

  1. Traffic initiated from an Amazon Elastic Compute Cloud instance in the spoke VPC B and destined to the corporate data center is routed to the Transit Gateway ENI as per the spoke VPC B route table.

  2. Traffic is forwarded to the AWS Transit Gateway. As per the spoke VPC route table, the traffic is routed to the office branch through the AWS Direct Connect Gateway attachment.

  3. The traffic is routed to the destination through the AWS Direct Connect link.

For more information about how to create an AWS Direct Connect connection, see Create a Direct Connect dedicated connection.

Further reading

For additional information, see the following resources:

Diagram history

To be notified about updates to this reference architecture diagram, subscribe to the RSS feed.

ChangeDescriptionDate

Initial publication

Reference architecture diagram first published.

August 17, 2022

Initial publication

Reference architecture diagram first published.

August 17, 2022

Initial publication

Reference architecture diagram first published.

August 17, 2022

Initial publication

Reference architecture diagram first published.

August 17, 2022

Initial publication

Reference architecture diagram first published.

August 17, 2022

Initial publication

Reference architecture diagram first published.

August 17, 2022

Initial publication

Reference architecture diagram first published.

August 17, 2022

Initial publication

Reference architecture diagram first published.

August 17, 2022

Note

To subscribe to RSS updates, you must have an RSS plugin enabled for the browser you are using.