AWS verifiedpermissions documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' for terminology consistency
Security assessment
Non-substantive terminology update in PrivateLink documentation. No security impact or feature changes.
Diff
diff --git a/verifiedpermissions/latest/userguide/vpc-interface-endpoints.md b/verifiedpermissions/latest/userguide/vpc-interface-endpoints.md index 1f96da732..07c81b1ff 100644 --- a//verifiedpermissions/latest/userguide/vpc-interface-endpoints.md +++ b//verifiedpermissions/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 Amazon Verified Permissions. You can access Verified Permissions 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 Verified Permissions. +You can use AWS PrivateLink to create a private connection between your VPC and Amazon Verified Permissions. You can access Verified Permissions 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 Verified Permissions.