SageMaker endpoint configuration encryption should be enabled¶

To help protect data at rest, ensure encryption with AWS Key Management Service (AWS KMS) is enabled for your SageMaker endpoint.

How to fix¶

Attribute kms_key_arn of aws_sagemaker_endpoint_configuration 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_sagemaker_endpoint_configuration.

resource "aws_sagemaker_endpoint_configuration" "this" {
  production_variants {
    initial_instance_count = 2
    instance_type          = "ml.t2.medium"
    model_name             = "pofix-example-model"
    variant_name           = "AllTraffic"
  }

  kms_key_arn = "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: sagemaker_endpoint_configuration_encryption_at_rest_enabled
Checkov Check: CKV_AWS_98
Powerpipe Control: aws_compliance.control.sagemaker_endpoint_configuration_encryption_at_rest_enabled