SD-WAN Devices Integration with AWS Transit Gateway and AWS Direct Connect
Publication date: December 28, 2024 (Diagram history)
This architecture shows how to use AWS Transit Gateway Connect attachments and AWS Direct Connect to extend and segment your SD-WAN traffic to AWS without adding extra infrastructure. Each Transit Gateway Connect Peer can have its own Transit Gateway Route Table and BGP peer to extend an on-premises VRF if required.
SD-WAN devices integration with AWS Transit Gateway and AWS Direct Connect architecture
The following steps describe the AWS to on-premises traffic flow:
-
Traffic initiated from an instance in the Spoke Amazon VPC A and destined to the corporate data center SD-WAN device is routed to the TGW ENI as per the Spoke Amazon VPC A Route Table.
-
Traffic is forwarded to the Transit Gateway. As per the Spoke VPC route table, the traffic is routed to the corporate data center through the Transit Gateway Connect attachment.
-
The Transit Gateway Connect attachment uses the Direct Connect connection as transport, and connects the Transit Gateway to the corporate data center SD-WAN device using GRE tunneling and BGP.
The following steps describe the on-premises to AWS traffic flow:
-
Traffic from the corporate data center SD-WAN device destined to the Spoke VPC B is forwarded to the Transit Gateway through the GRE tunnel of the Transit Gateway attachment, over the Direct Connect link.
-
As per the Transit Gateway Connect route table, the traffic is forwarded to the Spoke VPC B attachment.
-
The TGW ENI of the Spoke VPC B forwards the traffic to the destination.
For more information about how to integrate your on-premises SD-WAN devices using AWS Transit Gateway and AWS Direct Connect, see Integrate SD-WAN devices with AWS Transit Gateway and AWS Direct Connect
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.
| Change | Description | Date |
|---|---|---|
Reference architecture diagram first published. | December 28, 2024 | |
Reference architecture diagram first published. | December 28, 2024 | |
Reference architecture diagram first published. | December 28, 2024 | |
Reference architecture diagram first published. | December 28, 2024 | |
Reference architecture diagram first published. | December 28, 2024 | |
Initial publication | Reference architecture diagram first published. | December 28, 2024 |
Reference architecture diagram first published. | December 28, 2024 |
Note
To subscribe to RSS updates, you must have an RSS plugin enabled for the browser you are using.
