Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
rds_instance_multi_azProvider: AWS
Service:
rdsSeverity: MEDIUM
Categories:
resilienceResource type:
AwsRdsDbInstanceWhat this check verifies
RDS DB instances are evaluated for Multi-AZ configuration, either enabled on the instance or inherited from the associated DB cluster.Risk
Without Multi-AZ, an Availability Zone or instance failure can cause extended downtime and rely on restores, risking loss of recent writes. This degrades availability and may affect integrity, interrupting applications and breaching SLAs.Recommendation
Apply fault-tolerance and redundancy principles: enable Multi-AZ for production RDS workloads. Choose one standby or two readable standbys based on RTO/RPO and performance needs. Regularly test failover, monitor configuration drift, and allow exceptions only with documented, risk-based approval.Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws rds modify-db-instance —db-instance-identifier <db_instance_id> —multi-az —apply-immediately
References
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/RDS/rds-multi-az.html
- https://aws.amazon.com/rds/features/multi-az/
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_instance_multi_az. 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