Most teams model AWS Backup pricing as $0.05/GB-month. That estimate breaks quickly once restores, cross-region copies, and S3-level charges show up on the bill.
AWS Backup pricing at a glance
Pricing sourced from the AWS Backup official pricing page. All rates are for US East (N. Virginia). Prices vary by region and are subject to change.
AWS Backup pricing breakdown
AWS Backup pricing breaks down into a few core components, but they don’t scale the same way. Storage is predictable, while restores, transfers, and service-level charges are where costs start to diverge.
Warm and cold storage
AWS Backup charges for storage per GB-month, but the pricing model changes depending on tier, service, and retention behavior.
- Warm storage (default): $0.05/GB-month for most services with immediate restore access
- Cold storage: 70-80% cheaper (e.g., $0.0125/GB-month for EBS)
- Minimum retention: 90 days for cold storage. Backups deleted before 90 days incur a prorated charge based on the remaining storage period (AWS Backup pricing).
In late 2025, AWS introduced a low-cost warm storage tier specifically for S3 backups at approximately $0.035/GB-month, about 30% lower than the standard warm tier.
The new tier requires backups to remain in the standard warm tier for at least 60 days before transitioning, and includes a one-time tiering fee per object.
One detail many teams miss is billing granularity. Some services (including EFS, S3, VMware, SAP HANA on EC2, and Timestream) are billed per GB-day, so even short-lived backups can incur a full day of charges (AWS Backup pricing).
Per-service pricing differences
AWS Backup pricing varies significantly by service, which makes blended cost estimates unreliable at scale.
- EBS: $0.05 warm / $0.0125 cold (incremental snapshots reduce actual usage) (AWS Backup pricing).
- DynamoDB: $0.10 warm / $0.03 cold (requires advanced features enabled) (AWS Backup pricing).
- RDS: $0.095/GB-month (Aurora snapshots free within retention window) (AWS Backup pricing).
- S3: $0.05/GB-month (no cold tier + small object overhead) (AWS Backup pricing).
Two environments with similar total data volumes can end up with very different backup costs depending on how data is distributed across services, how snapshots are stored, and which features are enabled.
As a result, accurate cost estimation requires modeling at the service level instead of just applying a single blended rate.
Restore costs
Restore costs are one of the most underestimated parts of AWS Backup pricing. While storage is predictable, recovery costs depend on how often and how granularly you restore data.
- Warm restores: $0.02/GB (some services like EBS and RDS may not charge for standard restores) (N2W AWS Backup pricing breakdown).
- Cold restores: $0.03/GB (N2W AWS Backup pricing breakdown).
- Item-level recovery: $0.50/request + per-GB charges (AWS Backup pricing).
Storage cost is fixed, but recovery cost scales with usage, making it harder to predict.
Cross-region and cross-account costs
Cross-region backups introduce both transfer and storage costs, which are easy to underestimate.
Transfer rates vary by service group, generally ranging from $0.02 to $0.04/GB, with storage billed separately in the destination region. (AWS Backup pricing).
There’s no charge for transfers within the same region, including cross-account copies. However, once you introduce multi-region disaster recovery, costs increase quickly, especially for large or frequently changing datasets.
Additional cost components most teams miss
Several secondary charges often show up outside AWS Backup itself, making the total cost harder to track.
- S3 API charges:
- GET/LIST requests are billed separately
- EventBridge events also add cost
- Backup search & indexing:
- $0.02 per million indexed items/month
- $0.07 per million items queried
- Audit Manager: $1.25 per 1,000
These charges are usually small individually, but they add a non-trivial percentage to total spend, especially in large environments.
AWS Backup cost optimization tips
In most environments, spend is shaped by retention choices, restore behavior, and how data moves across regions. These are the levers that have the biggest impact:
- Use cold storage only for true long-term retention. Cold storage can reduce costs significantly, but the 90-day minimum retention changes the math. It only makes sense for backups you’re confident you won’t need to delete early.
- Align retention with actual recovery requirements. Over-retention is one of the most common cost drivers. Many teams default to 60-90 days of warm retention when shorter windows would meet recovery and compliance needs.
- Design around restore behavior. Frequent restores (especially item-level) can materially increase cost. If your team regularly tests recovery or restores individual files, factor those charges into your cost model upfront.
- Be deliberate with cross-region replication. Cross-region backups improve resilience, but transfer costs scale with data change rate. High-change workloads (like EFS or databases) can drive significant ongoing spend.
- Watch for S3-specific cost amplification. Backing up S3 introduces API request charges and small object overhead, which can inflate costs beyond storage alone, especially for buckets with millions of small files.
- Use cost allocation tags, but don’t rely on them alone. Tags help break down costs in AWS Cost Explorer, but manual tagging is easy to miss and doesn’t guarantee full coverage, especially in fast-changing environments.
Is AWS Backup worth the cost?
AWS Backup is a reasonable choice for straightforward, single-cloud AWS environments where the team can invest in policy setup and ongoing tag management.
AWS Backup works well when:
- The environment is AWS-only with no Azure or GCP workloads.
- The team has the capacity to manually tag resources and build per-service backup plans.
- Backup requirements are primarily snapshot-based with infrequent restores.
- Compliance needs are met by basic retention policies without continuous posture monitoring.
AWS Backup starts to show limitations at enterprise scale. The manual tagging requirement means new resources can go unprotected until someone notices. There is no automatic resource discovery, data classification, or drift detection.
For teams running multi-account, multi-region environments, the operational overhead of maintaining backup policies often exceeds the direct storage cost. And for multi-cloud environments, AWS Backup simply does not cover Azure or GCP workloads.
AWS Backup alternatives and pricing comparison
AWS Backup works well for basic AWS-native backups, but teams often look at alternatives when costs become harder to predict or environments grow beyond a single cloud. Here’s how leading options compare:
These tools differ in how they handle backup complexity, visibility, and recovery.
- Eon focuses on Cloud Backup Posture Management (CBPM), automating coverage, enforcing policies, and enabling granular recovery across AWS, Azure, and GCP.
- N2WS builds on AWS snapshots with automation, scheduling, and cross-account management, but still relies on AWS-native constructs.
- Druva offers a fully managed SaaS approach, simplifying operations but with less control over underlying backup architecture.
Eon vs. AWS Backup: Which makes sense for your environment?
The choice depends on the size and complexity of the environment and whether the team operates across a single cloud or multiple clouds.
AWS Backup is a strong fit when:
- The environment is AWS-only
- Backup needs are primarily snapshot-based
- The team can manage tagging and policies consistently
But the model starts to break as environments scale. Manual tagging introduces coverage gaps, policies drift over time, and costs become harder to attribute across services and accounts.
Eon is designed for environments where:
- Workloads span multiple clouds and accounts
- Backup coverage needs to be enforced automatically, not manually maintained
- Teams require granular recovery and clear cost visibility across environments
The core difference is the operating model. AWS Backup relies on configuration and ongoing maintenance, while Eon treats backup as a posture problem, with continuous discovery, policy enforcement, and recovery readiness built in.
See the full comparison of Eon vs. AWS Backup
A different approach to backup at scale
If your backup costs keep increasing while visibility and coverage stay inconsistent, the issue usually is how backup is managed.
At scale, teams run into the same patterns:
- Resources get missed because tagging isn’t consistent
- Policies drift across accounts and regions
- Restore processes are rarely tested until they’re needed
We built Eon to solve those problems directly: by turning backup into a continuously enforced posture rather than a set of manual configurations.
If you’re spending more time managing policies than actually recovering data, it’s worth evaluating a different approach.
Request a demo to see how Eon handles backup posture, granular recovery, and cost visibility across AWS, Azure, and Google Cloud.
Frequently asked questions
How much does AWS Backup cost per month?
AWS Backup’s monthly cost depends on data volume, resource type, and storage tier. For a typical 1 TB EBS backup with 30-day warm retention, expect roughly $50/month in storage alone. Restore fees, cross-region copies, and API charges add to that total.
Is AWS Backup free?
AWS Backup is not free. It has no upfront cost, but all storage, restore, and transfer usage is billed based on consumption, with limited free backup included for some services like Aurora.
What are AWS Backup’s hidden costs?
AWS Backup’s most commonly missed costs include S3 GET/LIST API charges, EventBridge event fees, item-level restore charges ($0.50/request), Audit Manager evaluation fees, and the early deletion penalty for cold storage removed before 90 days.
How does AWS Backup cold storage work?
AWS Backup cold storage reduces storage cost but requires a 90-day minimum retention. Data moved to cold storage is cheaper to store but more expensive to restore and cannot be deleted early without penalty.
Does AWS Backup work with Azure or Google Cloud?
No, AWS Backup does not work with Azure or Google Cloud. It is designed exclusively for AWS services. Organizations running multi-cloud environments need separate backup solutions for each provider, or a cloud-native platform that covers all three.
How much does cross-region backup cost in AWS?
Cross-region backup in AWS costs $0.02-$0.04/GB for data transfer, depending on the resource type, plus ongoing storage charges in the destination region. There is no charge for cross-account copies within the same region.
Is AWS Backup cheaper than third-party backup tools?
Whether AWS Backup is cheaper depends on the scale and complexity of the workload. Per-GB storage rates are competitive for simple use cases. At enterprise scale, the total cost, including restores, API charges, and operational overhead, can make cloud-native platforms more cost-effective.
What is the cheapest way to back up data on AWS?
The cheapest way to back up data on AWS depends on retention needs. For short-term recovery, native features like Aurora automated backups and EBS snapshots are often included at no extra cost. For long-term retention, AWS Backup cold storage at $0.01-$0.0125/GB-month is competitive.
