AWS ram documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in AWS PrivateLink documentation
Security assessment
Branding update without substantive security implications. Maintains existing security guidance about private network access.
Diff
diff --git a/ram/latest/userguide/vpc-interface-endpoints.md b/ram/latest/userguide/vpc-interface-endpoints.md index 509fe33c7..9f38b3c56 100644 --- a//ram/latest/userguide/vpc-interface-endpoints.md +++ b//ram/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 Resource Access Manager. You can access AWS RAM 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 RAM. +You can use AWS PrivateLink to create a private connection between your VPC and AWS Resource Access Manager. You can access AWS RAM 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 RAM.