- 最新
- 最多得票
- 最多評論
Q. After establishing DX connections to the Transit Gateway via DX Gateway, do I need to manually add individual routes in the VPC routing table for my on-premises CIDR (IP address range) via the Transit Gateway?
Unlike VGW, you can not propagate the TGW routes into VPC route tables so you need to manually add static routes for on-premises prefixes in VPC subnet route tables pointing towards TGW
Q. Can I assume that the TGW attachment of subnets will automatically handle the routing of traffic from my on-premises data center to the AWS environment through the Direct Connect connections?
See the below statement from the documentation, you can simply propagate the Direct Connect Gateway attachment into a TGW route table and all the routes learned via DX (BGP) will be installed in the TGW route table in which you propagate the DXGW attachment:
When dynamic routing is used with a VPN attachment or a Direct Connect gateway attachment, you can propagate the routes learned from the on-premises router through BGP to any of the transit gateway route tables.
- You would have to manually add a route in your subnet route table (VPC side) to route on-prem traffic to the transit gateway.
- Yes, assuming that you have advertised on-prem prefixes to AWS via Direct Connect (Transit VIF).
In addition to that, you would have to advertise AWS prefixes to on-prem and that can be done via the allowed prefixes tab in DXGW, refer to below for more info.
Thank you Matt
相關內容
- 已提問 10 個月前
- 已提問 3 個月前
Thanks Tushar