AWS Backup cost explained: retention is the whole bill

Quick answer

AWS Backup bills mostly for backup storage (GB-month, rate varies by service — EBS-snapshot backups ~$0.05/GB-month), plus restore and cross-region copy charges. There's no management fee on top. The bill grows almost entirely from retention: backup plans that create recovery points with no lifecycle to expire them accumulate forever. Set expiration, move long-term copies to cold, and limit cross-region copies.

AWS Backup centralizes backups across EBS, RDS, EFS, DynamoDB, and more behind one service and one set of backup plans. The cost is straightforward — it's storage — but it has the same failure mode as every backup system: it's easy to create recovery points and easy to forget to delete them, so the bill creeps up quietly.

What you pay for

Warm backup storage: per GB-month, at a rate that depends on the service backed up (EBS-snapshot-based backups are ~$0.05/GB-month; EFS, RDS, and others have their own rates).
Cold storage: a cheaper tier for long-retention backups of supported services, with a minimum-retention period.
Restore: per-GB restore charges for some services.
Cross-region / cross-account copy: data transfer plus storage in the destination.

Retention is the whole story

A backup plan creates recovery points on a schedule. Without lifecycle rules to expire them, they pile up: a daily backup retained "forever" for a 500 GB volume, even incremental, accumulates steadily and never stops billing. The single most effective control is a lifecycle that expires recovery points at the retention your compliance policy actually requires — which is almost never "keep everything."

How to keep it down

Set expiration on every backup rule. Define a retention period and let AWS Backup delete past it automatically.
Tier long-term backups to cold. Compliance copies you keep for years but rarely restore belong in cold storage — much cheaper, with a minimum-retention window.
Limit cross-region copy. Replicate only the backups that genuinely need regional DR; copying everything doubles storage and adds transfer.
Clean up orphaned backups. Backups outlive the resources they protect. Reconcile recovery points against live resources periodically.

The same incremental-vs-retention dynamics apply to raw EBS snapshots — see the aws_ebs_snapshot page for the storage mechanics underneath AWS Backup.

FAQ

How is AWS Backup priced?

By the GB-month of backup storage (warm storage rates vary by service — EBS snapshot backups are ~$0.05/GB-month, EFS and others differ), plus restore charges per GB for some services, plus cross-region and cross-account copy (which incurs data transfer). AWS Backup itself adds no separate management fee beyond the storage.

Why is my AWS Backup bill growing?

Almost always retention. Backup plans create recovery points on a schedule, and without a lifecycle that expires old ones, backups accumulate indefinitely. A daily backup kept for years quietly stores far more than the source data, especially for full (non-incremental) backup types.

Are AWS backups incremental?

For EBS and several services, yes — backups store only changed blocks since the last recovery point, so the storage cost is far below the naive daily-size × retention multiplication. Some services store full copies. Knowing which applies to your resources tells you how aggressively retention drives cost.

How do I reduce AWS Backup costs?

Set lifecycle rules that expire recovery points and move long-term ones to cold storage, right-size retention to what compliance actually requires (not 'keep everything'), limit cross-region copies to data that genuinely needs DR, and clean up backups of deleted resources. Retention discipline is the biggest lever.

Does cross-region backup copy cost extra?

Yes. Copying recovery points to another region incurs cross-region data transfer plus storage in the destination region. Continuous cross-region copy of large backups for DR is a real recurring cost — replicate only what needs regional durability.

How does C3X estimate backup cost?

Backup cost is storage-driven, so C3X models it from expected backup GB in c3x-usage.yml and prices the backup vault and related snapshot resources, letting you attribute backup storage to the resources that generate it.

What to do next

Backup cost is storage you don't see until it's large. C3X prices an aws_backup_vault and related snapshot resources and takes backup volume from c3x-usage.yml, so you can attribute backup storage to the resources generating it and catch runaway retention. The quickstart runs it on your Terraform in minutes.