Cloud Cost Analyzer evaluates Aurora clusters for over-provisioning, Serverless v1 that should move to v2, the I/O-Optimized breakeven, and non-Graviton classes, and estimates the monthly saving for each change.
$ cca scan --provider awsRead-only, runs in about 5 minutes. Free tier, no credit card.
Aurora I/O-Optimized removes per-request I/O charges in exchange for higher instance and storage rates. It becomes cheaper once I/O is roughly a quarter or more of your Aurora bill. For I/O-heavy clusters it can cut costs and make spend predictable.
Yes. Serverless v1 is end-of-life. v2 scales in finer increments, scales faster, and supports more features, and it is generally more cost-effective for variable workloads. Plan the migration before v1 support ends.
Yes. Aurora offers Graviton-based instance classes (for example db.r6g) that are typically cheaper than the equivalent Intel classes for the same performance, usually a minor version and instance-class change.
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.
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.