AWS EBS Snapshot Cost Optimization: The Ultimate Guide

Hundreds of snapshots are often created daily by an engineering team or generated automatically by AWS policies to back up data on Amazon Elastic Block Storage (EBS). Outdated backups accumulate quickly, generating unnecessary costs.

In this complete guide, we'll walk you through the process of how to cost optimize your EBS snapshots to save on your AWS bill — with updated best practices, AWS-native automation tools, and strategies to avoid common pitfalls.

First, let's quickly dive into the basics of how Snapshots work and how they are charged.

What are Amazon EBS Snapshots?

EBS Snapshots allow secure and efficient backups of storage volumes. By using snapshots, you can copy data to Amazon S3, ensuring easy access in case of need.

Amazon EBS snapshots work like a version control system. They save the current version of the data, and each new snapshot is similar to a "commit," containing only the changes made since the previous snapshot. This method allows efficient backup management by storing only the differences between versions in the subsequent snapshot, which saves storage space and simplifies the recovery of specific data from a particular point in time.

How do orphaned snapshots accumulate and drive up costs?

An engineering team creates many, many snapshots per day — or they can be generated en masse by automated AWS backup policies. If you delete an instance in AWS, the EBS volume is also deleted, but the snapshots remain. It is easy to forget about these orphaned snapshots as they continue to generate storage costs.

EBS Snapshot pricing: a quick intro

Amazon EBS charges for snapshots by the gigabyte-month. Charges are based on the size of your snapshot and how long you keep it. AWS snapshots are stored incrementally, i.e. the first snapshot of your instance is a full copy and each next snapshot is an incremental backup of what changed.

For the Standard tier, you incur charges only for changed blocks that you store. For the Archive tier, you incur charges for all snapshot blocks that you store. You also incur charges to retrieve snapshots in the Archive tier. Archive snapshots that contain infrequently accessed data but must be retained for compliance, auditing, or long-term recovery.

Current Amazon EBS snapshot pricing (as of 2026):

• Standard tier: $0.05 per GB-month
• Archive tier: $0.0125 per GB-month (75% savings)
• Retrieval from Archive: $0.03 per GB (one-time charge)

Here are some example scenarios from AWS for each storage tier:

Standard tier: You have a volume that stores 100 GB of EBS snapshot data. You incur charges for the full 100 GB of data for the first snapshot (snap A). At the time of the next snapshot (snap B), you have 105 GB of data. Amazon EBS then bills you for only the additional 5 GB of storage for incremental snap B.

Archive tier: You archive snap B. The snapshot then moves to the Archive tier, and Amazon EBS bills you for the full 105 GB snapshot block.

Keep in mind that the cost is NOT limited to the storage of the snapshots themselves. The frequent creation and management of snapshots can require additional time and resources to configure and maintain appropriate retention policies, as well as to monitor and optimize storage use.

Related Content

The Definitive Guide to AWS Rightsizing

Cut cloud waste and pay only for what you need

Download Now

Delete vs. Archive vs. Keep: Decision Framework

Not all old snapshots should be treated the same way. Here's how to decide:

Delete immediately when snapshots are:

• Older than your compliance requirements (if no regulatory need exists)
• Associated with terminated projects or decommissioned applications
• Test/development snapshots with no production dependencies

Archive when snapshots are:

