Explanation
Why the waste happens and who it affects.
Unlike automated backups tied to a live instance, these backups persist independently and continue generating storage costs despite no longer supporting any active database. This is distinct from excessive retention on active databases and typically arises from incomplete cleanup during decommissioning.
Billing model
The pricing dimensions that drive this cost.
Amazon RDS charges for backup storage beyond the free allocation associated with active database instances. Manual snapshots and retained backups are billed independently and continue to incur storage charges even after the source database instance is deleted.
How to detect
3 checks to find it in your estate.
- Review whether backup storage exists for database instances that no longer exist
- Assess whether retained snapshots are associated with decommissioned or retired environments
- Confirm whether remaining backups have an active recovery, audit, or compliance purpose
How to fix
2 ways to remove the waste.
- Remove manual snapshots and retained backups that are no longer required
- Incorporate backup cleanup into database decommissioning and environment teardown processes
Documentation
Vendor references for pricing and configuration.