AWS AmazonRDS documentation change
Summary
Replaced 'AWS Direct Connect' with 'Direct Connect' for terminology consistency
Security assessment
The edit standardizes the service name but does not modify the security implications of using PrivateLink. The content still emphasizes keeping traffic within the Amazon network, which is a security best practice, but the change itself is non-functional.
Diff
diff --git a/AmazonRDS/latest/UserGuide/vpc-interface-endpoints.md b/AmazonRDS/latest/UserGuide/vpc-interface-endpoints.md index ccc645c20..d30432a5b 100644 --- a//AmazonRDS/latest/UserGuide/vpc-interface-endpoints.md +++ b//AmazonRDS/latest/UserGuide/vpc-interface-endpoints.md @@ -11 +11 @@ You can establish a private connection between your VPC and Amazon RDS API endpo -AWS PrivateLink enables you to privately access Amazon RDS API operations without an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. DB instances in your VPC don't need public IP addresses to communicate with Amazon RDS API endpoints to launch, modify, or terminate DB instances. Your DB instances also don't need public IP addresses to use any of the available RDS API operations. Traffic between your VPC and Amazon RDS doesn't leave the Amazon network. +AWS PrivateLink enables you to privately access Amazon RDS API operations without an internet gateway, NAT device, VPN connection, or Direct Connect connection. DB instances in your VPC don't need public IP addresses to communicate with Amazon RDS API endpoints to launch, modify, or terminate DB instances. Your DB instances also don't need public IP addresses to use any of the available RDS API operations. Traffic between your VPC and Amazon RDS doesn't leave the Amazon network.