Terraform AWS ACM

Quick start

module "acm" {
  source  = "nis2.compliance.tf/terraform-aws-modules/acm/aws"
  version = "~> 6.3"

  # ... your arguments here
}

module "acm" {
  source  = "nistcsf.compliance.tf/terraform-aws-modules/acm/aws"
  version = "~> 6.3"

  # ... your arguments here
}

module "acm" {
  source  = "acscism2023.compliance.tf/terraform-aws-modules/acm/aws"
  version = "~> 6.3"

  # ... your arguments here
}

module "acm" {
  source  = "awswellarchitected.compliance.tf/terraform-aws-modules/acm/aws"
  version = "~> 6.3"

  # ... your arguments here
}

module "acm" {
  source  = "pcidss.compliance.tf/terraform-aws-modules/acm/aws"
  version = "~> 6.3"

  # ... your arguments here
}

This module on the compliance.tf registry lists its versions, inputs and outputs. The Get Started guide and Registry Endpoints cover authentication and how to customize the module for your requirements.

Migration from upstream

Already using terraform-aws-modules? Change only the source URL:

module "acm" {
  source  = "terraform-aws-modules/acm/aws"
  version = "~> 6.3"
}

module "acm" {
  source  = "soc2.compliance.tf/terraform-aws-modules/acm/aws"
  version = "~> 6.3"
}

Same arguments. Same outputs. Controls are checked at terraform plan. The Migration Guide has the step-by-step version.

Reversibility

No lock-in. Switch back by reverting the source URL:

module "acm" {
  source  = "terraform-aws-modules/acm/aws"
}

Run terraform init -upgrade. Terraform state is unchanged: same resource addresses, same provider, no compliance.tf-specific resources. Controls you already applied remain in AWS.

Controls enforced

Up to 2 controls are checked at terraform plan when this module comes from a compliance.tf endpoint. Which ones are active depends on the endpoint; see Framework coverage.

Mapped compliance frameworks

Framework coverage

Which controls from this module are active under each framework endpoint. Your framework preferences choose the columns.