Explanation
Why the waste happens and who it affects.
Unlike underutilized resources, these clusters are completely idle-showing no query activity, background processing, or usage over time. They often persist in dev, staging, or legacy environments where the workload has been retired or moved, yet the cluster remains active and continues to generate ongoing compute and storage costs.
Billing model
The pricing dimensions that drive this cost.
RDS clusters are billed per hour based on the instance types used for each node (primary and replicas), along with additional charges for storage, I/O, backups, monitoring, and data transfer. For provisioned instances, charges continue to accrue even if the cluster is idle or not serving traffic. Aurora Serverless v2 clusters configured to scale to 0 ACUs automatically pause when idle and stop instance charges, though storage is still billed.
How to detect
5 checks to find it in your estate.
- Identify RDS clusters with no active connections or query activity during the lookback period
- Confirm whether the cluster is receiving any traffic from applications or internal services
- Check for sustained low or zero CPU utilization, network throughput, and read/write IOPS
- Evaluate whether the cluster is part of a dev/test environment that is no longer in use
- Consult application and database owners to confirm that the cluster is no longer needed
How to fix
How to remove the waste.
Decommission the RDS cluster after confirming it is no longer in use. Take a final snapshot if the data may be needed later, and ensure that associated backups and read replicas are also deleted if not required. Incorporate regular reviews of cluster activity to identify and clean up idle infrastructure.
Documentation
Vendor references for pricing and configuration.