AWS Security ChangesHomeSearch

AWS inspector documentation change

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

File: inspector/latest/user/vpc-interface-endpoints-inspector.md

Summary

Updated service name reference from 'AWS Direct Connect' to 'Direct Connect' in PrivateLink documentation

Security assessment

Branding terminology update with no impact on security content. PrivateLink security benefits remain unchanged.

Diff

diff --git a/inspector/latest/user/vpc-interface-endpoints-inspector.md b/inspector/latest/user/vpc-interface-endpoints-inspector.md
index e7d4cd94d..debed5b91 100644
--- a//inspector/latest/user/vpc-interface-endpoints-inspector.md
+++ b//inspector/latest/user/vpc-interface-endpoints-inspector.md
@@ -9 +9 @@ ConsiderationsCreate an interface endpoint
-You can use AWS PrivateLink to create a private connection between your VPC and Amazon Inspector. You can access Amazon Inspector as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to access Amazon Inspector. 
+You can use AWS PrivateLink to create a private connection between your VPC and Amazon Inspector. You can access Amazon Inspector as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or Direct Connect connection. Instances in your VPC don't need public IP addresses to access Amazon Inspector.