1 Answer
2
Accepted Answer
Hi!
Let me see if I follow what you want to do: you have to Direct Connect links in two different Direct Connect locations. And you want the two Private VIFs connected to the same Direct Connect gateway, which is associated to your VPC(s). Is that right?
If it is, you can do that, check this section of the Hybrid Connectivity AWS Whitepaper: https://docs.aws.amazon.com/whitepapers/latest/hybrid-connectivity/aws-dx-dxgw-with-aws-transit-gateway-multi-regions-and-aws-public-peering.html. The example there shows Transit VIFs as it is connecting to a Transit Gateway in the Regions, but you can also do it with Private VIFs.
answered 7 months ago
Relevant questions
Direct Connect Failover with two Virtual Interfaces (VIFs)
Accepted Answerasked 2 years agoIs it better to have a single Direct Connect Gateway or multiple Direct Connect Gateways?
Accepted AnswerVPN over Direct Connect with Direct Connect Gateway
Accepted Answerasked 2 years agoHow to have multiple VPCs in different AWS accounts use the same physical AWS Direct Connect circuit.
Accepted Answerasked 4 years agoConnect remote sites using VPN to access on-prem via existing Direct Connect?
Accepted Answerasked 6 months agoAWS Direct Connect traffic from on-prem DC to remote AWS Region
Accepted Answerasked 3 years agoDirect Connect Gateway pricing?
Accepted Answerasked 5 years agoSingle DC-GW connected to multiple direct-connect links
Accepted Answerasked 7 months agoTransit Gateway to Direct Connect Gateway to Transit Gateway
Accepted Answerasked 3 years agoPrivate link access over direct connect - Direct Connect Gateway
Accepted Answerasked 4 years ago
Thanks for such a prompt response. yes, you got it right but it has one additional condition as direct-connect links will be from two different direct-connect locations associated with two different AWS regions. Please help me to fulfil this requirement too. Thanks,
You can connect VIFs from DX links in locations that are associated to different Regions into the same Direct Connect gateway. The DXGW is the representation of the AWS backbone, so regardless the Region associated, if you have the DXGW it will take the best path possible to any Region you associate to the DXGW (except China ones).
The only thing you have to be careful in configuring is the active/passive configuration - the DXGW will prefer the DX location associated with the AWS Region the traffic is coming from. This can be overridden through BGP community values - check this blog post for more information: https://aws.amazon.com/blogs/networking-and-content-delivery/creating-active-passive-bgp-connections-over-aws-direct-connect/