AWS architecture-diagrams documentation change
Summary
Updated terminology from 'AWS Direct Connect' to 'Direct Connect' throughout documentation, including section headers, descriptions, and image captions. Changed references to 'AWS Direct Connect gateway' to 'Direct Connect gateway' and updated a URL path segment from 'aws-direct-connect' to 'direct-connect'.
Security assessment
The changes appear to be branding/terminology updates rather than security-related modifications. There is no evidence of addressing vulnerabilities or security configurations. The updates maintain the same technical content about network routing through AWS backbone but use shortened product names.
Diff
diff --git a/architecture-diagrams/latest/routing-scenarios-with-aws-direct-connect-sitelink/routing-scenarios-with-aws-direct-connect-sitelink.md b/architecture-diagrams/latest/routing-scenarios-with-aws-direct-connect-sitelink/routing-scenarios-with-aws-direct-connect-sitelink.md index 08d766384..51f568981 100644 --- a//architecture-diagrams/latest/routing-scenarios-with-aws-direct-connect-sitelink/routing-scenarios-with-aws-direct-connect-sitelink.md +++ b//architecture-diagrams/latest/routing-scenarios-with-aws-direct-connect-sitelink/routing-scenarios-with-aws-direct-connect-sitelink.md @@ -5 +5 @@ -Traffic Flow Between On-Premises Locations DiagramTraffic Flow Between On-Premises Locations – BackupTraffic Flow Between On-Premises Locations – ExtensionFull Mesh Connectivity Between On-Premises Locations and AWSTraffic Segmentation with Several AWS Direct Connect GatewaysDownload editable diagramCreate a free AWS accountFurther readingContributorsDiagram history +Traffic Flow Between On-Premises Locations DiagramTraffic Flow Between On-Premises Locations – BackupTraffic Flow Between On-Premises Locations – ExtensionFull Mesh Connectivity Between On-Premises Locations and AWSTraffic Segmentation with Several Direct Connect GatewaysDownload editable diagramCreate a free AWS accountFurther readingContributorsDiagram history @@ -13 +13 @@ Publication date: **July 25, 2023 (Diagram history)** -With AWS Direct Connect SiteLink, route traffic between AWS Direct Connect locations through the AWS global network backbone without traversing any AWS Region. Associate your private or transit virtual interfaces (VIFs) to a common AWS Direct Connect gateway and enable SiteLink in those VIFs. +With AWS Direct Connect SiteLink, route traffic between Direct Connect locations through the AWS global network backbone without traversing any AWS Region. Associate your private or transit virtual interfaces (VIFs) to a common Direct Connect gateway and enable SiteLink in those VIFs. @@ -15 +15 @@ With AWS Direct Connect SiteLink, route traffic between AWS Direct Connect locat - + @@ -19 +19 @@ With AWS Direct Connect SiteLink, route traffic between AWS Direct Connect locat - 2. Once the VIF is attached to the **AWS Direct Connect** gateway (DXGW), it announces the CIDR block to any resource associated with it (such as **Amazon Virtual Private Cloud** (Amazon VPC) or **AWS Transit Gateway**). If SiteLink is enabled on this VIF, the CIDR block will also be announced to any other VIF that is attached to this **AWS Direct Connect** gateway and has SiteLink enabled. + 2. Once the VIF is attached to the **Direct Connect** gateway (DXGW), it announces the CIDR block to any resource associated with it (such as **Amazon Virtual Private Cloud** (Amazon VPC) or **AWS Transit Gateway**). If SiteLink is enabled on this VIF, the CIDR block will also be announced to any other VIF that is attached to this **Direct Connect** gateway and has SiteLink enabled. @@ -21 +21 @@ With AWS Direct Connect SiteLink, route traffic between AWS Direct Connect locat - 3. The customer gateway in the corporate data center B configures its VIF and it is associated with the **AWS Direct Connect** gateway. It receives the 10.0.1.0/24 block with AS PATH 65001 650011 65512\. The block 10.0.2.0/24 will also be announced to corporate data center A through the gateway with AS PATH 65001 65001 65513. Now both locations will be able to route traffic between each other. + 3. The customer gateway in the corporate data center B configures its VIF and it is associated with the **Direct Connect** gateway. It receives the 10.0.1.0/24 block with AS PATH 65001 650011 65512\. The block 10.0.2.0/24 will also be announced to corporate data center A through the gateway with AS PATH 65001 65001 65513. Now both locations will be able to route traffic between each other. @@ -26 +26 @@ With AWS Direct Connect SiteLink, route traffic between AWS Direct Connect locat -1 When connecting two AWS Direct Connect connections to the same AWS device, you get +1 AS prepended (AWS Direct Connect gateway ASN) when using SiteLink. However, when these connections are in different sites, you get this ASN twice (+2 AS prepended) – one for each AWS router. +1 When connecting two Direct Connect connections to the same AWS device, you get +1 AS prepended (Direct Connect gateway ASN) when using SiteLink. However, when these connections are in different sites, you get this ASN twice (+2 AS prepended) – one for each AWS router. @@ -38 +38 @@ You can use AWS Direct Connect SiteLink as a backup path to your private network - 3. In the case of an outage of the WAN network, traffic from corporate data center A to data center B is routed directly between **AWS Direct Connect** locations without traversing any AWS Region. + 3. In the case of an outage of the WAN network, traffic from corporate data center A to data center B is routed directly between **Direct Connect** locations without traversing any AWS Region. @@ -43 +43 @@ You can use AWS Direct Connect SiteLink as a backup path to your private network -For more information about how to influence path preference using BGP, refer to [Creating active/passive BGP connections over AWS Direct Connect.](https://aws.amazon.com/blogs/networking-and-content-delivery/creating-active-passive-bgp-connections-over-aws-direct-connect/) +For more information about how to influence path preference using BGP, refer to [Creating active/passive BGP connections over Direct Connect.](https://aws.amazon.com/blogs/networking-and-content-delivery/creating-active-passive-bgp-connections-over-aws-direct-connect/) @@ -47 +47 @@ For more information about how to influence path preference using BGP, refer to -You can use AWS Direct Connect SiteLink as an extension of your private network to route traffic between on-premises locations using AWS global network backbone without traversing any AWS Region. Not all of your datacenters need to have a direct connection. +You can use Direct Connect SiteLink as an extension of your private network to route traffic between on-premises locations using AWS global network backbone without traversing any AWS Region. Not all of your datacenters need to have a direct connection. @@ -49 +49 @@ You can use AWS Direct Connect SiteLink as an extension of your private network - + @@ -55 +55 @@ You can use AWS Direct Connect SiteLink as an extension of your private network - 3. Traffic between corporate data centers A and C is routed directly between **AWS Direct Connect** locations without traversing any AWS Region. + 3. Traffic between corporate data centers A and C is routed directly between **Direct Connect** locations without traversing any AWS Region. @@ -62 +62 @@ You can use AWS Direct Connect SiteLink as an extension of your private network -With a common AWS Direct Connect gateway, you can use the AWS backbone as the transit network to connect between on-premises and AWS resources worldwide. Enable SiteLink on your VIFs and attach them to a common AWS Direct Connect gateway, connected to your AWS resource (for example, AWS Transit Gateway or Amazon Virtual Private Cloud). +With a common Direct Connect gateway, you can use the AWS backbone as the transit network to connect between on-premises and AWS resources worldwide. Enable SiteLink on your VIFs and attach them to a common Direct Connect gateway, connected to your AWS resource (for example, AWS Transit Gateway or Amazon Virtual Private Cloud). @@ -70 +70 @@ With a common AWS Direct Connect gateway, you can use the AWS backbone as the tr - 3. The customer gateway in corporate data center A receives the CIDR blocks of the resources in AWS (Regions 1 and 2) with the AS PATH 65001 from the **AWS Direct Connect** gateway. + 3. The customer gateway in corporate data center A receives the CIDR blocks of the resources in AWS (Regions 1 and 2) with the AS PATH 65001 from the **Direct Connect** gateway. @@ -74 +74 @@ With a common AWS Direct Connect gateway, you can use the AWS backbone as the tr - 5. **Transit Gateway** in Region 2 routes the traffic to the corresponding **Amazon Virtual Private Cloud** (Amazon VPC) according to the **Transit Gateway** route table associated with the **AWS Direct Connect** gateway association. + 5. **Transit Gateway** in Region 2 routes the traffic to the corresponding **Amazon Virtual Private Cloud** (Amazon VPC) according to the **Transit Gateway** route table associated with the **Direct Connect** gateway association. @@ -79 +79 @@ With a common AWS Direct Connect gateway, you can use the AWS backbone as the tr -## Traffic Segmentation with Several AWS Direct Connect Gateways +## Traffic Segmentation with Several Direct Connect Gateways