AWS Direct Connect
User Guide

The AWS Documentation website is getting a new look!
Try it now and let us know what you think. Switch to the new look >>

You can return to the original look by selecting English in the language selector above.

Accessing a Remote AWS Region

AWS Direct Connect locations in public Regions or AWS GovCloud (US) can access public services in any other public Region (excluding China (Beijing and Ningxia)). In addition, AWS Direct Connect connections in public Regions or AWS GovCloud (US) can be configured to access a VPC in your account in any other public Region (excluding China(Beijing and Ningxia). You can therefore use a single AWS Direct Connect connection to build multi-Region services. All networking traffic remains on the AWS global network backbone, regardless of whether you access public AWS services or a VPC in another Region.

Any data transfer out of a remote Region is billed at the remote Region data transfer rate. For more information about data transfer pricing, see the Pricing section on the AWS Direct Connect detail page.

For more information about the routing policies and supported BGP communities for an AWS Direct Connect connection, see Routing Policies and BGP Communities.

Accessing Public Services in a Remote Region

To access public resources in a remote Region, you must set up a public virtual interface and establish a Border Gateway Protocol (BGP) session. For more information, see AWS Direct Connect Virtual Interfaces.

After you have created a public virtual interface and established a BGP session to it, your router learns the routes of the other public AWS Regions. For more information about prefixes currently advertised by AWS, see AWS IP Address Ranges in the Amazon Web Services General Reference.

Accessing VPCs in a Remote Region

You can create a Direct Connect gateway in any public Region. Use it to connect your AWS Direct Connect connection over a private virtual interface to VPCs in your account that are located in different Regions or to a transit gateway. For more information, see Working with Direct Connect Gateways.

Alternatively, you can create a public virtual interface for your AWS Direct Connect connection and then establish a VPN connection to your VPC in the remote Region. For more information about configuring VPN connectivity to a VPC, see Scenarios for Using Amazon Virtual Private Cloud in the Amazon VPC User Guide.