AWS S3 Glacier Storage Classes Explained AWS S3 Glacier is a group of three Amazon S3 storage classes built for data you keep for a long time and rarely touch. You get lower storage rates in exchange for different retrieval speeds and cost trade-offs.

Picking the wrong class hurts. Enterprise backups, compliance records, disaster recovery copies, and historical archives can look cheap on the storage line while retrieval fees, restore delays, and minimum storage periods quietly erase the savings.

This guide compares Glacier Instant Retrieval, Glacier Flexible Retrieval, and Glacier Deep Archive: how each works, where each fits, and how to choose.

Key Takeaways

  • S3 Glacier means three distinct storage classes, not one archive tier.
  • Instant Retrieval allows direct reads; the other two require a restore first.
  • Deep Archive has the lowest storage rate but the slowest restores and a 180-day minimum.
  • Check object size, retrieval frequency, minimum duration, and recovery objectives before transitioning data.

What Is S3 Glacier and Why Does It Matter?

What is AWS S3 Glacier?

S3 Glacier is a set of Amazon S3 object-storage classes for data retained for long periods and accessed less often than active application data. Objects stay in ordinary S3 buckets. You still use the S3 console, APIs, and SDKs, plus encryption, object tagging, and S3 Lifecycle rules.

Permissions work the way they do elsewhere in S3:

  • Reading an object requires s3:GetObject (or s3:GetObjectVersion for a specific version).
  • Restoring an archived object requires s3:RestoreObject.
  • SSE-KMS objects also need the relevant KMS permissions.

One terminology point. The original standalone Amazon Glacier vault service is separate from these S3 classes, with its own APIs. AWS says the vault service no longer accepts new customers, while existing data stays accessible. That status doesn't apply to the S3 storage classes.

Why are S3 Glacier classes important for cloud storage?

The right class controls storage spend, supports retention obligations and disaster recovery, and keeps historical data reachable without holding everything in a hot tier.

The wrong one causes damage:

  • Unexpected retrieval charges
  • Early deletion fees when objects leave before the minimum duration
  • Restore delays that blow past the workload's recovery time objective

A note on scope: S3 Glacier manages AWS object storage. Lucidity works on a different layer, autonomous block storage optimization across AWS, Azure, and Google Cloud. It isn't an S3 Glacier management tool. Enterprises typically need separate cost strategies for S3 objects and for block-storage volumes.

Types of AWS S3 Glacier Storage Classes

The three classes serve different access patterns, urgency levels, and retention periods. They aren't interchangeable versions of one service.

Pricing below is US East (N. Virginia) list pricing, as of November 18, 2026. Confirm current figures with AWS before you commit.

Attribute Instant Retrieval Flexible Retrieval Deep Archive
API/Lifecycle identifier GLACIER_IR GLACIER DEEP_ARCHIVE
Access method Direct GET Restore, then GET Restore, then GET
Retrieval options Milliseconds Expedited, Standard, Bulk Standard, Bulk
Storage, per GB-month $0.004 $0.0036 $0.00099
Retrieval, per GB $0.03 $0.03 / $0.01 / free (Exp. / Std. / Bulk) $0.02 Std. / $0.0025 Bulk
Minimum storage duration 90 days 90 days 180 days
Minimum object billing 128 KB 40 KB metadata per object 40 KB metadata per object
Typical use Medical images, news media Backup, disaster recovery Compliance archives

S3 Glacier storage classes comparison of access costs and restore times

The identifiers matter. In lifecycle configuration, GLACIER_IR is Instant Retrieval, GLACIER is Flexible Retrieval, and DEEP_ARCHIVE is Deep Archive. Using GLACIER when you meant Instant Retrieval puts data behind a restore step.

S3 Glacier Instant Retrieval

Instant Retrieval is for archived objects that must stay readable through a normal S3 GET, with millisecond latency and no restore workflow. It suits data accessed rarely, about once per quarter, but needed immediately when someone asks.

AWS lists medical imaging, genomics, news assets, and image hosting as examples, and reports that Snap adopted it for long-lived, rarely accessed media. These are examples, not universal recommendations.

Trade-offs:

  • Direct access and simpler application behavior
  • Higher retrieval charges ($0.03 per GB)
  • 128 KB billing floor: smaller objects are billed as 128 KB
  • Frequent access may make another class cheaper

AWS states it offers up to 68% lower storage costs than S3 Standard-IA for data accessed once per quarter. Standard-IA has higher per-GB storage prices but lower data-access costs, so this isn't a blanket saving.

S3 Glacier Flexible Retrieval

Flexible Retrieval is restore-based. You request a restore, pick a retrieval tier, wait, then read a temporary copy. AWS suggests about one to two accesses a year.

The tiers:

  • Expedited: typically 1-5 minutes for objects under 250 MB. Without provisioned capacity, requests may be rejected when demand is high.
  • Standard: typically 3-5 hours.
  • Bulk: typically 5-12 hours, with free retrieval and free requests.

Flexible Retrieval Expedited Standard and Bulk restore tier comparison

It fits backups, older logs, archived datasets, and disaster recovery copies that can tolerate a wait of minutes to hours.

Watch the billing. The archived original keeps accruing charges while the restored copy is billed at the S3 Standard rate for the days you specify. Free Bulk retrieval doesn't remove that temporary storage cost.

