compliance.tf
Terraform Modules for AWSDatabases, Caching & Analytics

Terraform AWS EMR

EMR clusters and instance groups with security configurations, encryption in transit and at rest, Kerberos, IAM roles, bootstrap actions, logging, and deployment in private subnets.

Controls enforced

These compliance controls are checked at terraform plan time.

Quick start

module "emr" {
  source  = "cfrpart11.compliance.tf/terraform-aws-modules/emr/aws"
  version = "1.0"

  # ... your arguments here
}
module "emr" {
  source  = "cisv80ig1.compliance.tf/terraform-aws-modules/emr/aws"
  version = "1.0"

  # ... your arguments here
}
module "emr" {
  source  = "ffiec.compliance.tf/terraform-aws-modules/emr/aws"
  version = "1.0"

  # ... your arguments here
}
module "emr" {
  source  = "hipaa.compliance.tf/terraform-aws-modules/emr/aws"
  version = "1.0"

  # ... your arguments here
}
module "emr" {
  source  = "nist800171.compliance.tf/terraform-aws-modules/emr/aws"
  version = "1.0"

  # ... your arguments here
}
module "emr" {
  source  = "nydfs23.compliance.tf/terraform-aws-modules/emr/aws"
  version = "1.0"

  # ... your arguments here
}
module "emr" {
  source  = "pcidss.compliance.tf/terraform-aws-modules/emr/aws"
  version = "1.0"

  # ... your arguments here
}
module "emr" {
  source  = "rbiitfnbfc.compliance.tf/terraform-aws-modules/emr/aws"
  version = "1.0"

  # ... your arguments here
}

See the Get Started guide and Registry Endpoints for details on how to customize the module for your requirements.

Migration from upstream

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

module "emr" {
  source  = "terraform-aws-modules/emr/aws"
  version = "1.0"
}
module "emr" {
  source  = "soc2.compliance.tf/terraform-aws-modules/emr/aws"
  version = "1.0"
}

Same arguments. Same outputs. Controls are checked at terraform plan. See the Migration Guide for step-by-step instructions.

Reversibility

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

module "emr" {
  source  = "terraform-aws-modules/emr/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.

Mapped compliance frameworks

11.300(b) Ensuring that identification code and password issuances are periodically checked, recalled, or revised (e.g., to cover such events as password aging)

3.3 Configure Data Access Control Lists

164.312(a)(1) Access control

1 controls from this module are active under NIST SP 800-171 Rev 2.

500.07 Access Privileges and Management

8.3.2: Strong cryptography is used to render all authentication factors unreadable during transmission and storage on all system components

8.I Basic Security Aspects

Framework coverage

Which controls from this module are active under each framework endpoint.

enforced by default · not activated by this endpoint

On this page

Ask AI about this

Help improve this page