Ensure EBS Volume is encrypted by KMS using a customer managed Key (CMK)

Error: AWS EBS Volume not encrypted using Customer Managed Key
Bridgecrew Policy ID: BC_AWS_GENERAL_109
Checkov Check ID: CKV_AWS_189
Severity: Low

AWS EBS Volume not encrypted using Customer Managed Key

Description

Amazon EBS automatically creates a unique AWS managed key in each Region where you store AWS resources. This KMS key has the alias alias/aws/ebs. By default, Amazon EBS uses this KMS key for encryption. Alternatively, you can specify a symmetric customer managed key that you created as the default KMS key for EBS encryption. Using your own KMS key gives you more flexibility, including the ability to create, rotate, and disable KMS keys.

Fix - Buildtime

Terraform

  • Resource: aws_ebs_volume
  • Attribute: kms_key_id - (Optional) The ARN for the KMS encryption key. When specifying kms_key_id, encrypted needs to be set to true. Note: Terraform must be running with credentials which have the GenerateDataKeyWithoutPlaintext permission on the specified KMS key as required by the EBS KMS CMK volume provisioning process to prevent a volume from being created and almost immediately deleted.
resource "aws_ebs_volume" "example" {
  availability_zone = "us-west-2a"
  size              = 40
+ kms_key_id = "ckv_kms"
  tags = {
    Name = "HelloWorld"
  }
}

Did this page help you?