AWS vpc-lattice documentation change
Summary
Updated terminology from 'AWS Direct Connect' to 'Direct Connect' in the VPC interface endpoints documentation
Security assessment
The change only involves a branding update (removing 'AWS' from 'AWS Direct Connect'). No security concepts, vulnerabilities, or security features were added or modified. The core security context of using PrivateLink for private connections remains unchanged.
Diff
diff --git a/vpc-lattice/latest/ug/vpc-interface-endpoints.md b/vpc-lattice/latest/ug/vpc-interface-endpoints.md index 05428390f..fe304925a 100644 --- a//vpc-lattice/latest/ug/vpc-interface-endpoints.md +++ b//vpc-lattice/latest/ug/vpc-interface-endpoints.md @@ -9 +9 @@ Considerations for interface VPC endpointsCreating an interface VPC endpoint for -You can establish a private connection between your VPC and Amazon VPC Lattice by creating an _interface VPC endpoint_. Interface endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink/), a technology that enables you to privately access VPC Lattice APIs without an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to communicate with VPC Lattice APIs. +You can establish a private connection between your VPC and Amazon VPC Lattice by creating an _interface VPC endpoint_. Interface endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink/), a technology that enables you to privately access VPC Lattice APIs without an internet gateway, NAT device, VPN connection, or Direct Connect connection. Instances in your VPC don't need public IP addresses to communicate with VPC Lattice APIs.