AWS AmazonRDS documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in network connectivity section
Security assessment
Consistency update for service naming. The security implications of using Direct Connect vs public access remain unchanged in the documentation.
Diff
diff --git a/AmazonRDS/latest/UserGuide/modify-multi-az-db-cluster.md b/AmazonRDS/latest/UserGuide/modify-multi-az-db-cluster.md index 0ace82fe4..bda41d7ef 100644 --- a//AmazonRDS/latest/UserGuide/modify-multi-az-db-cluster.md +++ b//AmazonRDS/latest/UserGuide/modify-multi-az-db-cluster.md @@ -102 +102 @@ Console setting | Setting description | CLI option and RDS API parameter | When -**Public access** | **Publicly accessible** to give the DB cluster a public IP address, meaning that it's accessible outside its virtual private cloud (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). | Not available when modifying a DB cluster. | The change occurs immediately. This setting ignores the apply immediately setting. | Downtime doesn't occur during this change. +**Public access** | **Publicly accessible** to give the DB cluster a public IP address, meaning that it's accessible outside its virtual private cloud (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). | Not available when modifying a DB cluster. | The change occurs immediately. This setting ignores the apply immediately setting. | Downtime doesn't occur during this change.