AWS pcs documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in PrivateLink description
Security assessment
Branding/naming standardization update (removing 'AWS' prefix). No changes to security posture - the PrivateLink security benefits remain described as before.
Diff
diff --git a/pcs/latest/userguide/vpc-interface-endpoints.md b/pcs/latest/userguide/vpc-interface-endpoints.md index c1f37dace..ee26e53b1 100644 --- a//pcs/latest/userguide/vpc-interface-endpoints.md +++ b//pcs/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 Parallel Computing Service (AWS PCS). You can access AWS PCS 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 PCS. +You can use AWS PrivateLink to create a private connection between your VPC and AWS Parallel Computing Service (AWS PCS). You can access AWS PCS 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 PCS.