AWS AmazonRDS documentation change
Summary
Modified 'AWS Direct Connect' to 'Direct Connect' in network connectivity section
Security assessment
Consistency update for service naming. No changes to security controls or recommendations about public accessibility and VPC configurations.
Diff
diff --git a/AmazonRDS/latest/UserGuide/USER_ModifyInstance.Settings.md b/AmazonRDS/latest/UserGuide/USER_ModifyInstance.Settings.md index 05cd05d52..24a9881fc 100644 --- a//AmazonRDS/latest/UserGuide/USER_ModifyInstance.Settings.md +++ b//AmazonRDS/latest/UserGuide/USER_ModifyInstance.Settings.md @@ -75 +75 @@ For more information, see [Provisioned IOPS SSD storage](./CHAP_Storage.html#USE -**Public access** **Publicly accessible** to give the DB instance a public IP address, meaning that it's accessible outside the VPC. To be publicly accessible, the DB instance also has to be in a public subnet in the VPC. **Not publicly accessible** to make the DB instance 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 instance from outside its VPC, the DB instance must be publicly accessible. Also, access must be granted using the inbound rules of the DB instance's security group. In addition, 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 instance isn't publicly accessible, you can also 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` | The change occurs immediately. This setting ignores the apply immediately setting. | Downtime doesn't occur during this change. | All DB engines +**Public access** **Publicly accessible** to give the DB instance a public IP address, meaning that it's accessible outside the VPC. To be publicly accessible, the DB instance also has to be in a public subnet in the VPC. **Not publicly accessible** to make the DB instance 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 instance from outside its VPC, the DB instance must be publicly accessible. Also, access must be granted using the inbound rules of the DB instance's security group. In addition, 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 instance isn't publicly accessible, you can also 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` | The change occurs immediately. This setting ignores the apply immediately setting. | Downtime doesn't occur during this change. | All DB engines