Summary

  • Amazon S3's current Lifecycle default prevents objects smaller than 128 KB from transitioning to any storage class. A configuration created before September 2024 can retain an older default that let those objects move to S3 Glacier Flexible Retrieval or Deep Archive.
  • Creating, editing or deleting a rule switches that older configuration to the newer default unless the operator explicitly selects the prior behavior or uses a custom object-size filter. The change affects transition eligibility, not the existence of the objects.

A small rule edit can move the boundary for every small file

An operator opens an old S3 Lifecycle configuration to change one rule. The intent may be narrow: adjust a prefix, timing or destination. Yet the configuration carries another decision that is easy to miss. Before September 2024, S3's default permitted objects below 128 KB to move into Glacier Flexible Retrieval or Deep Archive. The current default prevents sub-128-KB transitions to any storage class. AWS says old configurations keep their prior behavior until modified; creating, editing or deleting rules brings in the new default.

The threshold has a cost logic. Each transition is a billable request. For tiny objects, those requests can cost more than lower storage rates save. Archiving in Glacier Flexible Retrieval or Deep Archive also adds 40 KB of billed metadata per object: 8 KB at S3 Standard rates and 32 KB at the archive-class rate. AWS chose a conservative default for the smallest files. That choice can still surprise a customer whose lifecycle plan assumed the earlier behavior.

The boundary is configurable. AWS shows an object-size filter that admits small objects to a transition rule, and its lifecycle API exposes a choice between the old storage-class-specific default and the all-classes 128-KB default for general-purpose buckets. A custom size filter takes precedence. The right setting depends on object counts, sizes, transition requests, duration and retrieval needs; AWS's documentation alone cannot price a particular bucket.

Before approving a rule edit, look at the configuration's current default and the size distribution of objects eligible for the rule. Then compare the resulting transition policy with what the team intended. A successful update response only proves the configuration was accepted. The economics live in the objects that will now stay in their current class or move under an explicit exception.

Sources