Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Use VPC peering to share/route virtual private gateway subnet between two VPC

0

Can Virtual Private Gateway subnet in the route table share/route to another VPC through vpc peering?

In VPC A route table, there is a 10.192.1.0 route origin using Virtual Private Gateway from direct connect. Can I use vpc peering to route 10.192.1.0 to VPC B?

Topics
Networking & Content Delivery
Tags
Amazon VPC
Language
English
asked 9 days ago23 views
2 Answers
0

No. That's not supported.

But what you should have in addition to the Direct Connect is a Direct Connect Gateway. You can use the Direct Connect Gateway to connect to multiple VPCs while using the same Direct Connect.

AWS
EXPERT
answered 9 days ago
  • Ryan
    9 days ago

    If under propagated column indicates "Yes" on the 10.192.1.0 route origin using Virtual Private Gateway, also not supported?

  • Brettski-AWS EXPERT
    4 days ago

    Still not supported.

0

That will not work. See the VPC peering limitations section here specifically the 'Edge to edge routing through a gateway or private connection' sub section

If VPC A has an AWS Direct Connect connection to a corporate network, resources in VPC B can't use the AWS Direct Connect connection to communicate with the corporate network.

As Brett mentioned you can use Direct Connect Gateway (no additional cost for using DXGW) and connect to both the VPCs, see the option 2 showed here

For VPC to VPC traffic you can continue to use the peering connection; just note that it is non-transitive.

AWS
EXPERT
answered 9 days ago

Relevant content