AWS sms-voice documentation change
Summary
Updated 'AWS Direct Connect' to 'Direct Connect' in network connectivity documentation
Security assessment
Consistency edit for service naming. No changes to the security posture of PrivateLink implementation or VPC endpoint guidance.
Diff
diff --git a/sms-voice/latest/userguide/vpc-interface-endpoints.md b/sms-voice/latest/userguide/vpc-interface-endpoints.md index f05e7b218..c3d8a2e72 100644 --- a//sms-voice/latest/userguide/vpc-interface-endpoints.md +++ b//sms-voice/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 SMS. You can access AWS End User Messaging SMS 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 SMS. +You can use AWS PrivateLink to create a private connection between your VPC and AWS End User Messaging SMS. You can access AWS End User Messaging SMS 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 SMS.