> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Stop Lifecycle Transitions of Small S3 Objects

> Stop lifecycle rules from moving small or short-lived S3 objects to classes where the fees cost more than the storage saves.

Moving objects to Glacier, Deep Archive, Glacier Instant Retrieval, Standard-IA or One Zone-IA has a charge per object, and those classes add per-object overhead or a minimum billable size. For small objects, or objects deleted soon after they move, these charges can cost more than the cheaper storage saves. nOps finds lifecycle transitions that lose money and estimates the saving from keeping that data in S3 Standard.

| | |
| - | - |
| **Cloud** | AWS |
| **Category** | Storage |
| **Service** | Amazon S3 |
| **Action** | Modify |
| **Effort** | Low |
| **Restart needed** | No |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 7 days |
| **Source** | nOps |

## Why it matters

A lifecycle rule that applies to every object in a bucket often moves millions of tiny files, each paying a transition fee.

## How nOps finds it

nOps reads 50 days of S3 transition, overhead and storage charges for each bucket and target class. A class is flagged when transitions ran in the last 3 days, started at least 37 days ago, and the data in the class has not grown more than 25% in 30 days. For the last 7 days, nOps compares the transition charge plus per-object overhead with what the class saves on storage, using public price ratios applied to your billed cost. The saving is the sum of the losses for each losing class, scaled to a month, and must be at least \$20 a month. Intelligent-Tiering transitions are not included.

## Before you start

Permission to update lifecycle rules (`s3:GetLifecycleConfiguration`, `s3:PutLifecycleConfiguration`).

## How to implement

1. Find the rule that transitions data to the class: `aws s3api get-bucket-lifecycle-configuration --bucket BUCKET`.
2. If objects are small, add an object size filter so only larger objects move, for example `ObjectSizeGreaterThan` of 131072 bytes (128 KB).
3. If objects are deleted soon after they move, remove the transition, or transition only data you keep for many months.
4. Write back the full edited configuration with `put-bucket-lifecycle-configuration`, since it replaces every rule.
5. Update Terraform or CloudFormation with the same change.

## Risks and considerations

* The transition charge stops at once. Overhead on objects already moved stops only as they expire or are removed.
* Check that no retention or compliance requirement depends on the archive class before changing the rule.
* To roll back, restore the original lifecycle rule.

## FAQs

> [accordion] Why do small objects lose money?
>
> Each transition is charged per object, and archive classes add metadata per object, while IA and Glacier Instant Retrieval bill objects under 128 KB as 128 KB.

## Related

* [Move S3 Data Out of Standard-IA](https://help.nops.io/inform/supported-recommendations/move-s3-data-out-of-standard-ia)
* [Switch S3 Bucket to Intelligent-Tiering](https://help.nops.io/inform/supported-recommendations/switch-s3-bucket-to-intelligent-tiering)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.