Direct Connect + VPN + TGW with DX/VPN failover
0
Two of my customers want to use DX (with VPN) connected to a TGW with an additional VPN failover. They want to avoid routing traffic over that failover link unless the primary DX isn’t routing traffic.
All VPN connections seem to default to ECMP if you enable ECMP on the TGW, meaning all traffic is split across all VPN links all the time.
Could you do BGP route manipulation on the on-prem side to achieve this? A combination of advertising a lower-cost route for AWS->on-prem traffic, and AS path prepending for on-prem->AWS?
Sprache
English
gefragt vor 4 Jahren725 Aufrufe
1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
So you have multiple IPSec VPN terminating on the same TGW and want to prefer one over the other? Is that correct?
You can control this from the customer side (CGW)
- AWS->On-Prem: Use AS-Prepend or MED to control which path to take
- On-Prem->AWS: Use LOCAL_PREF to control which path to take
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 10 Monaten- AWS OFFICIALAktualisiert vor 10 Monaten
- Wie verbinde ich verschiedene Zweigstellen mithilfe von AWS Site-to-Site VPN und AWS Direct Connect?AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren