Site-to-Site VPN gateway with transit gateway

0

We have a Site-to-Site VPN (VPN Gateway) setup in a MAIN account in AWS. All connectivity in the VPC for that MAIN account and on-prem work fine. (both ways) The MAIN account using a shared TGW to the SECONDARY account. Connectivity between the MAIN and SECONDARY is fine (both ways) For the SECONDARY account to traverse through TGW to the MAIN account and then the VPN (On-prem), what routes would be needed? I have tried many routes for the TGW and the Route tables themselves, none work.

Will this even work? Or does the Site-to-Site VPN need to be associated to the TGW and not the MAIN VPC?

Daniel
已提问 9 个月前326 查看次数
1 回答
1
已接受的回答

Transitive routing is not supported with VPC's

As you rightly speculated. The S2S VPN Has to terminate on the Transit gateway.

You cant have a S2S VPN terminate in the VPC Directly and they route from Secondary account via transit gateway to main account and then via the Local Virtual Private Gateway in the Main VPC.

https://docs.aws.amazon.com/whitepapers/latest/aws-vpc-connectivity-options/aws-transit-gateway-vpn.html

profile picture
专家
已回答 9 个月前
profile picture
专家
已审核 9 个月前
profile pictureAWS
专家
已审核 9 个月前
  • Figured. Thank you

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则