AWS social-messaging documentation change
Summary
Replaced 'AWS Direct Connect connection' with 'Direct Connect connection'
Security assessment
Branding terminology update only. No changes to PrivateLink security mechanisms or network isolation principles.
Diff
diff --git a/social-messaging/latest/userguide/vpc-interface-endpoints.md b/social-messaging/latest/userguide/vpc-interface-endpoints.md index bf490e514..270b4326c 100644 --- a//social-messaging/latest/userguide/vpc-interface-endpoints.md +++ b//social-messaging/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 End User Messaging Social. You can access AWS End User Messaging Social 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 AWS End User Messaging Social. +You can use AWS PrivateLink to create a private connection between your VPC and AWS End User Messaging Social. You can access AWS End User Messaging Social 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 AWS End User Messaging Social.