AWS AmazonRDS documentation change
Summary
Updated documentation to replace 'AWS Direct Connect' with 'Direct Connect' in DB instance modification instructions
Security assessment
This is a branding terminology change (removing redundant 'AWS' prefix) with no impact on security guidance. The existing security recommendations about public accessibility and network configurations remain unchanged.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/Aurora.Modifying.md b/AmazonRDS/latest/AuroraUserGuide/Aurora.Modifying.md index b1beaad36..48757a058 100644 --- a//AmazonRDS/latest/AuroraUserGuide/Aurora.Modifying.md +++ b//AmazonRDS/latest/AuroraUserGuide/Aurora.Modifying.md @@ -301 +301 @@ Using the RDS API, call [ ModifyDBCluster](https://docs.aws.amazon.com/AmazonRDS -**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 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). | Using the AWS Management Console, Modifying a DB instance in a DB cluster. Using the AWS CLI, run [`modify-db-instance`](https://docs.aws.amazon.com/cli/latest/reference/rds/modify-db-instance.html) and set the `--publicly-accessible|--no-publicly-accessible` option. Using the RDS API, call [`ModifyDBInstance`](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_ModifyDBInstance.html) and set the `PubliclyAccessible` parameter. | Only the specified DB instance | An outage doesn't occur during this change. +**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 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). | Using the AWS Management Console, Modifying a DB instance in a DB cluster. Using the AWS CLI, run [`modify-db-instance`](https://docs.aws.amazon.com/cli/latest/reference/rds/modify-db-instance.html) and set the `--publicly-accessible|--no-publicly-accessible` option. Using the RDS API, call [`ModifyDBInstance`](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_ModifyDBInstance.html) and set the `PubliclyAccessible` parameter. | Only the specified DB instance | An outage doesn't occur during this change.