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.
Quick start
module "emr" {
source = "fedrampmoderate.compliance.tf/terraform-aws-modules/emr/aws"
version = "~> 3.3"
# ... your arguments here
}module "emr" {
source = "nist800171.compliance.tf/terraform-aws-modules/emr/aws"
version = "~> 3.3"
# ... your arguments here
}module "emr" {
source = "nist80053.compliance.tf/terraform-aws-modules/emr/aws"
version = "~> 3.3"
# ... your arguments here
}module "emr" {
source = "pcidss.compliance.tf/terraform-aws-modules/emr/aws"
version = "~> 3.3"
# ... your arguments here
}module "emr" {
source = "awswellarchitected.compliance.tf/terraform-aws-modules/emr/aws"
version = "~> 3.3"
# ... your arguments here
}module "emr" {
source = "cfrpart11.compliance.tf/terraform-aws-modules/emr/aws"
version = "~> 3.3"
# ... your arguments here
}module "emr" {
source = "cisv80ig1.compliance.tf/terraform-aws-modules/emr/aws"
version = "~> 3.3"
# ... your arguments here
}module "emr" {
source = "eugmpannex11.compliance.tf/terraform-aws-modules/emr/aws"
version = "~> 3.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 "emr" {
source = "terraform-aws-modules/emr/aws"
version = "~> 3.3"
}module "emr" {
source = "soc2.compliance.tf/terraform-aws-modules/emr/aws"
version = "~> 3.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 "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.
Controls enforced
Up to 5 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
| Clause | Controls from this module |
|---|---|
| AC-4: Information Flow Enforcement | |
| AU-6(1)(3) | |
| Audit Record Retention (AU-11) | |
| Information Handling and Retention (SI-12) | |
| Protection of Audit Information (AU-9) | |
| Protection of Information at Rest (SC-28) | |
| SC-7: Boundary Protection |
| Clause | Controls from this module |
|---|---|
| 3.1.3: Control the flow of CUI in accordance with approved authorizations. | |
| 3.13.11 Employ FIPS-validated cryptography when used to protect the confidentiality of CUI | |
| 3.13.16: Protect the confidentiality of CUI at rest. | |
| 3.13.1: Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. | |
| 3.3.1: Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity | |
| 3.3.8: Protect audit information and audit logging tools from unauthorized access, modification, and deletion. | |
| 3.6.1 Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities | |
| 3.6.2 Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization |
| Clause | Controls from this module |
|---|---|
| AC-16(b) | |
| AU-11(1) Long-Term Retrieval Capability | |
| AU-12(1) System-Wide And Time-Correlated Audit Trial | |
| AU-12(2) Standardized Formats | |
| AU-12(3) Changes By Authorized Individuals | |
| AU-14(a) | |
| AU-14(b) | |
| AU-6(3) Correlate Audit Record Repositories | |
| AU-6(4) Central Review And Analysis | |
| AU-6(6) Correletion With Physical Monitoring | |
| AU-6(9) Correletion With From Nontechnical Sources | |
| AU-9(3) Cryptographic Protection | |
| Audit Record Retention (AU-11) | |
| CA-7(b) | |
| CP-9(d) | |
| Continuous Monitoring Strategy (PM-31) | |
| Information Management and Retention (SI-12) | |
| Non-Repudiation (AU-10) | |
| PM-14(a)(1) | |
| PM-14(b) | |
| PM-21(b) | |
| SC-13(a) | |
| SC-28(1): Cryptographic Protection | |
| SC-28(2) Offline Storage | |
| SC-7(13): Isolation Of Security Tools, Mechanisms, And Support Components | |
| SC-7: Boundary Protection | |
| SC-8(3) Cryptographic Protection For Message Externals | |
| SC-8(4) Conceal Or Ramdomize Communications | |
| SI-19(4) Removal, Masking, Encryption, Hashing, Or Replacement Of Direct Identifiers | |
| SI-4(17) Integrated Situational Awareness |
| Clause | Controls from this module |
|---|---|
| 1.3.1: Network access to and from the cardholder data environment is restricted. | |
| 1.3.2: Network access to and from the cardholder data environment is restricted. | |
| 10.3.2: Audit logs are protected from destruction and unauthorized modifications. | |
| 10.3.3: Audit log files, including those for externalfacing technologies, are promptly backed up to a secure, central, internal log server(s) or other media that is difficult to modify | |
| 10.3.4: File integrity monitoring or change-detection mechanisms is used on audit logs to ensure that existing log data cannot be changed without generating alerts | |
| 10.5.1: Retain audit log history for at least 12 months, with at least the most recent three months immediately available for analysis | |
| 3.2.1: Storage of account data is kept to a minimum. | |
| 3.3.1.1: Sensitive authentication data (SAD) is not stored after authorization. | |
| 3.3.1.3: Sensitive authentication data (SAD) is not stored after authorization. | |
| 3.3.2: Sensitive authentication data (SAD) is not stored after authorization. | |
| 3.3.3: Sensitive authentication data (SAD) is not stored after authorization. | |
| 3.5.1: Primary account number (PAN) is secured wherever it is stored. | |
| 5.3.4: Anti-malware mechanisms and processes are active, maintained, and monitored. | |
| 8.3.2: Strong cryptography is used to render all authentication factors unreadable during transmission and storage on all system components | |
| A1.2.3: Processes or mechanisms are implemented for reporting and addressing suspected or confirmed security incidents and vulnerabilities |
| Clause | Controls from this module |
|---|---|
| Data protection | |
| Identity and access management |
| Clause | Controls from this module |
|---|---|
| 11.10(c) Protection of records to enable their accurate and ready retrieval throughout the records retention period | |
| 11.10(d) Limiting system access to authorized individuals | |
| 11.10(e) Use of secure, computer-generated, time-stamped audit trails to independently record the date and time of operator entries and actions that create, modify, or delete electronic records | |
| 11.30 Controls for open systems |
| Clause | Controls from this module |
|---|---|
| 4.4: Implement and Manage a Firewall on Servers | |
| 8.1: Establish and Maintain an Audit Log Management Process |
| Clause | Controls from this module |
|---|---|
| 12.1 Security | |
| 17 Archiving | |
| 7.1 Data Storage - Damage Protection |
Framework coverage
Which controls from this module are active under each framework endpoint. Your framework preferences choose the columns.
5 controls enforced with a source URL change.