SNS topic is not encrypted at rest
- Severity
- Low
- Service
- SNS
- Check ID
- SNS_NOT_ENCRYPTED
What this check finds
The topic has no KMS key, so messages are stored without server-side encryption while SNS holds them.
Passing looks like: SNS topics encrypted at rest.
How to fix it
Enable server-side encryption on the topic with an AWS managed (alias/aws/sns) or customer managed KMS key.
AWS CLI
aws sns set-topic-attributes --topic-arn TOPIC_ARN --attribute-name KmsMasterKeyId --attribute-value alias/aws/sns
Names in capitals are placeholders for your own resource. Review a command before you run it.
Compliance controls it is evidence for
A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works
| Framework | Controls |
|---|---|
| NIST SP 800-53 Rev5 (Moderate) |
|
| NIST Cybersecurity Framework 2.0 |
|
| ISO/IEC 27001:2022 Annex A |
|
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs