AWS msk medium security documentation change
Summary
Updated IAM role configuration instructions, removing automatic attachment of AWSSecretsManagerClientReadOnlyAccess policy and requiring manual addition of Secrets Manager/KMS permissions.
Security assessment
Explicit removal of broad Secrets Manager policy attachment (replaced with scoped inline policies) indicates a least-privilege fix. This prevents over-permissioning of replicator roles, reducing risk of unintended secret access. Direct reference to SASL/SCRAM and CMK-encrypted credentials confirms security context.
Diff
diff --git a/msk/latest/developerguide/msk-replicator-external-prereqs.md b/msk/latest/developerguide/msk-replicator-external-prereqs.md index 92cc12b7b..aa3bc821a 100644 --- a//msk/latest/developerguide/msk-replicator-external-prereqs.md +++ b//msk/latest/developerguide/msk-replicator-external-prereqs.md @@ -13 +13 @@ Create an IAM execution roleConfigure SASL/SCRAM user and ACL permissionsConfigu -Create an IAM role with a trust policy for `kafka.amazonaws.com`. Attach the `AWSMSKReplicatorExecutionRole` and `AWSSecretsManagerClientReadOnlyAccess` managed policies. +Create an IAM role with a trust policy for `kafka.amazonaws.com`. Attach the `AWSMSKReplicatorExecutionRole` managed policy. The managed policy grants the cluster-, topic-, and consumer-group-level Kafka permissions the Replicator needs, but it does _not_ include AWS Secrets Manager or AWS KMS permissions, which are required for SASL/SCRAM authentication and CMK-encrypted credentials. For the inline policy snippets to add, see [Additional SER permissions for SASL/SCRAM and customer managed keys](./msk-replicator-ser-additional-perms.html).