AWS outposts documentation change
Summary
Updated references from 'AWS Direct Connect' to 'Direct Connect' throughout the document, including section headers, troubleshooting steps, and documentation links. No technical changes to procedures or configurations.
Security assessment
The changes are purely branding/naming updates (removing 'AWS' from 'AWS Direct Connect'). There is no evidence of addressing security vulnerabilities, patching weaknesses, or modifying security-related configurations. The troubleshooting procedures and recommendations remain technically unchanged.
Diff
diff --git a/outposts/latest/userguide/network-troubleshoot.md b/outposts/latest/userguide/network-troubleshoot.md index 966c5695c..169f4ddf6 100644 --- a//outposts/latest/userguide/network-troubleshoot.md +++ b//outposts/latest/userguide/network-troubleshoot.md @@ -5 +5 @@ -Connectivity with Outpost network devicesAWS Direct Connect public virtual interface connectivity to AWS RegionAWS Direct Connect private virtual interface connectivity to AWS RegionISP public internet connectivity to AWS RegionOutposts is behind two firewall devices +Connectivity with Outpost network devicesDirect Connect public virtual interface connectivity to AWS RegionDirect Connect private virtual interface connectivity to AWS RegionISP public internet connectivity to AWS RegionOutposts is behind two firewall devices @@ -56 +56 @@ If BGP peering status is `UP` between the customer local network devices and the - * Edge routers connected with AWS Direct Connect – Public virtual interface in use for service link connectivity. For more information, see AWS Direct Connect public virtual interface connectivity to AWS Region. + * Edge routers connected with Direct Connect – Public virtual interface in use for service link connectivity. For more information, see Direct Connect public virtual interface connectivity to AWS Region. @@ -58 +58 @@ If BGP peering status is `UP` between the customer local network devices and the - * Edge routers connected with AWS Direct Connect – Private virtual interface in use for service link connectivity. For more information, see AWS Direct Connect private virtual interface connectivity to AWS Region. + * Edge routers connected with Direct Connect – Private virtual interface in use for service link connectivity. For more information, see Direct Connect private virtual interface connectivity to AWS Region. @@ -65 +65 @@ If BGP peering status is `UP` between the customer local network devices and the -## AWS Direct Connect public virtual interface connectivity to AWS Region +## Direct Connect public virtual interface connectivity to AWS Region @@ -67 +67 @@ If BGP peering status is `UP` between the customer local network devices and the -Use the following checklist to troubleshoot edge routers connected with AWS Direct Connect when a public virtual interface is in use for service link connectivity. +Use the following checklist to troubleshoot edge routers connected with Direct Connect when a public virtual interface is in use for service link connectivity. @@ -79 +79 @@ Use the following checklist to troubleshoot edge routers connected with AWS Dire - 1. Check the AWS Direct Connect link status from the edge router or the AWS Management Console. + 1. Check the Direct Connect link status from the edge router or the AWS Management Console. @@ -83 +83 @@ Use the following checklist to troubleshoot edge routers connected with AWS Dire - 3. If the BGP peering status is `DOWN`, ping the peer AWS IP address and check the BGP configuration in the edge router. For more information, see [Troubleshooting AWS Direct Connect](https://docs.aws.amazon.com/directconnect/latest/UserGuide/Troubleshooting.html) in the _AWS Direct Connect User Guide_ and [My virtual interface BGP status is down in the AWS console. What should I do?](https://repost.aws/knowledge-center/virtual-interface-bgp-down). + 3. If the BGP peering status is `DOWN`, ping the peer AWS IP address and check the BGP configuration in the edge router. For more information, see [Troubleshooting Direct Connect](https://docs.aws.amazon.com/directconnect/latest/UserGuide/Troubleshooting.html) in the _Direct Connect User Guide_ and [My virtual interface BGP status is down in the AWS console. What should I do?](https://repost.aws/knowledge-center/virtual-interface-bgp-down). @@ -107 +107 @@ Use the following checklist to troubleshoot edge routers connected with AWS Dire - 6. If the issue persists, perform MTR / traceroute / packet captures from your edge router to the AWS Direct Connect peer IP addresses. Share the test results with AWS Support, using your Enterprise support plan. + 6. If the issue persists, perform MTR / traceroute / packet captures from your edge router to the Direct Connect peer IP addresses. Share the test results with AWS Support, using your Enterprise support plan. @@ -112 +112 @@ Use the following checklist to troubleshoot edge routers connected with AWS Dire -## AWS Direct Connect private virtual interface connectivity to AWS Region +## Direct Connect private virtual interface connectivity to AWS Region @@ -114 +114 @@ Use the following checklist to troubleshoot edge routers connected with AWS Dire -Use the following checklist to troubleshoot edge routers connected with AWS Direct Connect when a private virtual interface is in use for service link connectivity. +Use the following checklist to troubleshoot edge routers connected with Direct Connect when a private virtual interface is in use for service link connectivity. @@ -120 +120 @@ Use the following checklist to troubleshoot edge routers connected with AWS Dire - 2. Ensure that BGP peering over the AWS Direct Connect private virtual interface between your service link endpoint VPC and the Outpost installed on your premises is `UP`. For more information, see [Troubleshooting AWS Direct Connect](https://docs.aws.amazon.com/directconnect/latest/UserGuide/Troubleshooting.html) in the _AWS Direct Connect User Guide_ , [My virtual interface BGP status is down in the AWS console. What should I do?](https://repost.aws/knowledge-center/virtual-interface-bgp-down), and [How can I troubleshoot BGP connection issues over Direct Connect?](https://repost.aws/knowledge-center/troubleshoot-bgp-dx). + 2. Ensure that BGP peering over the Direct Connect private virtual interface between your service link endpoint VPC and the Outpost installed on your premises is `UP`. For more information, see [Troubleshooting Direct Connect](https://docs.aws.amazon.com/directconnect/latest/UserGuide/Troubleshooting.html) in the _Direct Connect User Guide_ , [My virtual interface BGP status is down in the AWS console. What should I do?](https://repost.aws/knowledge-center/virtual-interface-bgp-down), and [How can I troubleshoot BGP connection issues over Direct Connect?](https://repost.aws/knowledge-center/troubleshoot-bgp-dx). @@ -122 +122 @@ Use the following checklist to troubleshoot edge routers connected with AWS Dire - 3. The AWS Direct Connect private virtual interface is a private connection to your edge router in your chosen AWS Direct Connect location, and it uses BGP to exchange routes. Your private virtual private cloud (VPC) CIDR range is advertised through this BGP session to your edge router. Similarly, the IP address range for the Outpost service link is advertised to the region through BGP from your edge router. + 3. The Direct Connect private virtual interface is a private connection to your edge router in your chosen Direct Connect location, and it uses BGP to exchange routes. Your private virtual private cloud (VPC) CIDR range is advertised through this BGP session to your edge router. Similarly, the IP address range for the Outpost service link is advertised to the region through BGP from your edge router. @@ -132 +132 @@ Use the following checklist to troubleshoot edge routers connected with AWS Dire - 3. If the issue persists, perform MTR / traceroute / packet captures from your edge router to the AWS Direct Connect peer IP addresses. Share the test results with AWS Support, using your Enterprise support plan. + 3. If the issue persists, perform MTR / traceroute / packet captures from your edge router to the Direct Connect peer IP addresses. Share the test results with AWS Support, using your Enterprise support plan. @@ -215 +215 @@ If you have placed your Outpost behind a high-availability pair of synced firewa - * If you are using AWS Direct Connect connectivity for the service link, it is possible that an AWS planned maintenance triggered asymmetric routing of the service link. + * If you are using Direct Connect connectivity for the service link, it is possible that an AWS planned maintenance triggered asymmetric routing of the service link. @@ -217 +217 @@ If you have placed your Outpost behind a high-availability pair of synced firewa - * Check for notifications of planned maintenance on your AWS Direct Connect service(s). + * Check for notifications of planned maintenance on your Direct Connect service(s). @@ -219 +219 @@ If you have placed your Outpost behind a high-availability pair of synced firewa - * Note that if you have redundant AWS Direct Connect services, you can proactively test the routing of the Outposts service link over each likely network path under maintenance conditions. This allows you to test if an interruption to one of your AWS Direct Connect services could lead to asymmetric routing of the service link. The resiliency of the AWS Direct Connect portion of the end-to-end network connectivity can be tested by the AWS Direct Connect Resiliency with Resiliency Toolkit. For more information, see [Testing AWS Direct Connect Resiliency with Resiliency Toolkit – Failover Testing](https://aws.amazon.com/blogs/networking-and-content-delivery/testing-aws-direct-connect-resiliency-with-resiliency-toolkit-failover-testing/). + * Note that if you have redundant Direct Connect services, you can proactively test the routing of the Outposts service link over each likely network path under maintenance conditions. This allows you to test if an interruption to one of your Direct Connect services could lead to asymmetric routing of the service link. The resiliency of the Direct Connect portion of the end-to-end network connectivity can be tested by the Direct Connect Resiliency with Resiliency Toolkit. For more information, see [Testing Direct Connect Resiliency with Resiliency Toolkit – Failover Testing](https://aws.amazon.com/blogs/networking-and-content-delivery/testing-aws-direct-connect-resiliency-with-resiliency-toolkit-failover-testing/).