AWS data-exchange documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in VPC endpoint documentation
Security assessment
Terminology update without changing the security posture. The PrivateLink security benefits remain unchanged.
Diff
diff --git a/data-exchange/latest/userguide/vpc-interface-endpoints.md b/data-exchange/latest/userguide/vpc-interface-endpoints.md index 15d39f274..f42ff43da 100644 --- a//data-exchange/latest/userguide/vpc-interface-endpoints.md +++ b//data-exchange/latest/userguide/vpc-interface-endpoints.md @@ -9 +9 @@ Considerations for AWS Data Exchange VPC endpointsCreating an interface VPC endp -You can establish a private connection between your virtual private cloud (VPC) and AWS Data Exchange 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 AWS Data Exchange API operations 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 AWS Data Exchange API operations. Traffic between your VPC and AWS Data Exchange does not leave the Amazon network. +You can establish a private connection between your virtual private cloud (VPC) and AWS Data Exchange 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 AWS Data Exchange API operations 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 AWS Data Exchange API operations. Traffic between your VPC and AWS Data Exchange does not leave the Amazon network.