- 新しい順
- 投票が多い順
- コメントが多い順
For the purposes of this answer I've assumed you're running a VPC-attached Virtual Private Gateway.
The documentation is correct - you can't specific a metric as the tunnel selection is within the VPN service and therefore either tunnel could be used.
Another option is to use Transit Gateway; that allows for both tunnels on the same VPN connection to be used simultaneously (using ECMP) or for you to configure two different tunnels and advertise different routes and metrics for the tunnels using BGP. It is a more complex setup but it does give you greater flexibility.
Agree with what Brettski replied, that TGW gives your customer more flexibility and control. However, if static routing is the only option, your customer won't be able to select one tunnel over another.
I challenge you to dive a bit deeper into the reasons why:
- BGP isn't an option
- there is the desire to privilege one tunnel over another.
関連するコンテンツ
- AWS公式更新しました 1年前
Hello @brettski, thank you very much for your anwer.
Our customer doesn't want to use BGP, that's why we're using static routing.
If we used a Transit Gateway, would we have an option to set the metric per tunnel and avoid ECMP (because the customer wants priorities, not equal cost paths) ?