1 個回答
- 最新
- 最多得票
- 最多評論
2
VPC Peering is not transitive. Your best option is to use a Transit Gateway.
相關內容
- 已提問 10 個月前
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
VPC Peering is not transitive. Your best option is to use a Transit Gateway.
I've spent some time with this but struggling to make it work. What I've done is:
Created TransitGateway in Legacy
Shared TransitGateway via RAM
Created association for legacy VPC
Created association for New VPC
Added TransitGateway route 192.168.1.0/24 -> legacy VPC attachment
Set Legacy VPC Routes: 192.168.1.0/24 -> 10.0.0.200 EIC 10.50.0.0/16 -> TransitGateway
Set New VPC routes 10.0.0.0/8 -> TransitGateway 10.50.0.0/16 -> local 192.168.1.0/24 -> TransitGateway
Pings from 10.50.0.1 to 192.168.1.10 time out. Any further help would be greatly appreciated!