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

# Move S3 Data Out of Standard-IA

> Stop moving data to S3 Standard-IA when its retrieval and early-delete fees cost more than the storage discount.

S3 Standard-IA stores data for less than S3 Standard, but charges for every GB retrieved and for objects deleted before 30 days. When data in Standard-IA is read often or deleted soon after it moves, those fees can cost more than the discount. nOps finds buckets where keeping the data in S3 Standard would cost less.

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

Lifecycle rules that move everything to Standard-IA after a fixed number of days are common, and they backfire on data that is still in use.

## How nOps finds it

nOps reads the last 30 days of S3 billing. A bucket is flagged when it has at least $5 of Standard-IA storage, and its Standard-IA storage plus retrieval and early-delete fees exceed what the same data would cost in S3 Standard by at least $25 a month. The Standard cost uses the public price ratio between Standard and Standard-IA in the region. The saving is that difference.

## Before you start

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

## How to implement

1. Find the rule that transitions data to `STANDARD_IA`: `aws s3api get-bucket-lifecycle-configuration --bucket BUCKET`.
2. Remove that transition, or change it to `INTELLIGENT_TIERING`, which has no retrieval fees.
3. Write back the full edited configuration with `put-bucket-lifecycle-configuration`, since it replaces every rule.
4. Optionally copy frequently read objects back to Standard.
5. Update Terraform or CloudFormation with the same change.

## Risks and considerations

* Objects already in Standard-IA stay there unless you copy them back. Copying them early can itself trigger early-delete fees.
* To roll back, restore the original lifecycle rule.

## Related

* [Switch S3 Bucket to Intelligent-Tiering](https://help.nops.io/inform/supported-recommendations/switch-s3-bucket-to-intelligent-tiering)
* [Stop Lifecycle Transitions of Small S3 Objects](https://help.nops.io/inform/supported-recommendations/stop-lifecycle-transitions-of-small-s3-objects)
* [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.