AWS AmazonRDS documentation change
Summary
Updated Direct Connect service reference from 'AWS Direct Connect' to 'Direct Connect'
Security assessment
Branding/style change for Direct Connect service name. Security guidance about public access requirements and VPN usage remains unchanged.
Diff
diff --git a/AmazonRDS/latest/UserGuide/USER_CreateDBInstance.Settings.md b/AmazonRDS/latest/UserGuide/USER_CreateDBInstance.Settings.md index cac20be6f..c827ce812 100644 --- a//AmazonRDS/latest/UserGuide/USER_CreateDBInstance.Settings.md +++ b//AmazonRDS/latest/UserGuide/USER_CreateDBInstance.Settings.md @@ -126 +126 @@ For more information, see [Amazon RDS DB instance storage](./CHAP_Storage.html). -**Public access** | **Yes** 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. **No** 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 of 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, 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` | All +**Public access** | **Yes** 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. **No** 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 of 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, 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` | All