Book a demo
Cloud Efficiency Hub

Misaligned S3 Storage Tier Selection Based on Access Patterns

The short version

While moving objects to colder storage classes like Glacier or Infrequent Access (IA) can reduce storage costs, premature transitions without analyzing historical access patterns can lead to unintended expenses.

John Webb

Data Solutions Engineer @ Ollion

AWS service
AWS S3
Category
Storage
Reference
CER-0160
Type
Suboptimal Tier or SKU

Explanation

Why the waste happens and who it affects.

Retrieval charges, restore time delays, and early delete penalties often go unaccounted for in simplistic tiering decisions. This inefficiency arises when teams default to colder tiers based solely on perceived "age" of data or storage savings - without confirming access frequency, restore time SLAs, or application requirements. Unlike inefficiencies focused on underuse of cold storage, this inefficiency reflects overuse or misalignment, resulting in higher total costs or operational friction.

Billing model

The pricing dimensions that drive this cost.

S3 is billed by storage class, with additional charges for data retrieval, API requests, and minimum storage durations in cold tiers. While cold storage (e.g., Glacier, Infrequent Access) offers lower per-GB storage pricing, retrieval costs and minimum duration charges can outweigh savings if access patterns are not well understood or if data is accessed frequently or unpredictably.

How to detect

5 checks to find it in your estate.

  • Review historical access patterns for S3 buckets before applying lifecycle transitions to colder storage classes
  • Evaluate whether buckets or prefixes in IA or Glacier tiers are being accessed more frequently than expected
  • Check for retrieval operations, restore requests, or early delete penalties that may offset storage savings
  • Assess whether application SLAs or workloads are sensitive to Glacier restore latency
  • Identify transitions that occur uniformly across all objects without regard to access variability

How to fix

5 ways to remove the waste.

  • Use S3 Storage Class Analysis (by bucket, prefix, or object tag; its recommendations cover transitions from S3 Standard to S3 Standard-IA only), S3 Storage Lens advanced-tier activity metrics for prefix-level request trends, and server access logs or CloudTrail data events when per-object access detail is required, to analyze access frequency before applying lifecycle transitions
  • Apply intelligent-tiering selectively where access patterns are unpredictable
  • Avoid bulk transitions to IA or Glacier for data with unclear or variable access characteristics
  • Regularly audit lifecycle policies and revise based on actual usage patterns
  • Educate teams on the full cost model of cold storage (e.g., retrieval fees, early deletion penalties, restore time delays)

Documentation

Vendor references for pricing and configuration.

Browse the library