AWS vpn documentation change
Summary
Updated terminology from 'AWS Direct Connect' to 'Direct Connect' throughout the document, removed redundant 'AWS' references in product names and links, and maintained existing security guidance about RFC 1918 addresses for tunnel endpoints.
Security assessment
The changes are primarily branding/terminology updates (removing redundant 'AWS' references) and do not introduce new security content or address vulnerabilities. The existing security guidance about using RFC 1918 addresses remains unchanged except for terminology alignment. No evidence of security vulnerability fixes or new security features added.
Diff
diff --git a/vpn/latest/s2svpn/private-ip-dx-steps.md b/vpn/latest/s2svpn/private-ip-dx-steps.md index dae4810f1..6138ae6d5 100644 --- a//vpn/latest/s2svpn/private-ip-dx-steps.md +++ b//vpn/latest/s2svpn/private-ip-dx-steps.md @@ -7 +7 @@ PrerequisitesCreate the customer gateway -# Create a private IP AWS Site-to-Site VPN over AWS Direct Connect +# Create a private IP AWS Site-to-Site VPN over Direct Connect @@ -9 +9 @@ PrerequisitesCreate the customer gateway -To create a private IP VPN with AWS Direct Connect follow these steps. Before you create the private IP VPN over Direct Connect, you need to ensure that a transit gateway and Direct Connect gateway are first created. After creating the two gateways you then need to create an assocation between the two. These prerequisites are described in the following table. Once you've created and associated the two gateways, you'll create a VPN customer cateway and connection using that association. +To create a private IP VPN with Direct Connect follow these steps. Before you create the private IP VPN over Direct Connect, you need to ensure that a transit gateway and Direct Connect gateway are first created. After creating the two gateways you then need to create an assocation between the two. These prerequisites are described in the following table. Once you've created and associated the two gateways, you'll create a VPN customer cateway and connection using that association. @@ -22,2 +22,2 @@ When specifying the transit gateway CIDR block to be associated with your Privat -Create the AWS Direct Connect gateway for Site-to-Site VPN. | Create the Direct Connect gateway by using the Direct Connect console or by using the command-line or API. See [Create an AWS Direct Connect gateway](https://docs.aws.amazon.com/directconnect/latest/UserGuide/create-direct-connect-gateway.html) in the _AWS Direct Connect User Guide_. | A Direct Connect gateway allows you to connect virtual interfaces (VIFs) across multiple AWS Regions. This gateway is used to connect to your VIF. -Create the transit gateway association for Site-to-Site VPN. | Create the association between the Direct Connect gateway and the transit gateway by using the Direct Connect console or using the command-line or API. See [Associate or disassociate AWS Direct Connect with a transit gateway](https://docs.aws.amazon.com/directconnect/latest/UserGuide/associate-tgw-with-direct-connect-gateway.html) in the _AWS Direct Connect User Guide_. | After creating the AWS Direct Connect gateway, create a transit gateway association for the AWS Direct Connect gateway. Specify the private IP CIDR for the transit gateway that was identified earlier in the allowed prefixes list. +Create the Direct Connect gateway for Site-to-Site VPN. | Create the Direct Connect gateway by using the Direct Connect console or by using the command-line or API. See [Create an AWS Direct Connect gateway](https://docs.aws.amazon.com/directconnect/latest/UserGuide/create-direct-connect-gateway.html) in the _Direct Connect User Guide_. | A Direct Connect gateway allows you to connect virtual interfaces (VIFs) across multiple AWS Regions. This gateway is used to connect to your VIF. +Create the transit gateway association for Site-to-Site VPN. | Create the association between the Direct Connect gateway and the transit gateway by using the Direct Connect console or using the command-line or API. See [Associate or disassociate Direct Connect with a transit gateway](https://docs.aws.amazon.com/directconnect/latest/UserGuide/associate-tgw-with-direct-connect-gateway.html) in the _Direct Connect User Guide_. | After creating the Direct Connect gateway, create a transit gateway association for the Direct Connect gateway. Specify the private IP CIDR for the transit gateway that was identified earlier in the allowed prefixes list. @@ -45 +45 @@ A customer gateway is a resource that you create in AWS. It represents the custo -When configuring AWS Private IP AWS Site-to-Site VPN, you must specify your own tunnel endpoint IP addresses using RFC 1918 addresses. Do not use the point-to-point IP addresses for the eBGP peering between your customer gateway router and the AWS Direct Connect endpoint. AWS recommends using a loopback or LAN interface on your customer gateway router as the source or destination address instead of point-to-point connections. +When configuring AWS Private IP AWS Site-to-Site VPN, you must specify your own tunnel endpoint IP addresses using RFC 1918 addresses. Do not use the point-to-point IP addresses for the eBGP peering between your customer gateway router and the Direct Connect endpoint. AWS recommends using a loopback or LAN interface on your customer gateway router as the source or destination address instead of point-to-point connections. @@ -77 +77 @@ If you specified **IPv6** for **Tunnel inside IP version** , you can optionally - 18. For **Transport attachment ID** , choose the transit gateway attachment for the appropriate AWS Direct Connect gateway. + 18. For **Transport attachment ID** , choose the transit gateway attachment for the appropriate Direct Connect gateway. @@ -86 +86 @@ If you specified **IPv6** for **Tunnel inside IP version** , you can optionally -The **Enable acceleration** option is not applicable for VPN connections over AWS Direct Connect. +The **Enable acceleration** option is not applicable for VPN connections over Direct Connect.