Kinesis streams should be encrypted with CMK¶

Ensure Kinesis streams are encrypted using CMK. Using KMS CMK, you gain full control over who can use the keys to access AWS Kinesis data (including the system metadata).

How to fix¶

Attribute kms_key_id of aws_kinesis_stream 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_kinesis_stream.

resource "aws_kinesis_stream" "this" {
  encryption_type  = "KMS"
  name             = "pofix-example-stream"
  retention_period = 168
  shard_count      = 1

  kms_key_id = "arn:aws:kms:us-east-1:123456789012:key/12345678-1234-1234-1234-123456789012"
}

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: kinesis_stream_encrypted_with_kms_cmk
Checkov Check: CKV_AWS_185
Powerpipe Control: aws_compliance.control.kinesis_stream_encrypted_with_kms_cmk