S3 Glacier Deep Archive

Deep Archive is for data kept for years and almost never read: regulatory records, legal archives, historical datasets, and long-term disaster recovery copies.

AWS cites financial services, healthcare, and public-sector data retained 7-10 years or longer. Choosing the class doesn't by itself establish compliance.

Key facts:

  • Standard restores typically finish within 12 hours, Bulk within 48 hours
  • No Expedited option
  • Lowest storage price of the three at $0.00099 per GB-month
  • 180-day minimum storage duration
  • 40 KB metadata overhead per object

Deep Archive restore options pricing minimum duration and limitations

It's a poor fit for unpredictable recovery needs, same-day access requirements, frequent downloads, or retention shorter than 180 days. Deep Archive also can't transition out through Lifecycle; changing class means restoring and copying.

How to Choose the Right S3 Glacier Storage Class

Start with access pattern and recovery requirements, not the lowest monthly rate. AWS's own guidance points to archiving best practices that weigh object counts, lifecycle fees, early deletion, and restore charges next to storage price.

Match access frequency and recovery time

Sort each dataset into one of three buckets:

  • Rarely read but needed immediately (media libraries, medical images): Instant Retrieval
  • Occasionally restored (backups, older logs, analytics datasets): Flexible Retrieval
  • Almost never retrieved (compliance archives, long-term DR copies): Deep Archive

Then ask how often you'll retrieve, how much at once, and how long the business can wait. Document the recovery time objective before choosing any restore-based class.

Model total cost

Build the full cost picture, not just the storage rate:

  • Storage and per-GB retrieval
  • Request charges and lifecycle transition charges (priced per object moved)
  • Minimum-duration charges, early deletion, and temporary restored copies

Millions of tiny objects hit the 128 KB floor in Instant Retrieval and 40 KB overhead in Flexible Retrieval and Deep Archive. Small-object archives can cost more than the per-GB rate suggests.

Gather these inputs before you model:

  • Region, bytes stored, object count, and size distribution
  • Retention period and retrieved GB per tier
  • Restore frequency and early-transition events

Plug in current rates for your Region rather than a generic estimate.

Automate and govern

  • Use S3 Lifecycle rules with prefix, tag, age, and size filters. Since September 2024, new configurations exclude objects under 128 KB by default.
  • Allow transitions from Instant Retrieval to Flexible Retrieval or Deep Archive, and from Flexible Retrieval to Deep Archive. Lifecycle will not move Instant Retrieval objects before 90 days.
  • Keep Object Lock and legal holds in place across class transitions, and test rules against versioning and deletion policies.
  • Monitor with S3 Storage Lens, Cost Explorer (S3: API Requests - Glacier), and CloudWatch, and track restores with s3:ObjectRestore:Completed events.

What to Check Before Finalizing a Storage Class

  • Don't base the choice on storage price alone. Model retrieval frequency, urgency, object size, and request volume.
  • Confirm restore mechanics. Apps must handle async retrieval, and restored copies expire. Restoring does not change class; a permanent move needs a post-restore copy via CLI, SDKs, or REST API (not the S3 console).
  • Re-verify pricing and windows. Rates, retrieval times, and minimums change; check them before implementation.
  • Run a restore drill. Test lifecycle rules and recovery with representative objects for compliance, backup, and DR. Batch Operations completion only means requests started, not that objects are readable yet.

Conclusion

S3 Glacier includes three classes, each with a different balance of access speed, storage cost, retrieval cost, and retention:

  • Instant Retrieval fits archives that need direct access
  • Flexible Retrieval suits restore-based archives with moderate recovery expectations
  • Deep Archive fits long-term data that can wait the longest

Base the decision on documented access patterns, recovery objectives, lifecycle policies, and a current total-cost model. Storage price is only one line of that model.

Frequently Asked Questions

What are the three S3 Glacier storage classes?

Glacier Instant Retrieval, Glacier Flexible Retrieval, and Glacier Deep Archive. Instant offers millisecond direct access, Flexible needs a restore taking minutes to hours, and Deep Archive suits rarely accessed data with the slowest restores.

What is the difference between S3 Glacier Instant Retrieval and Flexible Retrieval?

Instant Retrieval supports direct object access with a normal GET. Flexible Retrieval requires a restore request and offers Expedited, Standard, and Bulk tiers.

Which S3 Glacier storage class is cheapest?

Deep Archive has the lowest storage rate ($0.00099 per GB-month in US East, N. Virginia). Retrieval fees, the 180-day minimum, and slow recovery also affect total cost.

How long does it take to retrieve data from S3 Glacier?

Instant Retrieval takes milliseconds. Flexible Retrieval typically takes 1-5 minutes (Expedited), 3-5 hours (Standard), or 5-12 hours (Bulk). Deep Archive typically takes up to 12 hours (Standard) or 48 hours (Bulk).

Do you need to restore objects from S3 Glacier?

Not for Instant Retrieval, which supports a normal GET. Flexible Retrieval and Deep Archive require a restore request before the object can be downloaded.

How do you choose between S3 Glacier Flexible Retrieval and Deep Archive?

Compare retrieval frequency, acceptable delay, retention period, and total cost. Choose Deep Archive only if data is rarely read, retained 180 days or more, and can tolerate 12-48 hour restores.