Direct connect Private VIF

Question

I have 2 DX connections us-east1 and 2
THE VPC I'm trying to connect in another aws account is in us-east 2 region
Do I have to select only DX connection in us east 2 region when creating a VIF ?

AWS-User-0357409 · Accepted Answer

Hi Ali,

You shouldn't need to use the DX in us-east-2 specifically.  With two Direct Connects, they would connect to your Direct Connect Gateway, then the underlying IP routing would handle the access between your on-premise networks and the target VPC.  You would be able to connect to multiple VPCs with this architecture.  Below is a diagram for reference.

Hope this helps!
![DX diagram](/media/postImages/original/IMQH4dnRVpQge5F5kU9hNluQ)

Tushar_J · Answer

Also take a look at this Hybrid Connectivity Whitepaper: https://docs.aws.amazon.com/whitepapers/latest/hybrid-connectivity/aws-dx-dxgw-with-vgw-multi-regions-and-aws-public-peering.html

Below are some of the examples of how the topology would look like. A Direct Connect gateway is a globally available resource. You can create the Direct Connect gateway in any Region and access it from all other Regions.

With redundancy the connectivity using DXGW would look like this:

![Enter image description here](/media/postImages/original/IMCjCqKc_KSLOzYf6K-6VWQg)

If you are using TGW it would look like this:

![Enter image description here](/media/postImages/original/IMHFYAoJXoR2WjIXqQmF5-eg)

Direct connect Private VIF

Relevant content