Cloud Cost Analyzer checks every instance against rules for idle and oversized compute, previous-generation families, Graviton migration candidates, stopped instances still holding EBS, burstable misuse, and Savings Plan or Reserved Instance coverage, each with a dollar estimate.
$ cca scan --provider awsRead-only, runs in about 5 minutes. Free tier, no credit card.
Right-size over-provisioned instances, migrate to current-generation and Graviton families, schedule non-production instances to stop outside working hours, use Spot for fault-tolerant work, and cover the steady baseline with a Savings Plan or Reserved Instances.
If your workload has an arm64 build (most modern runtimes and containers do), it is usually a straightforward instance-type change. Graviton is typically about 20 percent cheaper for equivalent performance. Test in a non-production environment first.
Usually not. Dev and test instances are often used only during working hours, so scheduling them to stop nights and weekends can cut their cost by 60 to 70 percent with no impact on developers.
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.
Oversized instances, Serverless v1, and I/O-Optimized breakevens.
Idle cache clusters and oversized, non-Graviton nodes.
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.