AWS connect documentation change
Summary
Updated 'AWS Direct Connect' to 'Direct Connect' in PrivateLink documentation
Security assessment
Branding/naming convention change without altering security properties of PrivateLink implementation
Diff
diff --git a/connect/latest/adminguide/vpc-interface-endpoints.md b/connect/latest/adminguide/vpc-interface-endpoints.md index fbce2506d..473f565f2 100644 --- a//connect/latest/adminguide/vpc-interface-endpoints.md +++ b//connect/latest/adminguide/vpc-interface-endpoints.md @@ -26 +26 @@ The core Amazon Connect service does not support AWS PrivateLink or VPC endpoint -Interface endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that enables you to privately access Amazon Connect 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 the Amazon Connect APIs that integrate with AWS PrivateLink. +Interface endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that enables you to privately access Amazon Connect 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 the Amazon Connect APIs that integrate with AWS PrivateLink.