AWS ARG documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in PrivateLink documentation
Security assessment
The change is a branding/naming convention update (removing redundant 'AWS' prefix) with no security implications.
Diff
diff --git a/ARG/latest/userguide/vpc-interface-endpoints.md b/ARG/latest/userguide/vpc-interface-endpoints.md index ca9095559..2c3e3cf60 100644 --- a//ARG/latest/userguide/vpc-interface-endpoints.md +++ b//ARG/latest/userguide/vpc-interface-endpoints.md @@ -9 +9 @@ ConsiderationsCreate an interface endpointCreate an endpoint policy -You can use AWS PrivateLink to create a private connection between your VPC and AWS Resource Groups. You can access Resource Groups 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 Resource Groups. +You can use AWS PrivateLink to create a private connection between your VPC and AWS Resource Groups. You can access Resource Groups 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 Resource Groups.