- Newest
- Most votes
- Most comments
From AWS Doc: When you have multiple virtual interfaces in the same associated Region, you can set the AS_PATH attribute to prioritize which interface AWS uses to route traffic. However, AS_PATH prepending doesn’t work when the Direct Connect connections are in different associated AWS Regions than the VPC. https://docs.aws.amazon.com/directconnect/latest/UserGuide/routing-and-bgp.html#private-routing-policies
However you can use AS-Path as your primary best path selection algorithm firstly by setting equal preference with Local preference BGP communities values e.g. (7200:100) on all the connections(VIFs). Which leads to tie in path selection hence AS-Path can be evaluated as a tie breaker. By also advertising your prefixes with different AS-Path length will influence traffic flow from AWS based on AS-Path.
Hi khanakee, So if I correctly understood this is that if I set the same BGP local preference community across all the VIFs, then I can use AS-Path to influence how routing takes place from AWS side. Is that correct?
The best practice from AWS when it comes to multi-region traffic engineering is to use communities. This article goes into the same scenario you described https://repost.aws/knowledge-center/direct-connect-bgp-communities also look at https://docs.aws.amazon.com/directconnect/latest/UserGuide/routing-and-bgp.html#local-pref-bgp-communities
On the multi region with direct connect usage u need to use :
- Local preference ,
- bgp communities to influence routing
Relevant content
- asked 8 months ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago
Hello Imran, yes that is correct