Explanation
Why the waste happens and who it affects.
RDS backup storage is significantly more expensive than equivalent storage in S3. For long-term retention or compliance use cases, exporting backups to S3 (e.g., via snapshot export to Amazon S3 in Parquet) is often more cost-effective than retaining them in RDS-native format, but exported data cannot be restored to an RDS DB instance, so this only suits analytics or archival needs where restoring the database is not required.
Billing model
The pricing dimensions that drive this cost.
Backups in RDS are billed by the total volume of backup data retained beyond the free tier (equal to the size of the active DB storage). Additional backup storage is charged per GB-month, which can lead to disproportionately high costs if backup volumes grow over time. Exporting snapshots to S3 offers a lower-cost archival alternative for data that will not need to be restored as a database.
How to detect
5 checks to find it in your estate.
- Review backup storage consumption by DB instance
- Review total backup size versus DB size to identify excess retention
- Check if automated backup retention periods are longer than necessary
- Determine whether legacy snapshots are still required or can be deleted
- Assess whether long-term backup needs could be satisfied with lower-cost S3 exports
How to fix
4 ways to remove the waste.
- Adjust backup retention periods to match business or compliance needs
- Shorten the automated backup retention period (automated backups of a running instance cannot be deleted individually and expire with the retention period), delete retained automated backups of deleted instances, and delete manual snapshots that are no longer needed
- Export long-term data to S3 using snapshot export where restore is not required, since exported data cannot be restored to a DB instance
- Monitor backup growth and align storage tier with data access needs
Documentation
Vendor references for pricing and configuration.