Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
rds_cluster_minor_version_upgrade_enabledProvider: AWS
Service:
rdsSeverity: MEDIUM
Categories:
vulnerabilitiesResource type:
AwsRdsDbClusterWhat this check verifies
RDS Multi-AZ DB clusters are configured for automatic minor engine upgrades viaauto_minor_version_upgrade.
The evaluation checks these clusters to see if this setting is enabled so preferred minor releases are applied during the maintenance window.
Risk
Without automatic minor upgrades, clusters can miss security patches, enabling exploitation of known flaws (confidentiality). Unfixed defects may corrupt data (integrity) or trigger crashes and failovers (availability). Emergency patching raises downtime and operational risk.Recommendation
Enableauto_minor_version_upgrade on RDS Multi-AZ clusters and align updates with approved maintenance windows. Validate changes in non-production, and document any exceptions with a strict manual patch cadence. This strengthens defense in depth and improves availability.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws rds modify-db-cluster —db-cluster-identifier <example_resource_id> —auto-minor-version-upgrade
References
- https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/modify-multi-az-db-cluster.html
- https://docs.aws.amazon.com/sdk-for-ruby/v3/api/Aws/RDS/Types/CreateDBClusterMessage.html
- https://docs.aws.amazon.com/securityhub/latest/userguide/rds-controls.html#rds-35
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = rds_cluster_minor_version_upgrade_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks