Submit feedback on
Orphaned RDS Backup Storage After Database Deletion
We've received your feedback.
Thanks for reaching out!
Oops! Something went wrong while submitting the form.
Close
Orphaned RDS Backup Storage After Database Deletion
CER:
AWS-Databases-9382
Service Category
Databases
Cloud Provider
AWS
Service Name
AWS RDS
Inefficiency Type
Orphaned backup storage
Explanation

This inefficiency occurs when an RDS database instance is deleted but its manual snapshots or retained backups remain. 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.

Relevant Billing Model

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.

Detection
  • 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
Remediation
  • Remove manual snapshots and retained backups that are no longer required
  • Incorporate backup cleanup into database decommissioning and environment teardown processes
Submit Feedback