Long-Retained RDS Manual Snapshot

Unlike automated backups, which are automatically deleted after a set retention period, manual snapshots remain in place until explicitly deleted. Over time, this can lead to an accumulation of snapshots that are no longer needed but still incur monthly storage charges. This is particularly common in environments where snapshots are taken frequently but not consistently reviewed. If left unmanaged, manual snapshots can become a source of ongoing cost, especially for large databases or when snapshots are copied across regions.

Amazon RDS snapshot storage is billed based on the total volume of data retained across all snapshots, measured in GB per month. AWS uses incremental storage under the hood, meaning only the changes between snapshots are stored. However, you're charged for the full set of unique data blocks needed to restore each snapshot, and these charges persist until the snapshot is deleted. There are two types of snapshots:

• Automated backups are managed by AWS and retained for a limited time (up to 35 days). Backup storage, covering both automated backups and manual snapshots, is included at no additional charge up to your total provisioned database storage in the region.
• Manual snapshots are created by the user and retained indefinitely unless explicitly deleted. They count toward the same regional backup storage allowance as automated backups, and usage beyond that allowance is billed per GB-month. Because manual snapshots persist until deleted, including after the source instance is deleted, they often push backup storage over the free allowance.

• List all manual RDS snapshots across regions and accounts
• Identify snapshots that exceed a predefined age threshold (e.g., 30, 60, or 90 days)
• Check whether snapshots are tied to deleted or decommissioned database instances
• Evaluate whether any snapshots are shared or copied across regions, increasing costs
• Coordinate with database owners or teams to confirm which snapshots are still needed for recovery, audit, or compliance purposes

Delete manual snapshots that are no longer required. Before removal, confirm that the data is not needed for restore workflows or long-term retention. Establish internal policies or automation to routinely review and clean up aged snapshots. If long-term storage is necessary, evaluate exporting data to object storage formats that may offer lower-cost archival options.

• RDS Pricingaws.amazon.com
• Deleting a DB snapshot for Amazon RDSdocs.aws.amazon.com
• Creating a DB snapshot for a Single-AZ DB instance for Amazon RDSdocs.aws.amazon.com