1 Answer
- Newest
- Most votes
- Most comments
3
Hello,
1- yes you need to create IPSec connection to the TGW and to each VGW.
2- When you create a VPN attachment on a Transit Gateway, you get two public IP addresses for VPN endpoints at the AWS side. These public IPs are reachable over the public VIF. So you can establish the VPN connection directly over the public VIF without the need for the Transit VIF in this scenario. The same applies to the VGW VPN Connection. Please refer to point 4 in the below documentation https://docs.aws.amazon.com/whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/direct-connect.html
Relevant content
- asked 2 years ago
- asked 3 years ago

Thanks for Question -1
For quetion-2, i understand the VPN establishment process but Can you elaborate more on routing part
For example, i am advertising 10.0.0.0/24 from Transit VIF through TGW association to DXGW and on-prem CISCO router is advertising 192.168.10.0/24 towards the transit VIF. Once i established IPSec, what would happened to those advertisement from TGW/DXGW and on-prem CISCO router ? and how to use IPSec tunnel path instead of transit VIF path ?
Do i need to disable or delete existing Transit VIF or Private VIF ?
As you are planning to leverage the IPSec connections to both the TGW and the VGW over the public VIF, the BGP sessions running on top of the IPSec connections will exchange the routes between TGW/VGW and on-prem. You don’t need the transit VIF or Private VIF for your scenario