AWS directconnect documentation change
Summary
Updated terminology capitalization from 'transit gateway' to 'Transit Gateway' throughout the document for consistency
Security assessment
Changes are purely cosmetic terminology updates (capitalization of 'Transit Gateway'). No security vulnerabilities, configurations, or features are mentioned or modified. The content about allowed prefixes and routing behavior remains functionally identical.
Diff
diff --git a/directconnect/latest/UserGuide/allowed-to-prefixes.md b/directconnect/latest/UserGuide/allowed-to-prefixes.md index 3782f447d..8d4a46e11 100644 --- a//directconnect/latest/UserGuide/allowed-to-prefixes.md +++ b//directconnect/latest/UserGuide/allowed-to-prefixes.md @@ -7 +7 @@ -Virtual private gateway associationsTransit gateway associationsExample: Allowed to prefixes in a transit gateway configuration +Virtual private gateway associationsTransit Gateway associationsExample: Allowed to prefixes in a Transit Gateway configuration @@ -11 +11 @@ Virtual private gateway associationsTransit gateway associationsExample: Allowed -Learn how allowed prefixes interact with transit gateways and virtual private gateways. For more information, see [Routing policies and BGP communities](./routing-and-bgp.html). +Learn how allowed prefixes interact with Transit Gateways and virtual private gateways. For more information, see [Routing policies and BGP communities](./routing-and-bgp.html). @@ -34 +34 @@ When you remove or add an allowed prefix, traffic which doesn't use that prefix -## Transit gateway associations +## Transit Gateway associations @@ -36 +36 @@ When you remove or add an allowed prefix, traffic which doesn't use that prefix -For a transit gateway association, you provision the allowed prefixes list on the Direct Connect gateway. The list routes on-premises traffic to or from a Direct Connect gateway to the transit gateway, even when the VPCs attached to the transit gateway do not have assigned CIDRs. Allowed prefixes work differently, depending on the gateway type: +For a Transit Gateway association, you provision the allowed prefixes list on the Direct Connect gateway. The list routes on-premises traffic to or from a Direct Connect gateway to the Transit Gateway, even when the VPCs attached to the Transit Gateway do not have assigned CIDRs. Allowed prefixes work differently, depending on the gateway type: @@ -38 +38 @@ For a transit gateway association, you provision the allowed prefixes list on th - * For transit gateway associations, only the allowed prefixes entered will be advertised to on-premises. These will show as originating from the Direct Connect gateway ASN. + * For Transit Gateway associations, only the allowed prefixes entered will be advertised to on-premises. These will show as originating from the Direct Connect gateway ASN. @@ -45 +45 @@ For a transit gateway association, you provision the allowed prefixes list on th -Consider the scenario where you have a VPC with CIDR 10.0.0.0/16 attached to a transit gateway. +Consider the scenario where you have a VPC with CIDR 10.0.0.0/16 attached to a Transit Gateway. @@ -56 +56 @@ Consider the scenario where you have a VPC with CIDR 10.0.0.0/16 attached to a t -Allowed prefix overlaps are not allowed when multiple transit gateways are associated with a Direct Connect gateway. For example, if you have a transit gateway with an allowed prefix list that includes 10.1.0.0/16, and a second transit gateway with an allowed prefix list that includes 10.2.0.0/16 and 0.0.0.0/0, you can't set the associations from the second transit gateway to 0.0.0.0/0. Since 0.0.0.0/0 includes all IPv4 networks, you can't configure 0.0.0.0/0 if multiple transit gateways are associated with a Direct Connect gateway. An error is returned indicating that the allowed routes overlap one or more existing allowed routes on the Direct Connect gateway. +Allowed prefix overlaps are not allowed when multiple Transit Gateways are associated with a Direct Connect gateway. For example, if you have a Transit Gateway with an allowed prefix list that includes 10.1.0.0/16, and a second Transit Gateway with an allowed prefix list that includes 10.2.0.0/16 and 0.0.0.0/0, you can't set the associations from the second Transit Gateway to 0.0.0.0/0. Since 0.0.0.0/0 includes all IPv4 networks, you can't configure 0.0.0.0/0 if multiple Transit Gateways are associated with a Direct Connect gateway. An error is returned indicating that the allowed routes overlap one or more existing allowed routes on the Direct Connect gateway. @@ -60 +60 @@ When you remove or add an allowed prefix, traffic which doesn't use that prefix -## Example: Allowed to prefixes in a transit gateway configuration +## Example: Allowed to prefixes in a Transit Gateway configuration @@ -64 +64 @@ Consider the configuration where you have instances in two different AWS Regions - * A transit gateway in each Region. + * A Transit Gateway in each Region. @@ -66 +66 @@ Consider the configuration where you have instances in two different AWS Regions - * A transit gateway peering connection. + * A Transit Gateway peering connection. @@ -70 +70 @@ Consider the configuration where you have instances in two different AWS Regions - * A transit gateway association between one of the transit gateways (the one in us-east-1) to the Direct Connect gateway. + * A Transit Gateway association between one of the Transit Gateways (the one in us-east-1) to the Direct Connect gateway. @@ -85 +85 @@ Configure the following options for the resources: - * Direct Connect gateway association with the transit gateway: Set the allowed prefixes to 10.0.0.0/8. + * Direct Connect gateway association with the Transit Gateway: Set the allowed prefixes to 10.0.0.0/8. @@ -87 +87 @@ Configure the following options for the resources: -This CIDR block encompasses both VPC CIDR blocks (10.0.0.0/16 and 10.2.0.0/16). For more information, see [Associate or disassociate a transit gateway with Direct Connect.](./associate-tgw-with-direct-connect-gateway.html). +This CIDR block encompasses both VPC CIDR blocks (10.0.0.0/16 and 10.2.0.0/16). For more information, see [Associate or disassociate a Transit Gateway with Direct Connect.](./associate-tgw-with-direct-connect-gateway.html). @@ -89 +89 @@ This CIDR block encompasses both VPC CIDR blocks (10.0.0.0/16 and 10.2.0.0/16). - * VPC route: To route traffic from the 10.2.0.0/16 VPC, create a route in the VPC route table with a Destination of 0.0.0.0/0 and the transit gateway ID as the Target. This enables traffic from the VPC to reach the Direct Connect gateway. For more information about routing to a transit gateway, see [Routing for a transit gateway](https://docs.aws.amazon.com/vpc/latest/userguide/route-table-options.html#route-tables-tgw) in the _Amazon VPC User Guide_. + * VPC route: To route traffic from the 10.2.0.0/16 VPC, create a route in the VPC route table with a Destination of 0.0.0.0/0 and the Transit Gateway ID as the Target. This enables traffic from the VPC to reach the Direct Connect gateway. For more information about routing to a Transit Gateway, see [Routing for a Transit Gateway](https://docs.aws.amazon.com/vpc/latest/userguide/route-table-options.html#route-tables-tgw) in the _Amazon VPC User Guide_.