SageMaker models should be in a VPC¶

Manage access to the AWS Cloud by ensuring SageMaker models are within an AWS Virtual Private Cloud (AWS VPC).

How to fix¶

Attribute vpc_config[0].security_group_ids of aws_sagemaker_model 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_model.

resource "aws_sagemaker_model" "this" {
  execution_role_arn = "arn:aws:iam::123456789012:role/example-role"

  vpc_config {
    security_group_ids = ["sg-abc12345"]
    subnets            = ["subnet-abc123", "subnet-def456"]
  }
}

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_model_in_vpc
AWS Config Managed Rule: SAGEMAKER_MODEL_IN_VPC
Powerpipe Control: aws_compliance.control.sagemaker_model_in_vpc