Backup Vault Cost

Backup vaults; cross-region cost.

Overview

AWS Backup vaults charge for storage by tier and for cross-region replication separately. The cost compounds across the retention period; a 30-day RPO with cross-region DR is a different bill than a 7-day RPO without it. The discipline is matching retention, tier, and cross-region scope to what recovery actually requires rather than enabling everything by default.

• Vault storage plus cross-region cost. Per-vault storage plus per-region replication. Both lines compound across retention.
• Storage tier choice. Warm tier for recent recovery points, cold tier for compliance retention. Cold is dramatically cheaper.
• Cross-region replication. Per-byte cost on data leaving the region plus storage in the target region. Reserve for DR-grade workloads.
• Per-resource retention plus quarterly audit. Retention scaled to recovery needs; quarterly review catches forgotten resources before they become a line item.

The approach

Three habits keep backup-vault spend matched to actual recovery need: per-resource retention tied to recovery requirements, tier-based storage that ages snapshots into colder classes, and cross-region replication restricted to data that genuinely needs it.

• Per-resource retention. Production data, dev data, and ephemeral workloads each get retention scaled to need. Uniform retention is uniformly wrong.
• Tier-based storage. Warm tier for recent backups, cold tier for compliance retention. Lifecycle rules transition automatically.
• Selective cross-region replication. Only DR-grade data crosses the region boundary. Non-critical data stays regional.
• Quarterly vault audit plus documented policy. Per-vault retention rationale and last-restore date; the audit catches drift while it is small.

Why this compounds

Each correctly-shaped retention and tier policy saves money every month for the lifetime of the backup. The team’s recovery discipline deepens; orphaned snapshots disappear before they accumulate.

• Cost efficiency. Retention and tier matched to recovery need. Savings continue every month.
• Recovery posture stays sharp. Right backups, right tier, tested restores. RPO and RTO match commitments.
• Operational hygiene. Quarterly audit catches orphaned snapshots before they become structural.
• Year-one investment, year-two habit. First policy is heavy lift. By year two, every new resource ships with backup policy on day one.