# Misaligned S3 Storage Tier Selection Based on Access Patterns

Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/misaligned-s3-storage-tier-selection-based-on-access-patterns

[Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) 

# Misaligned S3 Storage Tier Selection Based on Access Patterns

## Explanation

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. 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.

## Relevant Billing Model

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.

## Detection

- 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

## Remediation

- Use S3 Storage Lens or CUR data to analyze per-object or per-prefix 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)

## Relevant Documentation

[Amazon S3 Storage Classes](https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-class-intro.html) 
[S3 Lifecycle Configuration](https://docs.aws.amazon.com/AmazonS3/latest/userguide/lifecycle-configuration-examples.html) 
[S3 Pricing](https://aws.amazon.com/s3/pricing/)

[Submit Feedback](https://hub.pointfive.co/inefficiencies/misaligned-s3-storage-tier-selection-based-on-access-patterns)

## At a glance

Reference

CER-0160

Cloud provider

AWS

Service

AWS S3

Category

[Storage](https://www.pointfive.co/efficiency-hub/service-category/storage)

Inefficiency type

Misconfigured Storage Tier

## Contributed by

- John Webb 

### John Webb

Data Solutions Engineer @ Ollion

[LinkedIn](https://www.linkedin.com/in/johnhwebb/)

---
Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.