Snapshots Management

Before you start

Enable Snapshots Management for the selected AWS account, update the CloudFormation stack, and complete a sync. The role needs rds:DescribeDBSnapshots.

Every plan can view the inventory. Cleanup and retention scripts require a paid plan.

Read the snapshot inventory

The inventory combines manual snapshots and automated backups returned by RDS for the selected account and regions.

Manual snapshots remain in AWS until someone deletes them. An orphan manual snapshot belongs to a database that is no longer present in the current inventory.
Automated snapshots follow the backup retention policy of their source database.
Use the filters to compare snapshot identifiers, source databases, types, retention periods, age, size, and estimated annual cost.

Expected synchronization result

A snapshot appears after a successful sync scans its region. A deleted snapshot remains visible until a later successful sync confirms that it is no longer returned by AWS.

Generate a manual snapshot cleanup script

Select manual snapshots, then choose Generate cleanup. SnoozeDB creates a shell script that lists the selected identifiers and waits for a confirmation phrase before it calls the AWS CLI.

Download the script and review every snapshot identifier. Run it from a terminal that has credentials for the correct AWS account.

Review before running the script

Confirm that every identifier belongs to the intended AWS account and region.
Verify that each snapshot is manual, no longer required for recovery, and not protected by another retention process.
Run the script with an AWS identity that has only the deletion access needed for this operation.

Execution stays under your control

SnoozeDB generates and downloads the command file. It does not run the file, assume your terminal identity, or send deletion requests from the application.

Deletion is permanent

SnoozeDB does not delete snapshots. You run the script under your own AWS identity, and AWS processes the deletion requests. Confirm that each snapshot can be removed before you continue.

Generate an automated backup retention script

Select automated snapshots, choose Generate policy, and set the target retention period. The script updates backup retention on each source database.

The new policy controls future automated backup retention. It does not delete manual snapshots or convert automated snapshots into manual snapshots.

Review every source database

A shorter retention period removes recovery points sooner. Review the selected databases and your recovery requirements before running the script.

Expected result

After the script succeeds, the source database uses the selected retention period. Run a later sync to refresh the retention value shown by SnoozeDB.

Understand the cost estimate

Manual snapshot cost is an upper bound based on the size reported by RDS and a reference price of $0.023 per GB-month.

AWS bills the incremental blocks stored for a snapshot. Cost Explorer and detailed billing are the source of truth, so the displayed estimate is not an invoice amount or a guaranteed saving.

Estimate limitations

The estimate uses the full snapshot size reported by RDS, while AWS bills incremental storage blocks.
Regional pricing, free backup allowances, and later block changes can make the invoice differ.
Treat the amount as a prioritization signal and verify material savings in AWS billing data.

Troubleshooting

No inventory: confirm that Snapshots Management is enabled and that the CloudFormation stack includes rds:DescribeDBSnapshots.
Stale inventory: wait for the current sync to finish, then confirm that a later successful sync completed after the AWS deletion.
Disabled script buttons: cleanup and retention scripts require Team, Startup, or Scale.
No results after a successful sync: check the selected AWS account, enabled regions, and active filter.