AWS AmazonElastiCache: Document that encrypted SNS topics are unsupported for ElastiCache events
Summary
Replaces the SNS topic access policy requirement section (aws:SourceOwner vs aws:SourceAccount) with a statement that ElastiCache cannot publish to encrypted SNS topics (AWS managed or customer managed KMS keys), updates the prerequisites and troubleshooting steps accordingly, and notes that either aws:SourceAccount or aws:SourceOwner works in the topic policy.
Security assessment
The change documents a security-relevant limitation: event notifications cannot be delivered to KMS-encrypted SNS topics, so users must use an unencrypted topic (a trade-off affecting confidentiality of notification data) and must check TopicStatus to detect silent failures. It also relaxes the previously documented access-policy condition requirement, but no specific vulnerability or CVE is referenced, so this is medium-severity security documentation rather than a fix.
Evidence
+ElastiCache cannot publish to an encrypted Amazon SNS topic, whether the topic uses the AWS managed key for Amazon SNS or a customer managed key. 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. Use an unencrypted topic.
Diff
diff --git a/AmazonElastiCache/latest/dg/ECEvents.SNS.md b/AmazonElastiCache/latest/dg/ECEvents.SNS.md index b60a944..8a453c8 100644 --- a//AmazonElastiCache/latest/dg/ECEvents.SNS.md +++ b//AmazonElastiCache/latest/dg/ECEvents.SNS.md @@ -22 +22 @@ You can configure ElastiCache to send notifications for important cluster events -###### SNS topic access policy requirement +###### Encrypted Amazon SNS topics are not supported @@ -24,29 +24 @@ You can configure ElastiCache to send notifications for important cluster events -When you configure an Amazon SNS topic for ElastiCache notifications, the topic's access policy must use the `aws:SourceOwner` condition key, not `aws:SourceAccount`. Newly created Amazon SNS topics default to `aws:SourceAccount` in their access policy, which ElastiCache does not support for event notifications. - -If your Amazon SNS topic uses `aws:SourceAccount`, ElastiCache cannot publish notifications to the topic and automatically sets the topic status to _inactive_. Global Datastore failovers and other cluster operations can trigger this error. - -To ensure ElastiCache notifications work correctly, verify your Amazon SNS topic access policy includes the following statement: - - - { - "Statement": [ - { - "Sid": "AllowElastiCachePublish", - "Effect": "Allow", - "Principal": { - "AWS": "*" - }, - "Action": "SNS:Publish", - "Resource": "arn:aws:sns:region:account-id:topic-name", - "Condition": { - "StringEquals": { - "AWS:SourceOwner": "account-id" - } - } - } - ] - } - -If ElastiCache shows your Amazon SNS topic status as _inactive_ after a failover or other cluster operation, check the topic's access policy and replace `aws:SourceAccount` with `aws:SourceOwner`. Then re-enable the notification on the cluster with the `ModifyReplicationGroup` API operation or the console. - -For more information about these condition keys, see [aws:SourceAccount vs aws:SourceOwner](https://docs.aws.amazon.com/sns/latest/dg/sns-access-policy-use-cases.html#source-account-versus-source-owner) in the _Amazon SNS Developer Guide_. +ElastiCache cannot publish to an encrypted Amazon SNS topic, whether the topic uses the AWS managed key for Amazon SNS or a customer managed key. 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. Use an unencrypted topic. @@ -62 +34 @@ Before you configure Amazon SNS notifications for ElastiCache, verify the follow - * The Amazon SNS topic must not be encrypted with a customer managed AWS KMS key. ElastiCache does not support publishing notifications to Amazon SNS topics that are encrypted with customer managed AWS KMS keys. + * 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. @@ -104,0 +77,2 @@ Condition: `aws:SourceAccount` | Your AWS account ID | Restricts access to reque +The condition can use either `aws:SourceAccount` or `aws:SourceOwner`. The default access policy that Amazon SNS creates for a new topic also works without changes. + @@ -352,0 +327,2 @@ After configuring the Amazon SNS topic policy and adding the topic to your Elast + 4. To check the topic status, run `describe-cache-clusters` for each node and read `TopicStatus` in `NotificationConfiguration`. The `describe-replication-groups` command does not return it. + @@ -359,0 +336,5 @@ If you are not receiving Amazon SNS notifications from ElastiCache, check the fo +Topic encryption + + +If the topic status is inactive, check whether the topic is encrypted. ElastiCache sets an encrypted topic to inactive at the first notification. Use an unencrypted topic, and then turn notifications back on. + @@ -375,5 +355,0 @@ Check that the `aws:SourceAccount` value is your exact 12-digit AWS account ID. -KMS encryption - - -Verify that the Amazon SNS topic is not encrypted with a customer managed AWS KMS key. ElastiCache does not support publishing to topics with customer managed AWS KMS encryption. -