AWS cloudcontrolapi documentation change
Summary
Updated phrasing from 'AWS Direct Connect connection' to 'Direct Connect connection'
Security assessment
Change only involves branding terminology without altering security concepts. PrivateLink security benefits remain unchanged.
Diff
diff --git a/cloudcontrolapi/latest/userguide/vpc-interface-endpoints.md b/cloudcontrolapi/latest/userguide/vpc-interface-endpoints.md index cc07b6bee..25cdd91c8 100644 --- a//cloudcontrolapi/latest/userguide/vpc-interface-endpoints.md +++ b//cloudcontrolapi/latest/userguide/vpc-interface-endpoints.md @@ -9 +9 @@ Considerations for Cloud Control API VPC endpointsCreating an interface VPC endp -You can use AWS PrivateLink to create a private connection between your VPC and AWS Cloud Control API. You can access Cloud Control API 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 Cloud Control API. +You can use AWS PrivateLink to create a private connection between your VPC and AWS Cloud Control API. You can access Cloud Control API 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 Cloud Control API.