AWS vpc documentation change
Summary
Clarified conditions for default route table creation and updated backup route explanation wording
Security assessment
Changes clarify operational behavior of route tables and routing preferences, but contain no security-specific context or vulnerability references
Diff
diff --git a/vpc/latest/tgw/how-transit-gateways-work.md b/vpc/latest/tgw/how-transit-gateways-work.md index da38cdb31..ae0ba3724 100644 --- a//vpc/latest/tgw/how-transit-gateways-work.md +++ b//vpc/latest/tgw/how-transit-gateways-work.md @@ -122 +122 @@ For transit gateway peering attachments, only static routes are supported. -Your transit gateway automatically comes with a default route table. By default, this route table is the default association route table and the default propagation route table. Alternatively, if you disable route propagation and route table association, AWS does not create a default route table for the transit gateway. +Your transit gateway automatically comes with a default route table. By default, this route table is the default association route table and the default propagation route table. If you disable both route propagation and route table association, AWS does not create a default route table for the transit gateway. However, if either route propagation or route table association is enabled, AWS then creates a default route table. @@ -204 +204 @@ Some attachments support route advertisement over BGP. For routes with the same -AWS Transit Gateway only shows a preferred route. A backup route will only appear in the Transit Gateway route table if that route is no longer advertised — for example, if you are advertising the same routes over the Direct Connect gateway and over Site-to-Site VPN. AWS Transit Gateway will only show the routes received from the Direct Connect gateway route, which is the preferred route. The Site-to-Site VPN, which is the backup route, will only display when the Direct Connect gateway is no longer advertised. +AWS Transit Gateway only shows a preferred route. A backup route will only appear in the transit gateway route table if the previously active route is no longer advertised — for example, if you are advertising the same routes over the Direct Connect gateway and over Site-to-Site VPN. AWS Transit Gateway will only show the routes received from the Direct Connect gateway route, which is the preferred route. The Site-to-Site VPN, which is the backup route, will only display when the Direct Connect gateway is no longer advertised.