SNS topics should be encrypted at rest¶

To help protect data at rest, ensure that your AWS Simple Notification Service (AWS SNS) topics require encryption using AWS Key Management Service (AWS KMS).

How to fix¶

Attribute kms_master_key_id of aws_sns_topic must be non-empty.

Implementation options¶

Choose the option that matches how you manage Terraform. All options satisfy this control.

Option 1: Terraform AWS provider resources¶

If you manage resources directly, configure the relevant Terraform AWS provider resources to meet this control. See docs for the resources involved: aws_sns_topic.

resource "aws_sns_topic" "this" {
  kms_master_key_id = "alias/aws/sns"
  name              = "pofix-example-topic"
}

Which option should I choose?

Compliance.tf module (recommended): controls enforced by default and mapped to frameworks.
Open source module (terraform-aws-modules): compatible by design with compliance.tf. Same variable names for an easy, low-change migration path when you are ready.
Terraform AWS provider resources: manage Terraform resources directly.

Tool mappings¶

Use these identifiers to cross-reference this control across tools, reports, and evidence.

Compliance.tf (CTF) Control: sns_topic_encrypted_at_rest
AWS Config Managed Rule: SNS_ENCRYPTED_KMS
Checkov Check: CKV_AWS_26
Powerpipe Control: aws_compliance.control.sns_topic_encrypted_at_rest