AWS documentdb documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in AWS PrivateLink documentation
Security assessment
Consistency update in service naming. The security context of PrivateLink (keeping traffic within AWS network) remains unaffected by this terminology change.
Diff
diff --git a/documentdb/latest/developerguide/docdb-private-link.md b/documentdb/latest/developerguide/docdb-private-link.md index 4d1e5bb3b..878d89afe 100644 --- a//documentdb/latest/developerguide/docdb-private-link.md +++ b//documentdb/latest/developerguide/docdb-private-link.md @@ -15 +15 @@ You can establish a private connection between your VPC and Amazon DocumentDB AP -While Amazon DocumentDB instance-based clusters do not require an interface VPC endpoint connection, AWS PrivateLink enables you to privately access Amazon DocumentDB API operations without an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Amazon DocumentDB instances in your VPC don't need public IP addresses to communicate with Amazon DocumentDB API endpoints to launch, modify, or terminate database instances and database clusters. Your Amazon DocumentDB instances also don't need public IP addresses to use any of the available Amazon DocumentDB API operations. Traffic between your VPC and Amazon DocumentDB doesn't leave the Amazon network. +While Amazon DocumentDB instance-based clusters do not require an interface VPC endpoint connection, AWS PrivateLink enables you to privately access Amazon DocumentDB API operations without an internet gateway, NAT device, VPN connection, or Direct Connect connection. Amazon DocumentDB instances in your VPC don't need public IP addresses to communicate with Amazon DocumentDB API endpoints to launch, modify, or terminate database instances and database clusters. Your Amazon DocumentDB instances also don't need public IP addresses to use any of the available Amazon DocumentDB API operations. Traffic between your VPC and Amazon DocumentDB doesn't leave the Amazon network.