- 最新
- 投票最多
- 评论最多
Hi there - it is not possible to route between VPCs using a private vif. My advice would be to use Transit Gateway https://docs.aws.amazon.com/vpc/latest/tgw/what-is-transit-gateway.html. This is a routing device that can connect both direct connects and VPCs to each other. The other option as bwhaley pointed out would be to peer the VPCs to each other https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html
Thank you very much for the response AJ. Point noted. Do you have any suggestion to the link I sent on page 22 "AWS Direct Connect" section? https://d1.awsstatic.com/whitepapers/aws-amazon-vpc-connectivity-options.pdf
What it is saying is that a single dedicated direct connect can be split into multiple logical connections knows as virtual interfaces (VIFs). In the setup listed on page 22 those VPCs would be able to communicate back to on-prem, but not to each other. That whitepaper looks quite old - I would use this one instead https://docs.aws.amazon.com/whitepapers/latest/aws-vpc-connectivity-options/network-to-amazon-vpc-connectivity-options.html
Thank you!
相关内容
AWS 官方已更新 7 个月前- AWS 官方已更新 2 年前
- AWS 官方已更新 3 年前
I do not believe you can route traffic from one VPC to another through the Direct Connect - it's not transitive. You could instead peer the VPCs and use VPC route tables for inter-VPC communication.