AWS AmazonRDS: Grant rds_replication role instead of ALTER USER ... REPLICATION
Summary
Replaces the broad 'ALTER USER replication_user_name WITH REPLICATION' statement with 'GRANT rds_replication TO replication_user_name;' in the IAM authentication/logical replication setup steps.
Security assessment
The change swaps a blanket PostgreSQL REPLICATION user attribute for an AWS-managed, purpose-scoped role grant, which is a least-privilege hardening of replication permissions documented for users. It is guidance/permission-scoping rather than a patched vulnerability, so medium severity.
Evidence
+ GRANT rds_replication TO replication_user_name;
Diff
diff --git a/AmazonRDS/latest/UserGuide/PostgreSQL.Concepts.General.FeatureSupport.IAMLogicalReplication.md b/AmazonRDS/latest/UserGuide/PostgreSQL.Concepts.General.FeatureSupport.IAMLogicalReplication.md index f61c140..880d6e3 100644 --- a//AmazonRDS/latest/UserGuide/PostgreSQL.Concepts.General.FeatureSupport.IAMLogicalReplication.md +++ b//AmazonRDS/latest/UserGuide/PostgreSQL.Concepts.General.FeatureSupport.IAMLogicalReplication.md @@ -77 +77 @@ The following SQL commands grant the necessary roles to enable IAM authenticatio - ALTER USER replication_user_name WITH REPLICATION; + GRANT rds_replication TO replication_user_name;