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

# Switch S3 Bucket to Intelligent-Tiering

> Move S3 buckets with mostly untouched objects to Intelligent-Tiering, which moves cold objects to a cheaper tier automatically.

S3 Intelligent-Tiering moves objects that have not been accessed for 30 days to an Infrequent Access tier, and back again when they are read, with no retrieval fees. nOps finds buckets in S3 Standard where most objects were not touched over the last 30 days, and estimates the saving from the share of objects it can prove were not accessed.

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

## Why it matters

Many buckets hold data written once and rarely read again, but pay the S3 Standard price for all of it.

## How nOps finds it

nOps reads the last 90 days of S3 billing, including the object count from S3 Inventory. A bucket is flagged when it has at least $5 of Standard storage in the last 30 days, has an S3 Inventory report from the last 45 days, held only Standard storage with no lifecycle transitions for 90 days, and was billed for Standard storage on at least 85 of those days. Objects must average at least 128 KB. The share of objects not accessed is at least one minus object-level requests divided by the object count, and must be at least 50%. The saving is the Standard storage cost times that share times the price difference between the Frequent and Infrequent Access tiers, minus the Intelligent-Tiering monitoring fee, and must be at least $25 a month.

## Before you start

S3 Inventory enabled on the bucket (nOps needs its object count), and permission to update lifecycle rules (`s3:GetLifecycleConfiguration`, `s3:PutLifecycleConfiguration`).

## How to implement

1. Save the bucket's current lifecycle rules: `aws s3api get-bucket-lifecycle-configuration --bucket BUCKET`.
2. Add a rule that transitions objects to `INTELLIGENT_TIERING` after 0 days, keeping every existing rule. `put-bucket-lifecycle-configuration` replaces all rules, so write back the full merged configuration.
3. In the console: **S3 → bucket → Management → Create lifecycle rule → Move current versions of objects between storage classes → Intelligent-Tiering**.
4. Update Terraform or CloudFormation with the same rule.
5. Check after about a month that Intelligent-Tiering storage appears on the bill.

## Risks and considerations

* Savings start after objects go 30 days without access.
* Intelligent-Tiering charges a small monitoring fee per object, which is why small objects are excluded.
* The share is counted by objects, not bytes, so the real saving can differ.
* To roll back, restore the saved lifecycle rules. Objects already in Intelligent-Tiering stay there, with no retrieval fees.

## FAQs

> [accordion] Why does nOps need S3 Inventory?
>
> Billing shows requests but not how many objects a bucket holds. The Inventory object count lets nOps work out how many objects were not touched.

## Related

* [Move S3 Data Out of Standard-IA](https://help.nops.io/inform/supported-recommendations/move-s3-data-out-of-standard-ia)
* [Stop Lifecycle Transitions of Small S3 Objects](https://help.nops.io/inform/supported-recommendations/stop-lifecycle-transitions-of-small-s3-objects)
* [Expire Noncurrent S3 Object Versions](https://help.nops.io/inform/supported-recommendations/expire-noncurrent-s3-object-versions)
* [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.