Connecting Direct Connect to Transit Gateway - AMS Advanced Onboarding Guide

Connecting Direct Connect to Transit Gateway

You can use your existing Direct Connect connection or create a new Direct Connect connection in one of your existing AWS accounts. The Direct Connect connection should be a dedicated or hosted connection running at 1 Gbps or more.

Note

For information about using a DX with AWS services, see Getting Started at an AWS Direct Connect Location.

If you are using your existing Direct Connect dedicated connection, then it should not have any transit virtual interfaces created on the connection. This is because AWS Direct Connect dedicated connection has a limit of one transit virtual interface per connection. If you are using your existing Direct Connect hosted connection, then it should not have any virtual interfaces created on the connection. This is because private, public, or transit virtual interfaces per AWS Direct Connect hosted connection can only be one.

For more details of Direct Connect Limits, please refer to AWS Direct Connect Limits.

Once the Direct Connect connection is available:

  1. AMS would create a Direct Connect Gateway in the networking account . You would need to provide an Autonomous System Number (ASN ) number for the Direct Connect Gateway and the prefixes that have to be advertised from the Direct Connect Gateway. This ASN will be used as the Amazon side ASN.

  2. You will then create a new Transit VIF and set the Virtual interface owner as the networking account.

  3. AMS would then login to the networking account and accept the connection proposal.

  4. AMS would then associate the transit gateway with the Direct Connect gateway.

  5. AMS will the associate the attachment with the on-prem Transit Gateway routing table.

Note

The Autonomous System Number (ASN) provided for the Direct Connect gateway and the Transit gateway must be different.

To increase the resiliency of your connectivity, we recommend that you attach at least two transit virtual interfaces from different AWS Direct Connect locations, to the Direct Connect gateway. For more information, please refer to the AWS Direct Connect resiliency recommendation.