AWS AmazonRDS documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in public access documentation
Security assessment
The change removes the 'AWS' prefix from 'Direct Connect' service name but doesn't alter security guidance. No security implications - only branding/naming convention adjustment.
Diff
diff --git a/AmazonRDS/latest/UserGuide/create-multi-az-db-cluster.md b/AmazonRDS/latest/UserGuide/create-multi-az-db-cluster.md index 756a0fec2..2533986b2 100644 --- a//AmazonRDS/latest/UserGuide/create-multi-az-db-cluster.md +++ b//AmazonRDS/latest/UserGuide/create-multi-az-db-cluster.md @@ -352 +352 @@ You can't change the master user name after the Multi-AZ DB cluster is created. -**Public access** | **Publicly accessible** to give the DB cluster a public IP address, meaning that it's accessible outside the VPC. To be publicly accessible, the DB cluster also has to be in a public subnet in the VPC. **Not publicly accessible** to make the DB cluster accessible only from inside the VPC. For more information, see [Hiding a DB instance in a VPC from the internet](./USER_VPC.WorkingWithRDSInstanceinaVPC.html#USER_VPC.Hiding). To connect to a DB cluster from outside of its VPC, the DB cluster must be publicly accessible. Also, access must be granted using the inbound rules of the DB cluster's security group, and other requirements must be met. For more information, see [Can't connect to Amazon RDS DB instance](./CHAP_Troubleshooting.html#CHAP_Troubleshooting.Connecting). If your DB cluster isn't publicly accessible, you can use an AWS Site-to-Site VPN connection or an AWS Direct Connect connection to access it from a private network. For more information, see [Internetwork traffic privacy](./inter-network-traffic-privacy.html). | **CLI option:** `--publicly-accessible` `--no-publicly-accessible` **RDS API parameter:** `PubliclyAccessible` +**Public access** | **Publicly accessible** to give the DB cluster a public IP address, meaning that it's accessible outside the VPC. To be publicly accessible, the DB cluster also has to be in a public subnet in the VPC. **Not publicly accessible** to make the DB cluster accessible only from inside the VPC. For more information, see [Hiding a DB instance in a VPC from the internet](./USER_VPC.WorkingWithRDSInstanceinaVPC.html#USER_VPC.Hiding). To connect to a DB cluster from outside of its VPC, the DB cluster must be publicly accessible. Also, access must be granted using the inbound rules of the DB cluster's security group, and other requirements must be met. For more information, see [Can't connect to Amazon RDS DB instance](./CHAP_Troubleshooting.html#CHAP_Troubleshooting.Connecting). If your DB cluster isn't publicly accessible, you can use an AWS Site-to-Site VPN connection or an Direct Connect connection to access it from a private network. For more information, see [Internetwork traffic privacy](./inter-network-traffic-privacy.html). | **CLI option:** `--publicly-accessible` `--no-publicly-accessible` **RDS API parameter:** `PubliclyAccessible`