• Required for long-term compliance (90+ days minimum due to AWS's 90-day archive minimum)
• Infrequently accessed but must be retained
• End-of-project or final state snapshots with low restore probability
• 30+ days old and no longer part of active recovery workflows

Keep in Standard tier when snapshots are:

• Part of active disaster recovery plans requiring fast restore (Archive restore takes 24-72 hours)
• Less than 30 days old and frequently referenced
• Production-critical with RTO (Recovery Time Objective) under 1 hour
• Part of active incremental chains where other snapshots depend on them

Why Deleting Snapshots May Not Reduce Costs

This is a common source of confusion: you delete a snapshot, but your AWS bill doesn't drop as expected. Here's why.

EBS snapshots are incremental and interdependent. When you delete a snapshot in the middle of a chain, AWS automatically redistributes the unique data blocks from the deleted snapshot to the remaining snapshots in the chain to preserve data integrity. Frequent modifications to data increase the size of incremental snapshots over time. This means:

• Deleting intermediate snapshots can fail to reduce costs if the unique blocks get redistributed to a more recent snapshot
• Shared snapshots owned by other AWS accounts don't incur charges for your account—only when you copy them to your account
• Billing lag: AWS billing data updates every 6-8 hours, so cost reductions from deletions may not appear immediately

Example: You have three snapshots: Snap A (100 GB), Snap B (+20 GB unique blocks), and Snap C (+10 GB unique blocks). If you delete Snap B, those 20 GB of unique blocks must be preserved somewhere for Snap C to remain valid. AWS moves them to the next snapshot, so your total storage stays at 130 GB.

Best practice: Use AWS Cost Explorer or a third-party tool to identify the true unique data in each snapshot before deleting. Focus on deleting the final snapshot in a chain or snapshots with high unreferenced data percentages (25%+).

EBS Snapshot Archive Tradeoffs

AWS's Archive tier offers 75% cost savings ($0.0125 vs. $0.05 per GB-month), but it comes with critical tradeoffs:

When Archive backfires:

• Archiving snapshots in active incremental chains: If you archive a snapshot that other snapshots reference, you're billed for the full snapshot size in Archive tier—not just the incremental delta. This can actually increase costs.
• Short retention needs: If you archive a snapshot and delete it after 30 days, you're still billed for 90 days. Archive only makes sense for retention horizons of 90+ days.
• Frequent restores: If you restore an archived snapshot multiple times, the $0.03/GB retrieval charge quickly erodes your 75% storage savings.

Rule of thumb: Archive tier saves money when (restore probability × $0.03/GB) + (storage cost over time) is less than Standard tier storage cost. For most use cases, this means snapshots with <5% annual restore probability and 6+ month retention.

Automate Retention with Data Lifecycle Manager and AWS Backup

Manual snapshot management doesn't scale. AWS provides two native tools to automate snapshot creation, retention, and deletion:

Amazon Data Lifecycle Manager (DLM)

DLM is purpose-built for EBS snapshots and AMIs. It automates snapshot creation on a schedule and enforces retention policies.

Example retention policy:

• Daily snapshots: Retain for 7 days
• Weekly snapshots: Retain for 30 days
• Monthly snapshots: Retain for 365 days

Key features:

• Tag-based targeting (e.g., all volumes tagged `Environment:Production`)
• Cross-region snapshot copies for disaster recovery
• Automatic archiving after a specified age
• Fast Snapshot Restore (FSR) support for instant volume creation

AWS Backup

AWS Backup is a centralized, cross-service backup solution. It supports EBS, RDS, DynamoDB, EFS, and more. Use AWS Backup when you need unified backup policies across multiple AWS services.

Key features:

• Backup plans: Define schedules, retention, and lifecycle transitions in one place
• Vault Lock: Enforce WORM (Write Once Read Many) for compliance (e.g., HIPAA, GDPR)
• Cross-account and cross-region backup: Copy backups to separate accounts for added security
• Point-in-time restore: Restore to any recovery point within your retention window

When to use AWS Backup over DLM:

• You're backing up multiple AWS services (not just EBS)
• You need centralized backup governance and compliance reporting
• You require immutable backups (Vault Lock)

When to use DLM:

• You only need EBS snapshot management
• You want simpler, tag-based automation
• You need Fast Snapshot Restore without the overhead of Backup vaults

Hidden Snapshot Costs

Beyond the per-GB-month storage charges, snapshots introduce hidden costs that can catch teams off guard:

1. Data transfer costs: Copying snapshots across regions incurs inter-region data transfer charges (typically $0.02/GB)

2. API call costs: Frequent `DescribeSnapshots`, `CreateSnapshot`, and `DeleteSnapshot` API calls can add up (especially in large environments with automation scripts polling every 5 minutes)

3. Fast Snapshot Restore (FSR): Optional features such as Fast Snapshot Restore have separate charges beyond standard snapshot storage costs. Enabling FSR costs $0.75 per snapshot per Availability Zone per hour—use sparingly and only for production-critical recovery scenarios

4. Compliance storage overhead: If you're required to retain snapshots for 7+ years, consider migrating older snapshots to EBS snapshot archive

5. Shared snapshot charges: If you share snapshots across AWS accounts, the receiving account is charged for any copies they create—not for accessing the original shared snapshot

Retention Policy Example

Here's a production-ready retention policy framework you can adapt:

Tagging strategy to enable this policy:

• `Environment`: `Production`, `Staging`, `Development`
• `SnapshotType`: `Daily`, `Weekly`, `Monthly`, `Annual`, `End-of-Project`
• `Compliance`: `Required`, `Optional`
• `Project`: `ProjectName` (for cost allocation)

Use these tags to create separate DLM policies for each snapshot type. DLM can automatically transition snapshots to Archive tier after a specified age (e.g., daily snapshots move to Archive after 30 days).

Reduce your AWS costs with nOps

Cleaning up outdated snapshots can eliminate unnecessary storage costs. But for most organizations, the larger savings opportunity comes from optimizing the rates paid for the cloud resources they continue to use.

nOps makes it easy to understand and optimize your EBS snapshot costs and other AWS costs with:

Commitment Management: Save 50-60% autonomously on AWS costs while reducing your lock-in and risk. The pricing model is a percentage of savings, ensuring you only pay for results.

Cost Visibility & Allocation: Understand which teams, products, and features are driving spend across multicloud, AI, Kubernetes, and SaaS—with anomaly detection, budgeting, forecasting, and reporting.

AI Insights: Identify opportunities to optimize token usage, model selection, caching, provisioned throughput, and batch processing.

nOps processes over $4 billion in cloud spend and was recently named #1 in G2's cloud cost management category. You can book a free savings analysis to find out how nOps can help you start saving today!

FAQ

Let's dive into a few frequently asked questions about Amazon Elastic Block Store snapshots, EBS pricing, and how to optimize the costs of snapshots stored.

Q: How long does it take for snapshot deletion to reflect in my AWS bill?

A: AWS billing data updates every 6-8 hours. Cost reductions from snapshot deletions typically appear in your Cost Explorer within 24 hours, but your monthly invoice reflects the pro-rated usage up to the deletion timestamp.

Q: Can I automate snapshot archiving with DLM?

A: Yes. DLM supports automatic archiving as part of a snapshot lifecycle policy. You can configure DLM to archive snapshots after a specified number of days (e.g., archive daily snapshots after 30 days).

Q: What happens if I restore an archived snapshot before 90 days and then delete it?

A: You're billed for the full 90-day minimum archive period, even if the snapshot or data restored exists for fewer days. Plan archive workflows carefully to avoid unexpected charges.

Q: Should I archive snapshots that are part of an incremental chain?

A: No. Archiving a snapshot in an active incremental chain can increase costs because AWS bills you for the full snapshot size in the Archive tier—not just the incremental delta. Archive only the final snapshot in a chain or snapshots with high unreferenced data (25%+).

Q: How do I identify which snapshots have high unreferenced data?

A: Snapshots do not save empty blocks, only the blocks that have changed, reducing storage size. Use the AWS EBS API (`ListSnapshotBlocks` and `GetSnapshotBlock`) to calculate unreferenced blocks, or use a third-party tool like nOps, CloudFix, or N2WS. Snapshots with >25% unreferenced data are typically safe candidates for archiving or deletion.

Q: Do EBS snapshot costs vary by EBS volume type?A: Snapshot storage pricing is separate from the underlying EBS volume type. The same snapshot pricing model applies whether the source uses General Purpose SSD, Provisioned IOPS SSD, or Throughput Optimized HDD. Costs depend on the snapshot data stored and its storage tier.