RDS instance does not have Multi-AZ enabled
- Severity
- Low
- Service
- RDS
- Check ID
- RDS_MULTI_AZ_DISABLED
What this check finds
A single-AZ RDS instance has no automatic failover. A hardware failure, AZ outage, or maintenance window will cause downtime. Multi-AZ provides a synchronous standby replica in a separate Availability Zone with automatic failover typically within 1-2 minutes.
Passing looks like: RDS Multi-AZ enabled.
How to fix it
Enable Multi-AZ on the RDS instance.
AWS CLI
aws rds modify-db-instance --db-instance-identifier INSTANCE_ID --multi-az --apply-immediately
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
RDS → Databases → select instance → Modify → Availability & durability → Multi-AZ deployment → Create a standby instance.
Compliance controls it is evidence for
A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works
| Framework | Controls |
|---|---|
| CIS AWS Foundations Benchmark v5.0.0 |
|
| HIPAA Security Rule |
|
| SOC 2 — Trust Services Criteria |
|
| NIST SP 800-53 Rev5 (Moderate) |
|
| NIST Cybersecurity Framework 2.0 |
|
| ISO/IEC 27001:2022 Annex A |
|
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs
More RDS checks
- HighAurora/RDS cluster storage is not encrypted at rest
- HighRDS automated backups are disabled
- HighRDS instance does not have automatic minor version upgrades enabled
- HighRDS instance has zero database connections for 7 days
- HighRDS instance storage is not encrypted at rest
- HighRDS security group allows broad CIDR ingress (broader than /16)
- HighRDS snapshot is public
- MediumAurora/RDS cluster has automated backups disabled