# Orphaned RDS backup storage after database deletion

Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/orphaned-rds-backup-storage-after-database-deletion

An RDS database instance is deleted but its manual snapshots or retained backups remain.

By: Chandan Bukkapatnam

[Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) 

# Orphaned RDS Backup Storage After Database Deletion

The short version

An RDS database instance is deleted but its manual snapshots or retained backups remain.

Chandan Bukkapatnam

Senior Cloud FinOps Analyst @ Procore Technologies

AWS service

[AWS RDS](https://www.pointfive.co/efficiency-hub/cloud-services/aws-rds)

Category

[Databases](https://www.pointfive.co/efficiency-hub/service-category/databases)

Reference

CER-0299

Type

Idle or Unused Resource

## 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.

- [https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER\_WorkingWithAutomatedBackups.html  docs.aws.amazon.com](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithAutomatedBackups.html)

- [https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER\_DeleteSnapshot.html  docs.aws.amazon.com](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_DeleteSnapshot.html)

## Related inefficiencies

[Browse the library](https://www.pointfive.co/efficiency-hub)

- AWS RDS  CER-0097

### [No Lifecycle Management for Temporarily Stopped RDS Instances](https://www.pointfive.co/efficiency-hub/inefficiencies/no-lifecycle-management-for-temporarily-stopped-rds-instances)

While stopping an RDS instance reduces runtime cost, AWS enforces a 7-day limit on stopped state. After this period, the instance is automatically restarted and resumes incurring compute charges - even if the database is still not needed....

Databases

- AWS RDS  CER-0065

### [Inactive RDS Instance](https://www.pointfive.co/efficiency-hub/inefficiencies/inactive-rds-instance)

An RDS instance remains in the running state but is no longer actively serving application traffic. These instances may be remnants of retired applications, paused development environments, or workloads that were migrated elsewhere. If an...

Databases

- AWS RDS  CER-0064

### [Inactive RDS Cluster](https://www.pointfive.co/efficiency-hub/inefficiencies/inactive-rds-cluster)

An RDS cluster remains provisioned but is no longer serving any workloads and has no active database connections. Unlike underutilized resources, these clusters are completely idle-showing no query activity, background processing, or usage...

Databases

---
Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.