AWS aws-supply-chain documentation change
Summary
Updated 'AWS Direct Connect' to 'Direct Connect' in VPC interface endpoint documentation
Security assessment
Branding terminology change without altering security implications of using PrivateLink for network isolation
Diff
diff --git a/aws-supply-chain/latest/adminguide/vpc-interface-endpoints.md b/aws-supply-chain/latest/adminguide/vpc-interface-endpoints.md index e0e758946..4ae1110fb 100644 --- a//aws-supply-chain/latest/adminguide/vpc-interface-endpoints.md +++ b//aws-supply-chain/latest/adminguide/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 Supply Chain. You can access AWS Supply Chain 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 Supply Chain. +You can use AWS PrivateLink to create a private connection between your VPC and AWS Supply Chain. You can access AWS Supply Chain 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 Supply Chain.