Published on · Updated on
Updated pricing, lifecycle, copy, and restore-testing guidance.
To reduce AWS Backup costs without weakening recovery, start with actual backup usage, set schedules and retention to your recovery and compliance needs, and use a storage tier only when the resource and Region support it. AWS Backup charges for stored backup data, cross-Region transfer, restored data, and restore-testing evaluations; resource type and Region affect the details. Check the current AWS Backup pricing page before changing a plan.
AWS Backup has no setup charge or minimum fee. Its published pricing covers backup storage, backup data transferred between AWS Regions, data restored, and backup evaluations. Storage is generally measured as the average amount used during the billing month, though some resource types are billed by the day. Rates and billing units vary by resource, Region, and tier. Some related services can also bill separately: for example, Amazon S3 backups can incur S3 request, versioning, and EventBridge charges. See the AWS Backup pricing details for current rates and service-specific charges.
| Cost driver | What to review |
|---|---|
| Recovery-point storage | Stored data, retention period, resource type, Region, and the applicable warm or archive tier. |
| Backup copies | Storage in each destination vault and, for cross-Region copies, data transferred out of the source Region. |
| Restores and restore tests | Data restored, evaluation fees per tested recovery point, and any restored resources or requests charged by the underlying service. |
| S3 backup activity | AWS Backup storage plus S3 requests, EventBridge events, S3 Versioning, and restore requests where applicable. |
Use AWS Cost Explorer to compare AWS Backup spend by account, Region, and usage type over time. For line-item analysis, create a CUR 2.0 export through AWS Data Exports. Backup charges for resource types under full AWS Backup management can appear under the Backup service; S3 requests and EventBridge events may appear under those services, as described in the AWS Backup billing overview. Match cost data with an inventory of backup plans, vaults, resources, copies, and recovery points so a charge has an owner and a reason.
Look for overlapping schedules, copies that no longer serve a recovery or isolation requirement, long retention without an owner, and growth in stored data or restore activity. Confirm the workload owner, retention obligations, and recovery objective before changing protection. For account-wide cost analysis and allocation practices, see 10 AWS Cost Optimization Strategies for Engineers.
Choose backup frequency from the recovery point objective (RPO), and set retention from recovery, audit, and legal requirements. A daily, weekly, or monthly schedule is not a cost recommendation by itself; the right policy depends on how quickly the data changes and how far back the business must recover.
Many AWS Backup resource types support incremental backups, so later recovery points capture changes rather than another full copy. However, support and behavior are resource-specific. AWS Backup also retains the reference data needed for a full restore when an earlier recovery point expires. Do not estimate storage by multiplying each recovery point by the full source size, and do not assume deleting one old point will free that same amount of storage. Check the feature matrix and AWS Backup incremental-backup behavior, then compare the effect in billing data.
Before removing a schedule that overlaps a service-native backup, check how AWS Backup integrates with that resource. AWS documents that the relationship varies by service: some backups share the native service's backup infrastructure, while others form a separate backup layer. Disabling one plan without checking can either leave duplicate protection costs or remove a recovery path you still need. See how AWS Backup relates to native service backups.
AWS Backup recovery points are stored in backup vaults. The lifecycle of a recovery point is separate from the storage class of an object in an S3 bucket. S3 Standard, S3 Standard-IA, and S3 Glacier classes are not general choices for AWS Backup recovery points.
| Storage option | Where it applies | Cost point to check |
|---|---|---|
| AWS Backup warm storage | Default storage for supported recovery points in a backup vault. | Compare the service and Region rate with stored data and retention. |
| AWS Backup cold or archive lifecycle | Only resource types marked as supported in the AWS Backup feature matrix. Examples include EBS, EFS, and DynamoDB when advanced backup features are enabled. EBS cold lifecycle uses EBS Snapshots Archive. | Cold storage has a 90-day minimum. The recovery point's total retention must extend at least 90 days beyond the transition date; earlier deletion incurs the remaining minimum-period storage charge. EBS backups become full when transitioned to archive, which can change the storage economics. |
| AWS Backup lower-cost warm tier for S3 backups | S3 backup data within an AWS Backup vault. This is separate from AWS Backup cold storage and from S3 object storage classes. | Objects must remain in the standard warm tier for at least 60 days before transition. AWS Backup charges a one-time transition fee per object, so include object count and expected retention in the estimate. See the S3 backup tiering details. |
| Amazon S3 storage classes | Objects in the source S3 bucket, managed by S3 Lifecycle or object-level storage-class settings. | Compare transition-request charges, retrieval needs, minimum storage durations, and object size. These rules do not change the class of recovery points in a backup vault. |
Cold-tier and copy support varies by resource and Region. Check the current AWS Backup feature availability table for the exact resource before relying on a lifecycle transition. For example, AWS Backup cold lifecycle is not supported for standard Amazon RDS or S3 backups; S3 backups instead have the separate lower-cost warm tier described above. For S3 object transitions, use the applicable S3 Lifecycle transition rules and constraints.
Do not enable an archive transition solely because its storage rate is lower. Include the 90-day retention commitment, possible conversion of incremental EBS backups to full archive snapshots, retrieval charges, and the restore time your workload can tolerate. AWS's backup-plan lifecycle guidance describes these behaviors.
Copy backups to another account or Region when your recovery design calls for isolation, regional recovery, or data residency. A copy creates another stored recovery point. Cross-Region copies add data-transfer charges billed to the account sending the data; destination storage is billed to the account receiving it. A same-Region cross-account copy still uses destination storage even though AWS Backup's cross-Region transfer charge does not apply. See the AWS Backup cross-Region billing rules.
AWS Backup cross-account copies require the source and destination accounts to belong to the same AWS Organizations organization. The organization management account must enable cross-account backup, and the destination vault's access policy must allow the copy. AWS Backup does not support cross-account copies from cold-tier storage. Review AWS's cross-account backup requirements before adding another account as a destination.
Not every resource supports every copy path in every Region. Check the resource and Region support table before writing a policy. Some continuous backups become periodic snapshots when copied, so point-in-time recovery may not be available from the copy. Copy jobs also depend on access to the source and destination vaults and compatible AWS KMS keys. For some resource types that are not fully managed by AWS Backup, AWS-managed keys cannot be shared for cross-account copies; a customer-managed key and the required key-policy permissions may be necessary. Review the current AWS Backup encryption requirements.
When copying S3 backups that use the lower-cost warm tier, the destination copy starts in the standard warm tier. The destination vault's tiering configuration controls when eligible objects move to the lower-cost tier. Include both the initial destination storage and any later transition fees in the estimate; AWS documents these S3 backup tiering behaviors.
These are examples, not a complete service list. Confirm current feature and billing details for every protected resource and Region before changing its plan.
AWS Backup restore testing has a charge for each recovery point successfully tested and for the amount of data restored. Depending on resource type, the restored resource may add service charges while it exists. S3 tests can also incur S3 PUT charges; testing a cold recovery point uses cold-restore pricing, and testing an archived EBS snapshot temporarily restores it to the standard tier. See the current restore-testing prices and exceptions.
Keep restore tests frequent enough to prove the recovery paths that matter, but scope selections to the resources and recovery points needed for that evidence. Set a validation window that gives the team time to check the result, then inspect the job's deletion status: AWS Backup can fail to remove a test resource, and S3 bucket cleanup can take several days. See AWS Backup restore-testing behavior.
Lifecycle expiration is usually easier to audit than ad hoc deletion, but confirm which recovery points, copies, and service-native backups a rule affects. Before deleting a recovery point, verify its owner, restore role, required retention, and any independent copy. Do not remove the only usable restore point just because it is old or large.
AWS Backup Vault Lock can deny deletion or lifecycle changes for recovery points in a locked vault. In compliance mode, the lock becomes immutable after its grace period, which must be at least 72 hours; retained recovery points continue to incur storage charges until their lifecycle ends. Check that minimum and maximum retention settings match the policy before locking a vault, especially when a recovery point is configured to remain indefinitely. Read the AWS Backup Vault Lock behavior and limits before enabling it.
Revisit costs when retention requirements, data change rates, copy destinations, or AWS pricing change. After each policy change, compare actual usage and charges with the prior period and confirm that the required recovery points remain available.
No. S3 storage classes apply to S3 objects, while AWS Backup manages recovery points in backup vaults. AWS Backup has a resource-specific cold or archive lifecycle and a separate lower-cost warm tier for S3 backups; check the service matrix and pricing page for the feature and Region you use.
Only after you confirm the recovery point is outside required retention, is not protected by Vault Lock, and is not needed as a separate copy or recovery path. Incremental backup reference data is managed by AWS Backup, so deleting one point does not guarantee a proportional reduction in billed storage.
No. AWS Backup charges for restore-test evaluations and restored data, and the underlying service can add charges for temporary restored resources or requests. Check the current pricing page and review cleanup status after each test.