AWS AmazonRDS documentation change
Summary
Added documentation about RDS Proxy and smart drivers support for Blue/Green Deployments, and added instructions for testing Green environment with RDS Proxy by creating a separate proxy instance.
Security assessment
The changes are operational improvements focusing on reducing downtime and providing testing guidance. No security vulnerabilities, patches, or incidents are mentioned. The addition of RDS Proxy support is a feature enhancement for deployment reliability, not a security fix.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.md b/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.md index 8cfa997cc..23899cb8f 100644 --- a//AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.md +++ b//AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.md @@ -14,0 +15,2 @@ Because the green environment is a copy of the topology of the production enviro +Amazon Aurora Blue/Green Deployments support Amazon RDS Proxy and smart drivers. These solutions reduce writer node upgrade downtime during switchover by detecting the topology change and redirecting connections to the new production environment without waiting for DNS propagation. + @@ -99 +101 @@ For information about modifying a DB cluster, see [Modifying an Amazon Aurora DB -During testing, we recommend that you keep your databases in the green environment read only. Enable write operations on the green environment with caution because they can result in replication conflicts. They can also result in unintended data in the production databases after switchover. To enable write operations for Aurora MySQL, set the `read_only` parameter to `0`, then reboot the DB instance. For Aurora PostgreSQL, set the `default_transaction_read_only` parameter to `off` at the session level. +During testing, we recommend that you keep your databases in the green environment read only. Enable write operations on the green environment with caution because they can result in replication conflicts. They can also result in unintended data in the production databases after switchover. To enable write operations for Aurora MySQL, set the `read_only` parameter to `0`, then reboot the DB instance. For Aurora PostgreSQL, set the `default_transaction_read_only` parameter to `off` at the session level. If you need to test your Green environment with Amazon RDS Proxy, you must create a new Amazon RDS Proxy and register the Green cluster with it. This allows you to test the Green environment independently without affecting your production Blue environment traffic. Delete the test proxy once testing is completed.