AWS cloud-map documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in VPC endpoint documentation
Security assessment
Terminology update for service name consistency in PrivateLink documentation, no security implications or new security features documented.
Diff
diff --git a/cloud-map/latest/dg/vpc-interface-endpoints.md b/cloud-map/latest/dg/vpc-interface-endpoints.md index c0a071ed7..533a19500 100644 --- a//cloud-map/latest/dg/vpc-interface-endpoints.md +++ b//cloud-map/latest/dg/vpc-interface-endpoints.md @@ -9 +9 @@ ConsiderationsCreate an interface endpoint -You can use AWS PrivateLink to create a private connection between your VPC and AWS Cloud Map. You can access AWS Cloud Map 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 Cloud Map. +You can use AWS PrivateLink to create a private connection between your VPC and AWS Cloud Map. You can access AWS Cloud Map 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 Cloud Map.