AWS push-notifications documentation change
Summary
Replaced 'AWS Direct Connect' with 'Direct Connect' in PrivateLink connectivity documentation
Security assessment
Terminology standardization. No impact on security posture as the guidance about avoiding public IPs remains identical.
Diff
diff --git a/push-notifications/latest/userguide/vpc-interface-endpoints.md b/push-notifications/latest/userguide/vpc-interface-endpoints.md index cfa38669e..b18d66d83 100644 --- a//push-notifications/latest/userguide/vpc-interface-endpoints.md +++ b//push-notifications/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 Push. You can access AWS End User Messaging Push 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 Push. +You can use AWS PrivateLink to create a private connection between your VPC and AWS End User Messaging Push. You can access AWS End User Messaging Push 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 Push.