> ## 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 Request-Heavy S3 Data to Express One Zone

> Move request-heavy S3 data to S3 Express One Zone, where requests are much cheaper.

S3 Express One Zone stores data in a single Availability Zone with higher storage prices but much lower request prices than S3 Standard. For buckets that pay far more for requests than for storage, moving the data can cut the bill. nOps finds S3 Standard buckets where the request saving outweighs the higher storage price.

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

## Why it matters

Workloads such as analytics scratch space, ML training data and build caches can spend most of their S3 bill on GET and PUT requests.

## How nOps finds it

nOps reads the last 7 complete days of S3 billing. A bucket is flagged when it was billed for on-demand PUT/LIST and GET requests on all 7 days and holds only Standard storage. The saving is the request cost times the difference between the Express One Zone and Standard request prices, minus the extra storage cost at the Express One Zone storage price, using public prices for the region, scaled to a month. It must be at least \$25 a month. Express One Zone's per-GB charge on the part of each request above 512 KB is not counted.

## Before you start

Applications that can use a directory bucket and its zonal endpoint, compute in the same Availability Zone, and permission to create directory buckets (`s3express:CreateBucket`).

## How to implement

1. Check that the data is request-heavy because of many small objects (under 512 KB), and that it can live in a single Availability Zone.
2. Create a directory bucket in the Availability Zone where your compute runs (**S3 → Directory buckets → Create bucket**).
3. Copy the data, or change the workload to write to the new bucket.
4. Update applications to use the directory bucket. They may need a newer SDK and session-based authentication.
5. Keep a copy in a regional bucket if the data must survive an Availability Zone outage.

## Risks and considerations

* Express One Zone stores data in one Availability Zone, so an outage there makes the data unavailable.
* Large objects pay per-GB upload and retrieval charges that this estimate does not include.
* Directory buckets do not support every S3 feature, such as some lifecycle and replication options.
* To roll back, point the workload back at the original bucket.

## Related

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