AWS vpc documentation change
Summary
Added documentation specifying that VPN Concentrator attachments exclusively support BGP routing
Security assessment
The change clarifies routing protocol limitations for a specific attachment type but contains no references to security vulnerabilities, mitigations, or security features. It's a functional clarification without security implications.
Diff
diff --git a/vpc/latest/tgw/tgw-transit-gateways.md b/vpc/latest/tgw/tgw-transit-gateways.md index 99d647670..b53e9f7f8 100644 --- a//vpc/latest/tgw/tgw-transit-gateways.md +++ b//vpc/latest/tgw/tgw-transit-gateways.md @@ -15 +15 @@ You can create additional route tables inside the transit gateway, and change th -Transit gateways support dynamic and static routing between attached VPCs and VPN connections. You can enable or disable route propagation for each attachment. Transit gateway peering attachments support static routing only. You can point routes in transit gateway route tables to the peering attachment for routing traffic between the peered transit gateways. +Transit gateways support dynamic and static routing between attached VPCs and VPN connections. You can enable or disable route propagation for each attachment. VPN Concentrator attachments support BGP (dynamic) routing only. Transit gateway peering attachments support static routing only. You can point routes in transit gateway route tables to the peering attachment for routing traffic between the peered transit gateways.