AWS Security ChangesHomeSearch

AWS directconnect documentation change

Service: directconnect · 2025-11-19 · Documentation low

File: directconnect/latest/UserGuide/ts-layer-3.md

Summary

Updated terminology from 'AWS Direct Connect' to 'Direct Connect' in text and image alt text

Security assessment

Changes are branding/terminology updates without technical security implications. No vulnerabilities or security features are mentioned.

Diff

diff --git a/directconnect/latest/UserGuide/ts-layer-3.md b/directconnect/latest/UserGuide/ts-layer-3.md
index 210ad3a82..eb487e332 100644
--- a//directconnect/latest/UserGuide/ts-layer-3.md
+++ b//directconnect/latest/UserGuide/ts-layer-3.md
@@ -7 +7 @@
-Consider a situation where your AWS Direct Connect physical connection is up and you can ping the Amazon peer IP address. If your virtual interface is up and the BGP peering session cannot be established, use the following steps to troubleshoot the issue:
+Consider a situation where your Direct Connect physical connection is up and you can ping the Amazon peer IP address. If your virtual interface is up and the BGP peering session cannot be established, use the following steps to troubleshoot the issue:
@@ -28 +28 @@ The following flow chart contains the steps to diagnose issues with the BGP peer
-![Troubleshoot AWS Direct Connect](/images/directconnect/latest/UserGuide/images/troubleshooting-chart-layer-3-4.png)
+![Troubleshoot Direct Connect](/images/directconnect/latest/UserGuide/images/troubleshooting-chart-layer-3-4.png)