Terraform AWS RDS
RDS instances with subnet groups, security groups, storage encryption, automated backups, maintenance windows, performance insights, IAM authentication, and log exports.
Quick start
module "rds" {
source = "hipaa.compliance.tf/terraform-aws-modules/rds/aws"
version = "~> 7.2"
# ... your arguments here
}module "rds" {
source = "nist800171.compliance.tf/terraform-aws-modules/rds/aws"
version = "~> 7.2"
# ... your arguments here
}module "rds" {
source = "nist80053.compliance.tf/terraform-aws-modules/rds/aws"
version = "~> 7.2"
# ... your arguments here
}module "rds" {
source = "cisacyberessentials.compliance.tf/terraform-aws-modules/rds/aws"
version = "~> 7.2"
# ... your arguments here
}module "rds" {
source = "fedrampmoderate.compliance.tf/terraform-aws-modules/rds/aws"
version = "~> 7.2"
# ... your arguments here
}module "rds" {
source = "ffiec.compliance.tf/terraform-aws-modules/rds/aws"
version = "~> 7.2"
# ... your arguments here
}module "rds" {
source = "soc2.compliance.tf/terraform-aws-modules/rds/aws"
version = "~> 7.2"
# ... your arguments here
}module "rds" {
source = "cfrpart11.compliance.tf/terraform-aws-modules/rds/aws"
version = "~> 7.2"
# ... 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 "rds" {
source = "terraform-aws-modules/rds/aws"
version = "~> 7.2"
}module "rds" {
source = "soc2.compliance.tf/terraform-aws-modules/rds/aws"
version = "~> 7.2"
}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 "rds" {
source = "terraform-aws-modules/rds/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 19 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 |
|---|---|
| 164.308(a)(1)(ii)(B) Risk Management | |
| 164.308(a)(4)(i) Information access management | |
| 164.308(a)(4)(ii)(A) Isolating health care clearinghouse functions | |
| 164.308(a)(7)(i) Contingency plan | |
| 164.308(a)(7)(ii)(A) Data backup plan | |
| 164.308(a)(7)(ii)(B) Disaster recovery plan | |
| 164.308(a)(7)(ii)(C) Emergency mode operation plan | |
| 164.312(a)(2)(iv) Encryption and decryption | |
| 164.312(b) Audit controls | |
| 164.312(e)(2)(ii) Encryption |
| Clause | Controls from this module |
|---|---|
| 3.1.12: Monitor and control remote access sessions. | |
| 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.14.6 Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks | |
| 3.14.7: Identify unauthorized use 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.2 Ensure that the actions of individual system users can be uniquely traced to those users, so they can be held accountable for their actions | |
| 3.3.3 Review and update logged events | |
| 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) | |
| AC-2(4) Automated Audit Actions | |
| AC-3(1) Restricted Access To Privileged Functions | |
| AC-3(10) Audited Override Of Access Control Mechanisms | |
| AC-4(26) Audit Filtering Actions | |
| AC-6(9) | |
| 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-12(4) Query Parameter Audits Of Personally Identifiable Information | |
| AU-12(a) | |
| AU-12(c) | |
| AU-14(3) Remote Viewing And Listening | |
| AU-14(a) | |
| AU-14(b) | |
| AU-2(b) | |
| AU-3(a) | |
| AU-3(b) | |
| AU-3(c) | |
| AU-3(d) | |
| AU-3(e) | |
| AU-3(f) | |
| 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-8(b) | |
| AU-9(3) Cryptographic Protection | |
| Architecture And Provisioning For Name/Address Resolution Service (SC-22) | |
| Audit Record Retention (AU-11) | |
| CA-2(2) Specialized Assessments | |
| CA-7(4)(c) | |
| CA-7(b) | |
| CM-3(a) | |
| CM-5(1)(b) | |
| CP-1(a)(1)(b) | |
| CP-2(5) Continue Mission And Business Functions | |
| CP-2(6) Alternate Processing And Storage Sites | |
| CP-2(a) | |
| CP-2(d) | |
| CP-2(e) | |
| CP-6(2) Recovery Time And Recovery Point Objectives | |
| CP-9(8): Cryptographic Protection | |
| CP-9(d) | |
| Continuous Monitoring (CA-7) | |
| Continuous Monitoring Strategy (PM-31) | |
| Distributed Processing And Storage (SC-36) | |
| IA-3(3)(b) | |
| Information Management and Retention (SI-12) | |
| MA-4(1)(a) | |
| Non-Repudiation (AU-10) | |
| PM-14(a)(1) | |
| PM-14(b) | |
| PM-21(b) | |
| Resource Availability (SC-6) | |
| SA-15(a)(4) | |
| SC-13(a) | |
| SC-28(1): Cryptographic Protection | |
| SC-28(2) Offline Storage | |
| SC-36(1)(a) | |
| SC-5(2) Capacity, Bandwidth, And Redundancy | |
| SC-7(9)(b) | |
| SC-8(3) Cryptographic Protection For Message Externals | |
| SC-8(4) Conceal Or Ramdomize Communications | |
| SI-1(1)(c) | |
| SI-10(1)(c) | |
| SI-13(5) Failover Capability | |
| SI-19(4) Removal, Masking, Encryption, Hashing, Or Replacement Of Direct Identifiers | |
| SI-2(a) | |
| SI-3(8)(b) | |
| SI-4(17) Integrated Situational Awareness | |
| SI-4(2) Automated Tools For Real-Time Analysis | |
| SI-4(20) Privileged Users | |
| SI-7(8) Auditing Capability For Significant Events | |
| System Recovery And Reconstitution (CP-10) | |
| Thin Nodes (SC-25) |
| Clause | Controls from this module |
|---|---|
| Booting Up: Things to Do First-3 | |
| Your Data-1 | |
| Your Data-2 | |
| Your Data-4 | |
| Your Systems-2 | |
| Your Systems-3 |
|
| Clause | Controls from this module |
|---|---|
| AC-2(4) Automated Audit Actions | |
| AC-2(g) | |
| AU-12(a)(c) | |
| AU-2(a)(d) | |
| AU-6(1)(3) | |
| Audit Record Retention (AU-11) | |
| CA-7(a)(b) | |
| Content of Audit Records (AU-3) | |
| Denial Of Service Protection (SC-5) | |
| Information Handling and Retention (SI-12) | |
| Information System Recovery And Reconstitution (CP-10) | |
| Protection of Audit Information (AU-9) | |
| Protection of Information at Rest (SC-28) |
| Clause | Controls from this module |
|---|---|
| D1.RM.Rm.B.1 | |
| D2.MA.Ma.B.1 | |
| D3.CC.PM.B.1 | |
| D3.CC.PM.B.3 | |
| D3.DC.An.B.3 | |
| D3.DC.An.B.4 | |
| D3.PC.Am.B.12 | |
| D3.PC.Im.B.1 | |
| D5.DR.De.B.3 | |
| D5.IR.Pl.B.6 |
| 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 | |
| C1.1 The entity identifies and maintains confidential information to meet the entity's objectives related to confidentiality | |
| C1.2 The entity disposes of confidential information to meet the entity's objectives related to confidentiality | |
| CC1.3 COSO Principle 3: Management establishes, with board oversight, structures, reporting lines, and appropriate authorities and responsibilities in the pursuit of 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 | |
| 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. |
|
| CC7.3 The entity evaluates security events to determine whether they could or have resulted in a failure of the entity to meet its objectives (security incidents) and, if so, takes actions to prevent or address such failures | |
| CC7.5 The entity identifies, develops, and implements activities to recover from identified security incidents | |
| P4.2 The entity retains personal information consistent with the entity's objectives related to privacy | |
| PI1.3 Data is processed completely, accurately, and timely as authorized to meet the entity's processing integrity commitments and system requirements | |
| PI1.4 System outputs are complete, accurate, distributed only to intended parties, and retained to meet the entity's processing integrity commitments and system requirements | |
| PI1.5 Stored data is maintained complete, accurate, and protected from unauthorized modification to meet the entity's processing integrity commitments and system requirements |
| Clause | Controls from this module |
|---|---|
| 11.10(a) Validation of systems to ensure accuracy, reliability, consistent intended performance, and the ability to discern invalid or altered records | |
| 11.10(c) Protection of records to enable their accurate and ready retrieval throughout the records retention period | |
| 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(k) Use of appropriate controls over systems documentation that includes adequate controls over the distribution of, access to, and use of documentation for system operation and maintenance | |
| 11.30 Controls for open systems |
Framework coverage
Which controls from this module are active under each framework endpoint. Your framework preferences choose the columns.
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.