ElastiCache Multi-AZ Non-Critical
Multi-AZ runs and bills a second replica in another zone purely to survive a zone failure, which a cache whose contents can simply be rebuilt does not need.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Disable Multi-AZ on the non-critical ElastiCache cluster. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- ElastiCache on AWS
- The fix, by hand
- Confirm this is a non-production cache cluster.
- Modify → Availability → set Multi-AZ = Disable. This is a prerequisite only (AWS requires Multi-AZ off before the last replica can be removed). It removes no nodes and changes no billing.
- Modify → decrease the replica count to 0 (or API DecreaseReplicaCount / lower NumCacheClusters). THIS step removes the standby replica node(s) and stops their billing. It is the actual saving.
- Verify in the cluster detail page that the standby/replica nodes are gone.
These are the steps the finding carries in the product.
- Category
- Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-053- Full reference
Related checks
See the oversized resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.