AWS AmazonRDS: Clarify DCL (GRANT/REVOKE) handling in blue/green deployments
Summary
Updates the blue/green deployment considerations: fixes parameter name formatting for recovery_min_apply_delay, removes the note that delayed replication is incompatible with major version upgrades, and expands the DCL limitation to include ALTER DEFAULT PRIVILEGES and to state that a detected DCL statement puts green databases into 'Replication degraded' and blocks switchover, requiring deletion and recreation of the deployment.
Security assessment
The change documents that privilege-management statements (GRANT, REVOKE, ALTER DEFAULT PRIVILEGES) are not replicated to the green environment and now cause a degraded state that blocks switchover. This is authorization-relevant guidance (privilege drift between blue and green), but it documents existing behavior rather than fixing a specific vulnerability, so medium severity.
Evidence
+Data control language (DCL) statements, such as `GRANT`, `REVOKE`, and `ALTER DEFAULT PRIVILEGES`, aren't replicated from the blue environment to the green environment. | If Amazon RDS PostgreSQL detects a DCL statement in the blue environment, your green databases enter a state of **Replication degraded** and switchover is blocked, the same as for a DDL change. You must delete the blue/green deployment and all green databases, then recreate it. A warning also appears in the PostgreSQL log. No configuration or API is available to change this behavior, because it is a limitation of the blue/green deployment process.
Diff
diff --git a/AmazonRDS/latest/UserGuide/blue-green-deployments-considerations.md b/AmazonRDS/latest/UserGuide/blue-green-deployments-considerations.md index af86849..3417585 100644 --- a//AmazonRDS/latest/UserGuide/blue-green-deployments-considerations.md +++ b//AmazonRDS/latest/UserGuide/blue-green-deployments-considerations.md @@ -113 +113 @@ The following limitations apply to RDS for PostgreSQL blue/green deployments tha - * Blue/Green deployments have the following limitations when configuring delayed replication in RDS for PostgreSQL: + * Blue/green deployments have the following limitations when configuring delayed replication in RDS for PostgreSQL: @@ -115 +115 @@ The following limitations apply to RDS for PostgreSQL blue/green deployments tha - * **Green source instance** — The `recovery_min_apply_delay parameter` is disregarded, even if configured in the parameter group. Any delay settings on the green source instance do not take effect. + * **Green source instance** – The `recovery_min_apply_delay` parameter is disregarded, even if configured in the parameter group. Any delay settings on the green source instance do not take effect. @@ -117,3 +117 @@ The following limitations apply to RDS for PostgreSQL blue/green deployments tha - * **Green replica instance** — The `recovery_min_apply_delay parameter` is fully supported and applied to the PostgreSQL configuration file. Delay settings function as expected during the switchover workflow. - - * Delayed replication isn't compatible with RDS Blue/Green deployments for major version upgrades. + * **Green replica instance** – The `recovery_min_apply_delay` parameter is fully supported and applied to the PostgreSQL configuration file. Delay settings function as expected during the switchover workflow. @@ -170 +168 @@ Data definition language (DDL) statements, such as `CREATE TABLE` and `CREATE SC -Data control language (DCL) statements, such as `GRANT` and `REVOKE`, aren't replicated from the blue environment to the green environment. | If Amazon RDS PostgreSQL detects an attempt to execute a DCL statement in the blue environment, you will see a warning message. There is no configuration or API available to change this behavior, as it is a limitation of the blue/green deployment process. +Data control language (DCL) statements, such as `GRANT`, `REVOKE`, and `ALTER DEFAULT PRIVILEGES`, aren't replicated from the blue environment to the green environment. | If Amazon RDS PostgreSQL detects a DCL statement in the blue environment, your green databases enter a state of **Replication degraded** and switchover is blocked, the same as for a DDL change. You must delete the blue/green deployment and all green databases, then recreate it. A warning also appears in the PostgreSQL log. No configuration or API is available to change this behavior, because it is a limitation of the blue/green deployment process.