AWS AmazonRDS documentation change
Summary
Updated instructions for enabling write operations in RDS MySQL green environment by correcting `read_only` parameter value and removing reboot requirement
Security assessment
Clarifies secure procedure to prevent unintended writes during blue/green deployments but doesn't address a specific vulnerability
Diff
diff --git a/AmazonRDS/latest/UserGuide/blue-green-deployments-overview.md b/AmazonRDS/latest/UserGuide/blue-green-deployments-overview.md index e9a68054e..d6cdeda8e 100644 --- a//AmazonRDS/latest/UserGuide/blue-green-deployments-overview.md +++ b//AmazonRDS/latest/UserGuide/blue-green-deployments-overview.md @@ -97 +97 @@ For information about modifying a DB instance, see [Modifying an Amazon RDS DB i -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 RDS for MySQL, set the `read_only` parameter to `0`, then reboot the DB instance. For RDS for PostgreSQL deployments that use logical replication, set the `default_transaction_read_only` parameter to `off` at the session level. For those that use physical replication, you can't enable write operations on the green environment. +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 RDS for MySQL, set the `read_only` parameter to `1`, and wait for the parameter group to synchronize. Since `read_only` is a dynamic parameter, so a reboot isn't required. Once synchronized, change `read_only` from `1` to `0`. For RDS for PostgreSQL deployments that use logical replication, set the `default_transaction_read_only` parameter to `off` at the session level. For those that use physical replication, you can't enable write operations on the green environment.