AWS entityresolution documentation change
Summary
Updated 'AWS Direct Connect' to 'Direct Connect' in PrivateLink documentation
Security assessment
Naming convention change that doesn't affect the security posture of using AWS PrivateLink for private VPC connections.
Diff
diff --git a/entityresolution/latest/userguide/vpc-interface-endpoints.md b/entityresolution/latest/userguide/vpc-interface-endpoints.md index b0db6778f..fff36629f 100644 --- a//entityresolution/latest/userguide/vpc-interface-endpoints.md +++ b//entityresolution/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 Entity Resolution. You can access AWS Entity Resolution 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 Entity Resolution. +You can use AWS PrivateLink to create a private connection between your VPC and AWS Entity Resolution. You can access AWS Entity Resolution 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 Entity Resolution.