Cloud Cost Analyzer flags idle ElastiCache clusters using CPU, hit-rate, and connection metrics, plus oversized and non-Graviton node types, and prices each so you can right-size or retire with confidence.
$ cca scan --provider awsRead-only, runs in about 5 minutes. Free tier, no credit card.
Look for low CPU utilization, a low cache-hit rate, and few active connections over a representative period. A cluster that stays quiet across weeks is a candidate to downsize or delete. Cloud Cost Analyzer combines these signals to flag idle clusters.
Yes. ElastiCache offers Graviton node types (for example cache.r6g and cache.m6g) that are typically cheaper than the equivalent Intel nodes for the same performance.
For clusters that run continuously, reserved nodes offer a significant discount over on-demand in exchange for a one or three year commitment. Cover the steady baseline, not short-lived or bursty clusters.
Idle gateways and avoidable data-processing charges, one per AZ.
Over-provisioned classes, non-Graviton, and Multi-AZ on non-prod.
Orphaned volumes, old snapshots, and gp2 you never moved to gp3.
ALBs and NLBs with no targets or near-zero traffic, still billing.
Cold data sitting in Standard with no lifecycle policy.
Idle and oversized instances, previous-gen types, 24/7 dev boxes.
Oversized instances, Serverless v1, and I/O-Optimized breakevens.
Idle distributions and price classes wider than your audience.
On-demand billing on steady workloads, and unused indexes.
Over-provisioned memory and x86 functions that could be arm64.