AWS controltower documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in PrivateLink documentation
Security assessment
This is a branding/style change to use the shortened service name. The security posture of PrivateLink networking guidance remains unchanged.
Diff
diff --git a/controltower/latest/userguide/networking-privatelink.md b/controltower/latest/userguide/networking-privatelink.md index 78d036c2c..d6fcfc679 100644 --- a//controltower/latest/userguide/networking-privatelink.md +++ b//controltower/latest/userguide/networking-privatelink.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 Control Tower. You can access AWS Control Tower 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 Control Tower. +You can use AWS PrivateLink to create a private connection between your VPC and AWS Control Tower. You can access AWS Control Tower 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 Control Tower.