AWS AmazonElastiCache: Clarify SNS topic must be unencrypted and access policy requirement
Summary
Updates ElastiCache SNS notification docs: states the SNS topic must be unencrypted (AWS managed or customer managed key both unsupported), revises behavior when an encrypted topic is attached (status flips to inactive on first notification), and relaxes the access-policy guidance by removing the aws:SourceOwner condition-key requirement in favor of a general 'must allow ElastiCache to publish' statement.
Security assessment
The changed line documents an encryption constraint on SNS notification topics and associated topic access-policy requirements, which is security-relevant configuration guidance, but there is no indication it addresses a specific vulnerability, CVE, or incident.
Evidence
+ * The Amazon SNS topic must be unencrypted. ElastiCache cannot publish to a topic that is encrypted with the AWS managed key for Amazon SNS or with a customer managed key.
Diff
diff --git a/AmazonElastiCache/latest/dg/ElastiCacheSNS.md b/AmazonElastiCache/latest/dg/ElastiCacheSNS.md index c9f88b5..5aece26 100644 --- a//AmazonElastiCache/latest/dg/ElastiCacheSNS.md +++ b//AmazonElastiCache/latest/dg/ElastiCacheSNS.md @@ -23 +23 @@ Notifications are published to a specified Amazon SNS _topic_. The following are - * The Amazon SNS topic you are publishing to cannot be encrypted. + * The Amazon SNS topic must be unencrypted. ElastiCache cannot publish to a topic that is encrypted with the AWS managed key for Amazon SNS or with a customer managed key. @@ -27 +27 @@ Notifications are published to a specified Amazon SNS _topic_. The following are -It is possible to attach an encrypted (at-rest) Amazon SNS topic to the cluster. However, the status of the topic from the ElastiCache console will show as inactive, which effectively disassociates the topic from the cluster when ElastiCache pushes messages to the topic. +You can attach an encrypted topic to a cluster, and its status shows as active. When ElastiCache sends the first notification, it sets the topic status to inactive and does not emit an event. @@ -31 +31 @@ It is possible to attach an encrypted (at-rest) Amazon SNS topic to the cluster. - * The Amazon SNS topic's access policy must use the `aws:SourceOwner` condition key. If the policy uses `aws:SourceAccount` (which is now the default for newly created topics), ElastiCache cannot publish to the topic and automatically sets the topic status to _inactive_. For the required policy configuration, see [Managing ElastiCache Amazon SNS notifications](./ECEvents.SNS.html). + * The Amazon SNS topic's access policy must allow ElastiCache to publish to the topic. For the required policy configuration, see [Managing ElastiCache Amazon SNS notifications](./ECEvents.SNS.html).