Backup is essential, but on AWS it becomes a silent budget eater because snapshots accumulate without expiry, retention is set long for everything regardless of need, and snapshots from deleted volumes keep billing as orphans. The cure is a tiered backup policy: keep recent operational backups on warm storage for days to weeks, lifecycle older recovery points to cold archive tiers automatically, set compliance retention only where the rules require it, and sweep up orphaned snapshots on a schedule. Done well, this protects every recovery objective while cutting the backup line materially.
Backup is one of the most common places good intentions turn into recurring waste. Here is how to set policies that hold the line.
Why do AWS backup costs creep up?
Snapshots on AWS are incremental, which lulls teams into thinking backup is cheap. It is, per snapshot, but three patterns compound into a large bill. First, snapshots created on a schedule with no expiry pile up indefinitely. Second, a single long retention is applied to every workload, so low value data is kept as long as critical data. Third, when a volume is deleted its snapshots are often left behind as orphans that no one tracks and that bill every month.
None of these is dramatic on its own, which is why they survive. Surfaced together in the Cost and Usage Report, snapshot and backup storage is frequently a larger line than teams expect.
How long should you actually keep backups?
Retention should follow the reason for the backup, not a single default. Operational restores, recovering from a bad deploy or an accidental deletion, need recent backups available fast, so days to a few weeks on warm storage is usually enough. Compliance copies need to exist for a defined regulatory term, but they almost never need fast restore, so they belong in cold archive tiers. Disaster recovery copies sit in between, sized to your recovery objectives.
The expensive anti pattern is one blanket multi year retention kept on warm backup storage for everything. Splitting retention by purpose is the single biggest lever, because most of the data being kept for years is being kept on storage priced for fast restore it will never need.
What does a tiered backup policy look like?
AWS Backup supports lifecycle rules that transition recovery points from warm to cold storage automatically after a set period, and cold backup storage costs far less per gigabyte. A workable shape:
| Backup purpose | Storage tier | Retention window |
|---|---|---|
| Operational restore | Warm backup storage | Days to a few weeks |
| Disaster recovery | Warm then cold by lifecycle | Weeks to months |
| Compliance archive | Cold archive storage | Required regulatory term |
| Orphaned snapshots | Delete on schedule | None, sweep regularly |
Tag backups to an owner and a purpose so each policy is auditable, and run a regular sweep for snapshots whose source volume no longer exists. Automating the lifecycle transitions means the savings hold without anyone having to remember to move data.
A worked example
A Fortune 500 retailer kept every snapshot on warm storage for several years under one blanket policy and had thousands of orphaned snapshots from decommissioned volumes. Splitting retention by purpose, adding lifecycle rules to move anything past a few weeks to cold storage, and sweeping the orphans cut the backup and snapshot line substantially while preserving every compliance and recovery requirement. Figures are verified against billing data and anonymised.
Frequently asked questions
Why do AWS backup costs creep up?
How long should you keep cloud backups?
Can backups move to cheaper storage?
Right size your backup spend with us
We tier your AWS backup policies to real recovery and compliance needs, automate the lifecycle to cold storage, and clear the orphaned snapshots draining the budget. Our guarantee: we reduce your cloud spend or we reimburse our service fee. Pricing is either a Fixed Fee scoped up front or Gainshare, a share of verified savings with no retainer and no risk.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.