AWS Security ChangesHomeSearch

AWS AmazonRDS documentation change

Service: AmazonRDS · 2025-04-11 · Documentation low

File: AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-considerations.md

Summary

Added guidance about primary key requirements and REPLICA IDENTITY FULL usage for logical replication in blue/green deployments. Enhanced PostgreSQL documentation references.

Security assessment

Changes clarify replication configuration requirements but do not address specific security vulnerabilities or introduce security features.

Diff

diff --git a/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-considerations.md b/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-considerations.md
index ed80e76ec..1e1960db1 100644
--- a//AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-considerations.md
+++ b//AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-considerations.md
@@ -124 +124 @@ PostgreSQL has certain restrictions related to logical replication, which transl
-The following table describes logical replication limitations that apply to blue/green deployments for Aurora PostgreSQL.
+The following table describes logical replication limitations that apply to blue/green deployments for Aurora PostgreSQL. For more information, see [Restrictions](https://www.postgresql.org/docs/current/logical-replication-restrictions.html) in the PostgreSQL logical replication documentation.
@@ -132,3 +132 @@ Refreshing materialized views breaks replication. |  Refreshing materialized vie
-UPDATE and DELETE operations aren't permitted on tables that don't have a primary key. |  Before you create a blue/green deployment, make sure that all tables in the DB cluster have a primary key.  
-  
-For more information, see [Restrictions](https://www.postgresql.org/docs/current/logical-replication-restrictions.html) in the PostgreSQL logical replication documentation.
+UPDATE and DELETE operations aren't permitted on tables that don't have a primary key. |  Before you create a blue/green deployment, make sure that all tables have a primary key or use `REPLICA IDENTITY FULL`. However, only use `REPLICA IDENTITY FULL` if no primary or unique key exists, as it affects replication performance. For more information, see the [PostgreSQL documentation](https://www.postgresql.org/docs/current/logical-replication-restrictions.html).