Kinesis streams should have server side encryption enabled¶

Enable server side encryption (SSE) of your AWS Kinesis Server data at rest, in order to protect your data and metadata from breaches or unauthorized access, and fulfill compliance requirements for data-at-rest encryption within your organization.

How to fix¶

Attribute encryption_type of aws_kinesis_stream must be "KMS".

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" {
  kms_key_id       = "arn:aws:kms:us-east-1:123456789012:key/12345678-1234-1234-1234-123456789012"
  name             = "pofix-example-stream"
  retention_period = 168
  shard_count      = 1

  encryption_type = "KMS"
}

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_server_side_encryption_enabled
AWS Config Managed Rule: KINESIS_STREAM_ENCRYPTED
Checkov Check: CKV_AWS_43
Powerpipe Control: aws_compliance.control.kinesis_stream_server_side_encryption_enabled