ElastiCache replication group has Multi-AZ failover disabled
- Severity
- Low
- Service
- ElastiCache
- Check ID
- ELASTICACHE_MULTI_AZ_DISABLED
What this check finds
A Redis replication group without automatic failover and Multi-AZ has no standby to promote when the primary node or its Availability Zone fails, resulting in cache downtime and potential data loss. Enable automatic failover with Multi-AZ.
Passing looks like: ElastiCache Multi-AZ failover enabled.
How to fix it
Enable automatic failover and Multi-AZ on the replication group (requires at least one replica).
AWS CLI
aws elasticache modify-replication-group --replication-group-id RG_ID --automatic-failover-enabled --multi-az-enabled --apply-immediately
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
ElastiCache → Redis → select group → Modify → Multi-AZ / Auto-failover → Enable.
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 |
|---|---|
| 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