AWS clean-rooms documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in VPC endpoint documentation
Security assessment
Another branding/naming convention update. The security aspects of using PrivateLink remain unchanged.
Diff
diff --git a/clean-rooms/latest/userguide/vpc-interface-endpoints.md b/clean-rooms/latest/userguide/vpc-interface-endpoints.md index 4995d0d4b..88d403519 100644 --- a//clean-rooms/latest/userguide/vpc-interface-endpoints.md +++ b//clean-rooms/latest/userguide/vpc-interface-endpoints.md @@ -9 +9 @@ ConsiderationsCreate an interface endpoint -You can use AWS PrivateLink to create a private connection between your virtual private cloud (VPC) and AWS Clean Rooms or AWS Clean Rooms ML. You can access AWS Clean Rooms or AWS Clean Rooms ML 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 Clean Rooms. +You can use AWS PrivateLink to create a private connection between your virtual private cloud (VPC) and AWS Clean Rooms or AWS Clean Rooms ML. You can access AWS Clean Rooms or AWS Clean Rooms ML 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 Clean Rooms.