Skip to content
FinOps workspace
COST LEDGER / DECISION GUIDE

AWS Backup cost optimization: storage, copies and restores

Published and checked: 14 November 2026Request a backup cost review quote

Review the cost of protecting and recovering your workloads before changing backup policies. Map storage and copies to a recovery requirement, include restore testing, and have the application and security owners approve the proposed scope.

Illustration of server racks in the dark green and mint Cost Ledger palette
Connect each backup copy to an owner and a documented recovery requirement.

For protected databases, reconcile the underlying service with the RDS compute, storage and backup pricing boundary so centrally managed protection is counted once.

Start with the complete backup cost boundary

The Backup line on the invoice may not contain the entire cost. AWS explains in its metering and billing documentation that fully managed resource activity appears under Backup, while some charges for other resource types appear under the underlying service. Storage and data transfer for logically air-gapped vaults appear under AWS Backup. Reconcile by resource type and destination before comparing totals.

BoundaryEvidence to collectQuestion to resolve
Stored recovery pointsVault, resource type, tier and retentionWhich protection requirement does this storage serve?
CopiesSource and destination account and RegionWhich recovery scenario requires this copy?
Restore activityRecovery points tested and resources createdWhat is the complete cost of the recovery exercise?
Adjacent servicesResource-service billing and relevant requestsWhich costs sit outside the Backup subtotal?

Set the account boundary through the AWS cost review scope guide. For the underlying storage, use the EBS volume and snapshot review and the RDS cost review. Keep the resource identifier and period with each amount so a second analyst can reproduce the reconciliation.

Compare retention and storage tiers against recovery needs

The current AWS Backup pricing page separates storage, restores, restore testing and cross-Region transfer. Cold storage applies only to supported resource types; early deletion can carry a charge. Check the resource, Region, tier eligibility and minimum duration rather than applying one storage rate to every recovery point.

  • Identify the application owner and approved recovery requirement.
  • Record the backup plan, copy rules and existing recovery-point lifecycle.
  • Compare the current retention with the requirement and document any unexplained difference.
  • Include restore cost and operational effort in a tier comparison.

AWS documents that automatic backups use lifecycle settings from the backup plan, while on-demand backups have settings configured at creation. Review both populations. A review limited to the current plan can leave older or manually created recovery points outside the findings register.

Inspect Vault Lock before estimating removable storage

A locked recovery point cannot be treated as immediately removable spend. The AWS Backup Vault Lock documentation distinguishes Governance and Compliance modes. Governance locks can be removed by sufficiently authorized users; deletion protection applies while the lock remains in place. In Compliance mode, after the grace period, the lock cannot be removed while recovery points remain, and protected backups cannot be deleted or have their lifecycle changed. An empty vault can be deleted. Check each recovery point's own lifecycle: the vault lock's minimum and maximum retention settings do not retroactively change it.

  1. Inventory each vault and its lock mode.
  2. Record the retention and expiration information for existing recovery points.
  3. Separate changes feasible now from changes affecting future backups.
  4. Ask the security owner to approve the exact candidate change.
  5. Preserve the approval and validation result with the cost estimate.

Do not include locked storage in an immediate savings total merely because a revised policy would retain less data. Ask for a schedule distinguishing existing recovery points from future creation. Use the realized savings measurement guide to separate a proposed future cost difference from an invoice reduction already observed.

Include copy routes and restore tests in the estimate

For cross-Region copies, AWS pricing distinguishes transfer from destination storage. Restore testing can add evaluation and restored-data charges for the applicable resource types. Resources retained for any time after restoration completes can incur additional charges, including during the test; restored S3 objects also incur PUT request charges. Model the relevant recovery exercise beside steady-state protection, and assign cleanup ownership for the test environment.

  • Explain the recovery purpose of each destination rather than assuming multiple copies are redundant.
  • Match the transfer route to the account and Region on the bill.
  • Record the selected test scope and the expected resource cleanup.
  • Check the applicable rates on the date of the estimate.

For S3-backed protection, examine the adjacent requests and object-cost boundary with the S3 cost optimization checklist. For copy routes, the AWS data transfer cost guide helps keep transfer and storage separate. Request an estimate that identifies exclusions rather than filling gaps with a generic percentage.

Choose a review with evidence your team can accept

Ask the consultant to demonstrate relevant AWS billing and backup experience through an authorized sample deliverable or a walkthrough on an agreed dataset. Compare offers on the same resource scope, required customer effort and implementation boundary. Keep the initial analysis access separate from permission to edit backup policies or remove recovery points.

DeliverableAcceptance evidence
Inventory and billing bridgeVaults, resources, destinations and costs reconcile with explained gaps
Findings registerEach proposal names its recovery constraint, approver and affected population
Cost comparisonEditable inputs distinguish existing locked storage, future backups and restore activity
HandoverYour team receives calculations, review instructions and access-closure confirmation

Accept the method and the protection boundary before accepting a savings claim. Use the cloud cost RFP checklist to compare proposals. The engagement should state who supplies the inventory, who approves each change and how finance will verify its effect after implementation.

Get my FinOps quote