# S3 Standard - Infrequent Access used where Intelligent Tiering would be cheaper

Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/s3-standard-ia-used-where-intelligent-tiering-would-be-more-cost-effective

Organizations often use the Standard - Infrequent Access (Standard-IA) storage class based on documentation and code that predate 2021 updates to the...

By: Paul Marcelin

Updated: 2026-09-28

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

# S3 Standard - Infrequent Access Used Where Intelligent Tiering Would Be Cheaper

The short version

Organizations often use the Standard - Infrequent Access (Standard-IA) storage class based on documentation and code that predate 2021 updates to the Intelligent Tiering storage class.

[Paul Marcelin](https://www.linkedin.com/in/marcelin/)

Infrastructure Developer @ Independent

AWS service

[AWS S3](https://www.pointfive.co/efficiency-hub/cloud-services/aws-s3)

Category

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

Reference

CER-0307

Type

Suboptimal Pricing Model

## Explanation

Why the waste happens and who it affects.

Intelligent Tiering became suitable as an initial S3 storage class even for objects that are small and/or will be deleted early. It also gained a heavily-discounted access tier. Older internal runbooks, lifecycle policies (including ones specified in infrastructure-as-code templates), scripts, programs, and public examples may still default to Standard-IA, inflating storage costs.

This inefficiency report compares Standard-IA with Intelligent Tiering. It is not intended to cover other storage classes. S3 storage is billed per gibibyte or GiB (powers of 2) rather than per gigabyte or GB (powers of 10), which matters for small objects and also for large volumes of storage.

Relative to the Standard storage class, the Standard-IA storage class offers a moderate, constant storage price discount but imposes a minimum billable object size of 128 KiB, a minimum storage duration of 30 days, and a per-GiB retrieval charge.

In contrast, AWS updated the Intelligent Tiering storage class in September, 2021, eliminating the minimum storage duration and exempting small objects from a monthly per-object monitoring and automation charge. Intelligent Tiering never had retrieval charges for its Frequent, Infrequent, and Archive Instant Access tiers (only optional Expedited retrievals from the opt-in Archive Access tier are charged). In November, 2021, AWS added the heavily-discounted Archive Instant Access tier.

For objects stored beyond a few months, Intelligent Tiering's progressive storage price discounts surpass Standard-IA's constant discount. Storage savings accumulate each month. Objects in the Intelligent Tiering storage class automatically move through progressively cheaper access tiers unless the objects are accessed. Intelligent Tiering also avoids Standard-IA's minimum billable object size and minimum storage duration penalties.

## Billing model

The pricing dimensions that drive this cost.

S3 has several billing dimensions, but storage volume (per GiB-month) usually dominates. Storage class determines pricing in each dimension.

- S3 Standard-IA offers a reduced per-GiB-month storage price compared to S3 Standard, but imposes constraints: a minimum billable object size (small objects are billed as if they were 128 KiB), a minimum storage duration (even if objects are transitioned or deleted early, storage is billed for 30 days), and a per-GiB retrieval fee (billed each time an object is accessed).

- S3 Intelligent Tiering imposes a per-object, per-month monitoring and automation charge for objects 128 KiB and larger, but has no minimum billable object size and no minimum storage duration. Small objects, exempt from the monitoring and automation charge, are always stored in the Frequent Access tier, at the same storage price as if they were in the Standard storage class.

- Within the Intelligent Tiering storage class, objects automatically progress (without lifecycle transition charges) through access tiers, from the Frequent Access tier (same storage price as Standard) to the Infrequent Access tier (same storage price as Standard-IA) after 30 days without access, to the Archive Instant Access tier (heavily discounted) after 60 more days (90 days total) without access. If accessed, an object returns to the Frequent Access tier and the countdown restarts. Retrieval does affect cost, even though there is no retrieval charge.

Waste can arise with Standard-IA because Intelligent Tiering's progressive storage price discounts overtake Standard-IA's constant discount, and/or because Intelligent Tiering avoids minimum billable object size and minimum storage duration penalties.

## How to detect

5 checks to find it in your estate.

- Identify S3 lifecycle policies that transition objects to Standard-IA, and replication rules that copy objects to Standard-IA, and evaluate whether Intelligent Tiering would save money based on actual access patterns.

- Review infrastructure-as-code templates and deployment scripts (including ones that specify lifecycle policies or replication rules), as well as operational scripts and programs that specify an initial storage class, for references to Standard-IA. Pay particular attention to work completed before 2022.

- Assess the share of objects in Standard-IA that are significantly smaller than 128 KiB, as these objects incur inflated storage charges, due to the minimum billable object size.

- Review retrieval and early deletion charges for objects in Standard-IA, to identify cases where the Intelligent Tiering storage class would be less expensive on balance.

- Review internal documentation that recommends the Standard-IA S3 storage class.

## How to fix

6 ways to remove the waste.

- For new S3 buckets, configure Intelligent Tiering rather than Standard-IA as the initial storage class in scripts, code, and replication rules. In lifecycle transitions from Standard, specify Intelligent Tiering rather than Standard-IA.

- Update internal documentation, runbooks, and reference architectures to reflect the 2021 updates to the Intelligent Tiering storage class. AWS eliminated the minimum storage duration, exempted small objects from the monitoring and automation fee, and added the heavily discounted Archive Instant Access tier.

- For existing Standard-IA objects, model the impact of switching to Intelligent Tiering by weighing one-time per-object transition charges (unfavorable) against expected per-GiB storage price discounts (favorable, and typically large) plus per-object monitoring and automation charges (unfavorable, but typically small) over time.

- If modeling predicts net savings, transition existing objects from Standard-IA to Intelligent Tiering using lifecycle transition rules. Keep in mind that the objects will enter the Intelligent Tiering storage class in its Frequent Access tier (more expensive than Standard-IA, but temporary) and progress to cheaper tiers over time (if not accessed).

- Keep using Standard-IA only for workloads with highly predictable, well-understood object size, access, and longevity patterns, for which lifecycle transition and expiration rules can be precisely tuned and retrieval charges, controlled.

- Establish periodic reviews of storage class selections across the organization to prevent regression to outdated defaults.

## Documentation

Vendor references for pricing and configuration.

- [How S3 Intelligent-Tiering works - Amazon Simple Storage Service  docs.aws.amazon.com](https://docs.aws.amazon.com/AmazonS3/latest/userguide/intelligent-tiering-overview.html)

- [Amazon S3 Pricing  aws.amazon.com](https://aws.amazon.com/s3/pricing)

- [Object Storage Classes - Amazon S3  aws.amazon.com](https://aws.amazon.com/s3/storage-classes/)

- [Amazon S3 Intelligent-Tiering Storage Class  aws.amazon.com](https://aws.amazon.com/s3/storage-classes/intelligent-tiering/)

- [Understanding and managing Amazon S3 storage classes - AWS Documentation  docs.aws.amazon.com](https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-class-intro.html)

- [Amazon S3 Intelligent-Tiering further automates storage cost savings by removing the minimum storage duration and monitoring and automation charge for small objects - September, 2021  aws.amazon.com](https://aws.amazon.com/about-aws/whats-new/2021/09/amazon-s3-intelligent-tiering-automates-storage-savings)

- [Announcing the new S3 Intelligent-Tiering Archive Instant Access tier - November, 2021  aws.amazon.com](https://aws.amazon.com/about-aws/whats-new/2021/11/s3-intelligent-tiering-archive-instant-access-tier)

## Related inefficiencies

[Browse the library](https://www.pointfive.co/efficiency-hub)

- AWS S3  CER-0334

### [Excessive S3 Request Costs from Filesystem-Oriented I/O Patterns](https://www.pointfive.co/efficiency-hub/inefficiencies/excessive-s3-request-costs-from-filesystem-oriented-i-o-patterns)

Amazon S3 bills for nearly every API request - LIST, HEAD, GET, PUT, COPY, and POST - independently of storage charges (DELETE and CANCEL requests are free). Workloads originally designed for locally-provisioned storage, where listing a...

Storage

- AWS S3  CER-0303

### [Orphaned Cloud Storage from Dropped External Delta Tables in Databricks](https://www.pointfive.co/efficiency-hub/inefficiencies/orphaned-cloud-storage-from-dropped-external-delta-tables-in-databricks)

When external Delta tables are dropped from Databricks Unity Catalog or the legacy Hive metastore, only the table metadata is removed - the underlying data files in cloud object storage (such as S3, ADLS, or GCS) remain untouched and...

Storage

- AWS S3  CER-0237

### [Unexpired Non-Current Object Versions in S3](https://www.pointfive.co/efficiency-hub/inefficiencies/unexpired-non-current-object-versions-in-s3)

When S3 versioning is enabled but no lifecycle rules are defined for non-current objects, outdated versions accumulate indefinitely. These non-current versions are rarely accessed but continue to incur storage charges. Over time, this...

Storage

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

