AWS controlcatalog documentation change
Summary
Updated 'AWS Direct Connect' to 'Direct Connect' in PrivateLink setup documentation
Security assessment
Terminology standardization without modifying security architecture or recommendations
Diff
diff --git a/controlcatalog/latest/userguide/vpc-interface-endpoints.md b/controlcatalog/latest/userguide/vpc-interface-endpoints.md index dae4e9eae..8782a8f58 100644 --- a//controlcatalog/latest/userguide/vpc-interface-endpoints.md +++ b//controlcatalog/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 Control Catalog. You can access AWS Control Catalog 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 Control Catalog. +You can use AWS PrivateLink to create a private connection between your VPC and Control Catalog. You can access AWS Control Catalog 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 Control Catalog.