2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Set "AS_PATH prepending" as described in the following document.
https://docs.aws.amazon.com/directconnect/latest/UserGuide/private-transit-vif-example.html
0
It is not possible to do on-premises style PBR (policy based routing) like that with VGW.
How did you conclude the below?
The network latency from hosts in Availability Zone A is best to Direct Connect location 1. The network latency from hosts in Availability Zones B and C is best to Direct Connect location 2.
Thank you for your comment. A simple traceroute shows hop times.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 7 Monaten- AWS OFFICIALAktualisiert vor 2 Jahren
- 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
Sorry this answer is incorrect. This would result in traffic from all 3 Availability Zones using the same VIF. My question explains the Availability Zone A subnet should use VIF 1 and Availability Zone B, C subnets use VIF 2.
In the active/active case, "AS_PATH prepending" must be the same value so that load balancing occurs.
So I found it difficult to route to a specified VIF for a specific subnet only.