AWS RDS Aurora Terraform module
Upstream version 10.4.1
5 controls from FedRAMP Moderate Baseline Rev 4 requirements
Terraform Module Source
fedrampmoderate.compliance.tf/terraform-aws-modules/rds-aurora/awsBehavioral Summary
This module modifies 3 variable defaults and makes 0 resource changes from the upstream module. All changes are driven by compliance controls and can be reviewed in detail below.
Your Code Impact
If you are migrating from the upstream module, the enforced default changes mean your existing configurations will automatically gain compliance controls. Variables you have explicitly set will continue to use your values. Review the diff below to understand exactly what changes.
Compared to
terraform-aws-modules/rds-aurora/aws@10.4.13 changesVariables Changed
3| Variable | Upstream | CTF | Reason | Control |
|---|---|---|---|---|
| cloudwatch_log_group_retention_in_days | 7 | 365 | Ensure a minimum duration of event log data is retained for your log groups to help with troubleshooting and forensics investigations. | cloudwatch_log_group_retention_period_365 |
| cluster_monitoring_interval | 0 | 60 | Enable AWS Relational Database Service (AWS RDS) to help monitor AWS RDS availability. This provides detailed visibility into the health of your AWS RDS database instances. | rds_db_instance_and_cluster_enhanced_monitoring_enabled |
| deletion_protection | - | true | This control checks whether RDS clusters have deletion protection enabled. This control is intended for RDS DB instances. However, it can also generate findings for Aurora DB instances, Neptune DB instances, and AWS DocumentDB clusters. If these findings are not useful,then you can suppress them. | rds_db_cluster_deletion_protection_enabled |