AWS AmazonRDS documentation change
Summary
Updated documentation to replace 'AWS Direct Connect' with 'Direct Connect' in public access configuration guidance
Security assessment
The change is a minor terminology update (branding consistency for Direct Connect service) with no alteration to security implications. The documentation continues to emphasize proper network isolation practices but does not address a new vulnerability or security feature.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/Aurora.CreateInstance.md b/AmazonRDS/latest/AuroraUserGuide/Aurora.CreateInstance.md index 24ce25b44..d9a0a4b69 100644 --- a//AmazonRDS/latest/AuroraUserGuide/Aurora.CreateInstance.md +++ b//AmazonRDS/latest/AuroraUserGuide/Aurora.CreateInstance.md @@ -492 +492 @@ You can't change the master user name after the DB cluster is created. | Using -**Public access** | Choose **Publicly accessible** to give the DB cluster a public IP address, or choose **Not publicly accessible**. The instances in your DB cluster can be a mix of both public and private DB instances. For more information about hiding instances from public access, see [Hiding a DB cluster in a VPC from the internet](./USER_VPC.WorkingWithRDSInstanceinaVPC.html#USER_VPC.Hiding). To connect to a DB instance from outside of its Amazon VPC, the DB instance must be publicly accessible, access must be granted using the inbound rules of the DB instance'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 instance is 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). | Set this value for every DB instance in your Aurora cluster. Using the AWS CLI, run [`create-db-instance`](https://docs.aws.amazon.com/cli/latest/reference/rds/create-db-instance.html) and set the `--publicly-accessible | --no-publicly-accessible` option. Using the RDS API, call [`CreateDBInstance`](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_CreateDBInstance.html) and set the `PubliclyAccessible` parameter. +**Public access** | Choose **Publicly accessible** to give the DB cluster a public IP address, or choose **Not publicly accessible**. The instances in your DB cluster can be a mix of both public and private DB instances. For more information about hiding instances from public access, see [Hiding a DB cluster in a VPC from the internet](./USER_VPC.WorkingWithRDSInstanceinaVPC.html#USER_VPC.Hiding). To connect to a DB instance from outside of its Amazon VPC, the DB instance must be publicly accessible, access must be granted using the inbound rules of the DB instance'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 instance is 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). | Set this value for every DB instance in your Aurora cluster. Using the AWS CLI, run [`create-db-instance`](https://docs.aws.amazon.com/cli/latest/reference/rds/create-db-instance.html) and set the `--publicly-accessible | --no-publicly-accessible` option. Using the RDS API, call [`CreateDBInstance`](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_CreateDBInstance.html) and set the `PubliclyAccessible` parameter.