Cross-Region recovery plans can look inexpensive at first, but AWS Backup pricing is usage-based. Budget for AWS Backup-billed backup storage at the source and destination, copy activity, and recovery drills. Source-service charges, transfer charges between Regions where applicable, KMS key usage, destination infrastructure, and restore resources may also apply.
For a realistic 2026 budget, model AWS Backup costs as steady monthly protection expenses plus event-driven recovery expenses. Review the official AWS Backup pricing page, relevant service pricing pages, and AWS’s official cost-estimation tool before finalizing the estimate. Rates and billing responsibility can vary by Region, protected resource, storage tier, account ownership, and consolidated billing configuration.
Key Takeaways
- AWS Backup charges can include backup storage and data transfer, billed separately from destination storage. Amazon RDS, Amazon S3, Amazon EBS, AWS KMS, AWS Config, Backup Audit Manager, and restored target resources may add separate charges.
- A cross-Region copy can involve source-side transfer, destination storage, and a KMS key or vault configuration. Confirm the exact payer and rate in current AWS documentation.
- Cross-Region recovery has no single universal price because storage, transfer, and restore rates vary by Region and resource type.
- A full initial copy can create a one-time cost spike. Ongoing costs depend heavily on changed data, copy frequency, and retention.
- AWS Backup can’t create cross-Region copies directly into cold storage. Applicable recovery points for supported resources have a documented minimum retention of 90 days. That retention period isn’t universal for every backup type.
- Amazon RDS includes an automated backup allowance up to 100% of provisioned database storage per Region, but that allowance doesn’t make a separate disaster recovery copy free.
- Restore drills need their own budget. They can incur restore, temporary target-resource, storage, and restore testing charges.
How AWS Backup Pricing Works for Cross-Region Recovery
AWS Backup pricing starts with metered resource use, rather than a platform subscription. AWS lists backup storage, restored data, cross-Region transfer, restore activity and testing, and backup evaluations as potentially billable categories. Some charges may appear in the AWS bill under AWS Backup or the underlying service.
A useful recovery budget separates recurring costs from costs that appear only during a test or incident. Otherwise, a low monthly storage estimate can hide the actual price of proving that recovery works.
Recurring protection charges
Recurring charges generally include source and destination backup storage, plus data transfer for each cross-Region copy. Check current AWS documentation for the specific treatment of each cross-Region copy.
Retention settings determine how long those copies remain billable.
The billing unit is commonly GB-months, meaning AWS charges for average storage during the month. However, metering varies by protected resource. Check the protected service’s pricing page and AWS’s backup metering and billing guidance before applying one service’s rate to another.
Event-driven recovery charges
A restore or restore test can create charges under AWS Backup or the underlying service, even after payment. Restore pricing may cover restored data, restore testing, and target infrastructure needed to validate the recovered workload. The restored service can separately bill database, volume, compute, request, retrieval, network, or other infrastructure use.
Treat a production incident as a high-impact scenario, not an extension of normal monthly spend. A database restored into a new Region still needs database capacity, networking, and application validation resources.
Cross-Region Backup Transfer Costs
Cross-Region backup copies create linked source and destination costs. The source Region may incur backup storage, storage for snapshots, and any applicable data transfer or copy charges. Destination backup storage covers copied data for the full retention period, while KMS key requests or charges may apply; verify the exact 2026 AWS billing treatment.
Which account pays each charge
When applicable, the account sending the backup data is typically charged for cross-region data transfer or a copy fee. The receiving account owns the destination recovery point in its designated backup vault and typically pays destination copy storage.
Consolidated billing can make the payer shown on an invoice differ from the workload owner. Chargeback reports should show both sides, using the account, Region, vault, resource, and cost allocation tags where available. A FinOps chargeback and showback model can allocate cross-region data transfer to the workload owner while assigning destination copy storage to the recovery or platform team.
A destination vault centralizes copied backups, but it does not centralize every cost. Transfer and destination storage can land in different accounts.
Full copies, changed data, and retention overlap
The first copy often moves far more data than later incremental backups. Those incremental backups are service-specific, and logical changes don’t necessarily equal transferred GiB.
Do not estimate transfer from total protected capacity alone. Measure actual copy volume for a normal week, month-end batch cycle, and database maintenance period. Compare those results with service behavior, change rate, and copy frequency. Transfer volume and backup storage can diverge because retained recovery points may share data or follow service-specific retention behavior.
Backup Storage, Warm Storage, and Cold Storage
Storage is the most predictable part of the model, but its rates still require service-level detail. Backup storage pricing depends on the protected resource, Region, backup tier, lifecycle support, compression or deduplication behavior where relevant, and the amount actually metered, not simply provisioned capacity.
A backup vault is a logical destination, but it doesn’t erase service-specific storage charges or KMS costs. Use current rates for both the source and recovery Regions. AWS changes prices and adds features over time, so validate every estimate against the current AWS Backup rates page, relevant service pricing pages, and the AWS Pricing Calculator before approving a budget.
Warm storage supports active recovery plans
Warm storage suits backups that you may need to restore quickly or access during recurring tests. It is usually the practical starting tier for backup storage in cross-Region disaster recovery.
A cross-Region copy normally lands in a supported destination tier before any permitted lifecycle transition.
For each backup plan, record protected GiB, expected billed backup storage volume in GiB, daily or weekly data change, retention days, and destination Region. The difference between protected capacity and stored backup volume is often where forecasts fail.
Cold storage has constraints that change the economics
Cold storage can reduce long-retention backup storage expense for supported recovery points. However, AWS requires those items to remain in cold storage for a 90-day minimum retention period. Deleting one earlier triggers a prorated charge for the remaining minimum period.
According to AWS, cross-Region copies directly into cold tiers aren’t supported, so copies into cold storage aren’t available. Plan the destination copy as warm storage first, then confirm eligible resources and whether lifecycle policies for that service and Region support a later transition. Don’t assume the tier is always cheaper after copy, transition, retrieval, and restore charges.
Restore Pricing and Recovery Testing
A backup that restores only on paper isn’t a recovery strategy. Still, restore testing costs money, so teams should model it as a scheduled operating expense rather than avoid it.
AWS Backup pricing distinguishes backup storage charges for stored data from restore activity and testing. The precise restore pricing depends on the source service, Region, storage tier, restore method, and whether the test uses an AWS Backup restore test or a manually orchestrated restore. A cold storage backup may also have different restore behavior and retrieval charges.
Budget tests separately from emergency restores
Set an annual restore testing schedule, then model each event by separating AWS Backup restore activity from created resources. Include restored data or retrieval charges where applicable, test environment runtime, new EBS volumes or database instances, network processing, logging, KMS requests, customer-managed KMS key charges, and cleanup.
A small-sample data restore validates access and permissions. It doesn’t necessarily prove that the full application can meet its recovery time objective. Full-scale tests cost more, but they expose capacity and dependency issues before an outage. A single test can exceed months of backup storage.
Account for restore evaluation and cleanup
Restore testing can involve backup evaluations. Backup Audit Manager can create separate evaluation-related charges, while AWS Config may add billing for configuration items used by controls. These charges are separate from AWS Backup charges for stored backup data.
Tag temporary recovery resources with a test identifier and an expiration date. Then review Cost Explorer after every drill. Leftover volumes, snapshots, test databases, elastic IP addresses, and other temporary infrastructure can cost more than the backup operation itself.
Service Exceptions That Change the Estimate
A recovery plan covering RDS, Aurora, S3, EFS, and EBS shouldn’t use one blended backup storage rate. Each service owns its backup behavior and applicable pricing rules. Restored EBS volumes and snapshot storage are service-side costs, not automatically AWS Backup charges.
The operational design matters too. Native replication, database read replicas, S3 replication, and AWS Backup copies can protect similar data. These options can generate different storage and transfer bills, while service and organization backup policies affect coverage and copies.
Amazon RDS backup allowances are regional
Automated backup allowances apply separately in each Region. Amazon RDS includes free backup storage for eligible automated backups up to 100% of the total provisioned database storage in each Region. This free backup storage applies only to eligible RDS automated backup storage under the service’s pricing rules, as described in Amazon RDS pricing.
A recovery copy in another Region remains a separate line in the model. It can incur AWS Backup copy charges, transfer charges between Regions, destination storage charges in a backup vault, and restored DB instance costs. Customer-managed KMS key usage and vault access controls can introduce configuration-dependent costs or permission requirements. The RDS allowance doesn’t make these AWS Backup or recovery charges free.
For Aurora workloads, use an Aurora Serverless v2 pricing model that includes retained backups and secondary-Region spending rather than focusing only on ACUs.
Amazon S3 needs object-level assumptions
An Amazon S3 backup requires attention to object count, data size, versioning, retention, requests, retrieval, and copy design.
AWS Backup supports S3 backup copies across accounts and Regions. Review current AWS Backup S3 documentation because copies of continuous backups don’t provide point-in-time restore capabilities in the destination.
Also review the underlying Amazon S3 pricing components, including storage, requests, retrieval, and transfer charges. S3 workloads with millions of small objects can produce a different cost pattern than a few large archives, even when total capacity matches.
Build an AWS Backup Cost Model
A good model has one row for each protected resource group and one column for each Region. Keep monthly recurring charges separate from the annual cost of planned recovery tests.
Use a four-part monthly formula
Use this structure for each workload:
| Cost component | Planning input | Billing owner | Service or charge source |
|---|---|---|---|
| Source backup storage | Average backup GiB retained in the primary Region | Source workload account | AWS Backup or source service |
| Transfer | Measured GiB copied from the source Region | Sending account | AWS Backup, source service, or standard AWS data transfer |
| Destination vault storage | Average retained GiB in the DR Region, normally in warm storage | Receiving or vault account | AWS Backup destination vault |
| KMS key usage | Encryption and decryption requests, plus key scope | KMS key-owning account | AWS KMS |
| Restored target resources | Provisioned capacity, restored GiB, and runtime | Recovery program or workload owner | Target service created by the restore |
| Service requests or retrieval | Request counts, retrieved GiB, and service-specific retrieval | Workload owner | Source or destination service |
| Tests and restores | Restore frequency, restored GiB, evaluations, and test infrastructure runtime | Recovery program or workload owner | AWS Backup and recovery services |
The billing owner identifies the account charged. The service or charge source identifies the system generating the line item.
The transfer row can involve cross-region data transfer. Confirm the correct line item for the specific copy path before approval.
Monthly cost = (average retained GiB-months × applicable regional rates) + (measured copied GiB × transfer rate) + KMS usage + service requests. Add annual restore frequency × restored GiB and test-resource runtime to annual restore testing costs.
Record the backup plan, copy path, and charge source for each workload. Then add service-specific costs such as S3 requests, RDS capacity during restore tests, or EBS volumes created for recovery validation. This approach prevents a transfer-only estimate from becoming the approved disaster recovery budget.
Validate these inputs in the AWS Pricing Calculator, then check the live AWS Backup and service pricing pages before approval.
Model three operating scenarios
Create a baseline protection case using typical daily change volume and ordinary retention. Add a high-change case for patch windows, data loads, or large database maintenance. Finally, create an incident case that assumes a full restore in the recovery Region.
The high-change case often reveals the largest recurring risk because the retention period and copy frequency affect destination backup storage. A 20 TiB database with modest capacity can still generate substantial transfer when actual changed blocks or objects are rewritten daily. Measure changed blocks or changed objects where possible, rather than relying on capacity utilization.
FAQ
Is there one AWS Backup price for cross-Region recovery?
No. Charges can include backup storage, copy requests, retention, and restore operations. Rates vary by protected service, Region, resource type, and account setup. Check the official pricing page for AWS Backup, the relevant service pricing page, and current documentation for each estimate.
Can a cross-Region copy go directly to cold storage?
No. AWS Backup doesn’t support creating cross-Region copies directly in that tier. Copies must first use a supported tier. Moving eligible backups to cold storage later may reduce storage charges, but recovery points have a 90-day minimum retention period. Deleting them earlier can create early-deletion charges.
Does the RDS free backup allowance cover disaster recovery copies?
Not automatically. Eligible automated RDS backup storage includes free backup storage up to the provisioned database size per Region. It doesn’t generally cover copied storage or destination recovery resources. If the design uses a cold tier, its minimum retention can still apply, so check current RDS and AWS Backup documentation.
Which account pays for source and destination charges?
Billing depends on account ownership, copy configuration, and the services involved. The source account may receive copy-related or outbound transfer charges, while the destination account usually receives copied storage charges. Restore and recovery resource charges follow the account using those resources.
Do recovery tests create additional charges?
Yes. Planned tests can add restore operation charges, temporary compute, storage, and network-related costs. Estimate the resources used during each test, not just the protected backup volume. Consult the relevant service pricing page and current AWS Backup documentation.
Can KMS keys or vault ownership change the estimate?
Yes. KMS key usage, key policies, cross-account permissions, and destination vault ownership can affect setup and ongoing charges. Confirm the key and vault requirements in current AWS Backup and KMS documentation, then assign charges to the owning account.
Plan for Recovery Cost, Not Storage Cost Alone
A complete AWS Backup pricing checklist follows the recovery path:
- Source backup storage
- Any applicable cross-Region transfer
- Destination vault storage
- KMS configuration
- Retention
- Restore resources
- Scheduled testing
AWS Backup costs are only one part of the bill. Underlying services can also add charges for restored databases, volumes, compute, requests, retrieval, networking, or logging.
Build estimates from measured change rates and named recovery scenarios, then recheck regional prices before implementation. A tested cross-Region copy is a recovery capability, not merely a backup line item.
