1 Answer
- Newest
- Most votes
- Most comments
2
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 2 years ago
Relevant content
- Accepted Answerasked 6 years ago
- Accepted Answer
- Accepted Answerasked 5 years ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year 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/