Terraform AWS EC2 Instance
EC2 instances with IAM roles, EBS encryption, IMDSv2, security groups, detailed monitoring, user data, placement options, and optional Elastic IPs or attached volumes.
Quick start
module "ec2-instance" {
source = "cfrpart11.compliance.tf/terraform-aws-modules/ec2-instance/aws"
version = "~> 6.4"
# ... your arguments here
}module "ec2-instance" {
source = "eugmpannex11.compliance.tf/terraform-aws-modules/ec2-instance/aws"
version = "~> 6.4"
# ... your arguments here
}module "ec2-instance" {
source = "nist800171.compliance.tf/terraform-aws-modules/ec2-instance/aws"
version = "~> 6.4"
# ... your arguments here
}module "ec2-instance" {
source = "pcidss.compliance.tf/terraform-aws-modules/ec2-instance/aws"
version = "~> 6.4"
# ... your arguments here
}module "ec2-instance" {
source = "cisv80ig1.compliance.tf/terraform-aws-modules/ec2-instance/aws"
version = "~> 6.4"
# ... your arguments here
}module "ec2-instance" {
source = "fedrampmoderate.compliance.tf/terraform-aws-modules/ec2-instance/aws"
version = "~> 6.4"
# ... your arguments here
}module "ec2-instance" {
source = "nist80053.compliance.tf/terraform-aws-modules/ec2-instance/aws"
version = "~> 6.4"
# ... your arguments here
}module "ec2-instance" {
source = "soc2.compliance.tf/terraform-aws-modules/ec2-instance/aws"
version = "~> 6.4"
# ... 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 "ec2-instance" {
source = "terraform-aws-modules/ec2-instance/aws"
version = "~> 6.4"
}module "ec2-instance" {
source = "soc2.compliance.tf/terraform-aws-modules/ec2-instance/aws"
version = "~> 6.4"
}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 "ec2-instance" {
source = "terraform-aws-modules/ec2-instance/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 11 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 |
|---|---|
| 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.10(g) Use of authority checks to ensure that only authorized individuals can use the system, electronically sign a record, access the operation or computer system input or output device, alter a record, or perform the operation at hand | |
| 11.30 Controls for open systems |
| Clause | Controls from this module |
|---|---|
| 12.1 Security | |
| 4.8 Validation - Data Transfer | |
| 7.1 Data Storage - Damage Protection |
| Clause | Controls from this module |
|---|---|
| 3.1.1 Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems) | |
| 3.1.14 Route remote access via managed access control points | |
| 3.1.2: Limit system access to the types of transactions and functions that authorized users are permitted to execute. | |
| 3.1.3 Control the flow of CUI in accordance with approved authorizations | |
| 3.1.3: Control the flow of CUI in accordance with approved authorizations. | |
| 3.12.4 Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships with or connections to other systems | |
| 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.13.2 Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems | |
| 3.13.5 Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks | |
| 3.5.10 Store and transmit only cryptographically-protected passwords |
| 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.2.1.1: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events. | |
| 10.4.1.1: Audit logs are reviewed to identify anomalies or suspicious activity. | |
| 10.4.1: Audit logs are reviewed to identify anomalies or suspicious activity. | |
| 10.4.2: Audit logs are reviewed to identify anomalies or suspicious activity. | |
| 10.6.3: Time-synchronization mechanisms support consistent time settings across all systems. | |
| 10.7.1: Failures of critical security control systems are detected, reported, and responded to promptly. | |
| 10.7.2: Failures of critical security control systems are detected, reported, and responded to promptly. | |
| 11.5.2: A change-detection mechanism (for example, file integrity monitoring tools) is deployed | |
| 3.5.1: Primary account number (PAN) is secured wherever it is stored. | |
| 7.2.1: Access to system components and data is appropriately defined and assigned. | |
| 7.2.2: Access to system components and data is appropriately defined and assigned. | |
| 7.2.5: Access to system components and data is appropriately defined and assigned. | |
| 7.3.1: Access to system components and data is managed via an access control system(s). | |
| 7.3.2: Access to system components and data is managed via an access control system(s). | |
| 7.3.3: Access to system components and data is managed via an access control system(s). | |
| 8.2.7: User identification and related accounts for users and administrators are strictly managed throughout an accounts lifecycle. | |
| 8.2.8: If a user session has been idle for more than 15 minutes, the user is required to re-authenticate to re-activate the terminal or session | |
| 8.3.11: Where authentication factors such as physical or logical security tokens, smart cards, or certificates | |
| 8.3.2: Strong cryptography is used to render all authentication factors unreadable during transmission and storage on all system components | |
| 8.3.4: Strong authentication for users and administrators is established and managed. | |
| A3.3.1: PCI DSS is incorporated into business-as-usual (BAU) activities. | |
| A3.5.1: Suspicious events are identified and responded to. |
| Clause | Controls from this module |
|---|---|
| 11.3 Protect Recovery Data | |
| 11.4 Establish and Maintain an Isolated Instance of Recovery Data | |
| 3.3 Configure Data Access Control Lists | |
| 4.4: Implement and Manage a Firewall on Servers | |
| 4.6 Securely Manage Enterprise Assets and Software |
| Clause | Controls from this module |
|---|---|
| AC-17(1) Automated Monitoring/Control | |
| AC-21(b) | |
| AC-4: Information Flow Enforcement | |
| Access Enforcement (AC-3) | |
| Baseline Configuration (CM-2) | |
| Boundary Protection (SC-7) | |
| CA-7(a)(b) | |
| Denial Of Service Protection (SC-5) | |
| Information Flow Enforcement (AC-4) | |
| Least Privilege (AC-6) | |
| Protection of Information at Rest (SC-28) | |
| SC-7(3) Access Points | |
| SC-7: Boundary Protection | |
| SI-4(2) Automated Tools For Real-Time Analysis | |
| SI-4(4) Inbound and Outbound Communications Traffic | |
| SI-4(5) System-Generated Alerts | |
| SI-4(a)(b)(c) |
| Clause | Controls from this module |
|---|---|
| AC-17(1) Monitoring And Control | |
| AC-17(10) Authenticate Remote Commands | |
| AC-17(4)(a) | |
| AC-17(9) Disconnect Or Disable Access | |
| AC-17(b) | |
| AC-2(6) Dynamic Privilege Management | |
| AC-3(12)(a) | |
| AC-3(13) Attribute-Based Access Control | |
| AC-3(15)(a) | |
| AC-3(15)(b) | |
| AC-3(3) Mandatory Access Control | |
| AC-3(3)(a) | |
| AC-3(3)(b)(1) | |
| AC-3(3)(c) | |
| AC-3(4)(a) | |
| AC-3(4)(b) | |
| AC-3(4)(c) | |
| AC-3(4)(d) | |
| AC-3(4)(e) | |
| AC-3(4): Discretionary Access Control | |
| AC-3(7): Role-Based Access Control | |
| AC-3(8) Revocation Of Access Authorizations | |
| AC-4(21) Physical Or Logical Separation Of Infomation Flows | |
| AC-4(28) Linear Filter Pipelines | |
| AC-6: Least Privilege | |
| AU-9(3) Cryptographic Protection | |
| Access Control Decisions (AC-24) | |
| Access Enforcement (AC-3) | |
| CM-5(1)(a) | |
| CM-6(a) | |
| CM-9(b) | |
| CP-9(d) | |
| IA-3(4): Device Attestation | |
| IA-9: Service Identification And Authentication | |
| Media Access (MP-2) | |
| SA-8(20): Secure Metadata Management | |
| SC-13(a) | |
| SC-23(3) Unique System-Generated Session Identifiers | |
| SC-28(1): Cryptographic Protection | |
| SC-7(11) Restrict Incoming communications Traffic | |
| SC-7(12) Host-Based Protection | |
| SC-7(13): Isolation Of Security Tools, Mechanisms, And Support Components | |
| SC-7(16) Prevent Discovery Of System Components | |
| SC-7(2) Public Access | |
| SC-7(20) Prevent Discovery Of System Components | |
| SC-7(21) Isolation Of System Components | |
| SC-7(24)(b) | |
| SC-7(25) Unclassified National Security System Connections | |
| SC-7(26) Classified National Security System Connections | |
| SC-7(27) Unclassified Non-National Security System Connections | |
| SC-7(28): Connections To Public Networks | |
| SC-7(3) Access Points | |
| SC-7(7) Split Tunneling For Remote Devices | |
| SC-7(9)(a) | |
| SC-7(a) | |
| SC-7(b) | |
| SC-7(c) | |
| 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 | |
| Thin Nodes (SC-25) |
| Clause | Controls from this module |
|---|---|
| A1.2 The entity authorizes, designs, develops or acquires, implements, operates, approves, maintains, and monitors environmental protections, software, data back-up processes, and recovery infrastructure to meet its objectives | |
| CC6.1 The entity implements logical access security software, infrastructure, and architectures over protected information assets to protect them from security events to meet the entity's objectives | |
| CC6.6: The entity implements logical access security measures to protect against threats from sources outside its system boundaries. | |
| CC7.2: The entity monitors system components and the operation of those components for anomalies that are indicative of malicious acts, natural disasters, and errors affecting the entity's ability to meet its objectives; anomalies are analyzed to determine whether they represent security events. | |
| PI1.5 Stored data is maintained complete, accurate, and protected from unauthorized modification to meet the entity's processing integrity commitments and system requirements |
Framework coverage
Which controls from this module are active under each framework endpoint. Your framework preferences choose the columns.
| Control | PCI DSS v4.0 | SOC 2 |
|---|---|---|
| Attached EBS volumes should have encryption enabled | Enforced | Enforced |
| EC2 instances should have attached EBS volumes marked for deletion on termination | Not active | Not active |
| EC2 instances should have detailed monitoring enabled | Enforced | Enforced |
| EC2 instances should have EBS optimization enabled | Not active | Enforced |
| EC2 instances should have IAM profile attached | Enforced | Not active |
| EC2 instances should not use key pairs in running state | Enforced | Not active |
| EC2 instances should not have a public IP address | Enforced | Enforced |
| EC2 instances should have termination protection enabled | Not active | Enforced |
| EC2 instances should use IMDSv2 | Enforced | Enforced |
| VPC Security groups should only allow unrestricted incoming traffic for authorized ports | Enforced | Not active |
| VPC security groups should restrict ingress from 0.0.0.0/0 or ::/0 to cassandra ports 7199 or 9160 or 8888 | Enforced | Not active |
Known Terraform limitations
Separately from the controls above, some things people ask this module for cannot be implemented by any module in any registry: they are limits of Terraform itself. Known limitations for this module lists the recurring ones: what causes each, the native workaround in full, and, where one exists, the opt-in Operational Rule that removes the need for a fork.