AWS S3 Express One Zone cost: pay more to store, less per request
S3 Express One Zone charges far higher storage (around $0.16/GB-month) but much lower per-request costs than S3 Standard, in a single AZ for low latency. For request-heavy, latency-sensitive workloads it can be cheaper overall. Here is the math.
Quick answer
S3 Express One Zone stores data in a single Availability Zone for single-digit-millisecond latency. It flips the S3 cost model: storage is much higher (around $0.16/GB-month versus $0.023 for Standard) but request costs are far lower. For request-heavy, latency-sensitive workloads with modest data, it can be cheaper overall; for large, request-light data, Standard wins.
S3 Express One Zone is a high-performance S3 storage class for latency-sensitive workloads, keeping data in one Availability Zone to cut latency to single-digit milliseconds. Its pricing inverts the usual S3 tradeoff, so whether it saves money depends entirely on your ratio of requests to stored data.
The inverted cost model
| Dimension | Express One Zone | S3 Standard |
|---|---|---|
| Storage | ~$0.16 / GB-month | ~$0.023 / GB-month |
| Request cost | Much lower per request | Higher per request |
| Availability zones | One (lower durability scope) | Multiple |
| Latency | Single-digit ms | Higher |
Storage costs several times more than Standard, but requests cost a fraction. So a workload that makes enormous numbers of requests against a modest amount of data, where request cost dominates on Standard, can be cheaper on Express One Zone despite the higher storage rate.
When Express One Zone is cheaper
The crossover is the request-to-storage ratio. High request volume against small data (hot working sets, ML training data read repeatedly, analytics on frequently-accessed objects) favors Express One Zone, because the request savings outweigh the storage premium and you get the latency benefit. Large, cold, or request-light data favors Standard or an infrequent-access class, where the low storage rate matters most.
The single-AZ tradeoff
Data lives in one Availability Zone, so it does not have the multi-AZ resilience of Standard. Use it for data you can regenerate or that is a performance-optimized copy, not as the sole durable store of irreplaceable data. This is the same single-zone tradeoff as other one-zone options.
Choosing the class
Estimate your request and storage volumes and compare the total on each class, rather than picking by storage rate alone, the same whole-cost thinking as the S3 storage class comparison. Express One Zone is a targeted tool for request-heavy, latency-sensitive workloads, not a default.
FAQ
How is S3 Express One Zone priced?
With much higher storage (around $0.16 per GB-month versus $0.023 for S3 Standard) but far lower per-request costs, storing data in a single Availability Zone for single-digit-millisecond latency. The model is inverted from Standard, so cost depends on your request-to-storage ratio.
When is S3 Express One Zone cheaper than Standard?
For workloads with high request volume against modest data, where request cost dominates on Standard. The lower per-request cost outweighs the higher storage rate, and you gain low latency. For large, cold, or request-light data, Standard's low storage rate makes it cheaper.
What is the tradeoff with S3 Express One Zone?
It stores data in a single Availability Zone, so it lacks the multi-AZ resilience of Standard. Use it for regenerable data or performance-optimized copies, not as the sole durable store of irreplaceable data. You trade broader durability for latency and request cost.
How do I decide between Express One Zone and Standard?
Estimate your request and storage volumes and compare the total cost on each class, not the storage rate alone. High requests against small data favors Express One Zone; large or request-light data favors Standard or an infrequent-access class. The request-to-storage ratio is the deciding factor.
Is S3 Express One Zone good for ML training?
Often yes, for training data read repeatedly at high request volume, where the low per-request cost and single-digit-millisecond latency both help. Keep it as a performance copy of data that also lives durably elsewhere, since it is single-AZ.
Does C3X estimate S3 cost across classes?
C3X prices S3 buckets from your Terraform. Because class cost depends on storage volume, request counts, and access patterns, you provide those as usage assumptions to compare Express One Zone against Standard and other classes for your workload.
What to do next
Compare S3 classes for your workload before you commit. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.
Pricing references
Related posts
- S3 request fees explained: when they matter more than storage
PUT is $0.005/1K. GET is $0.0004/1K. For high-frequency small-object workloads, request fees can exceed storage fees by 100x. Here's the full request pricing matrix across all storage classes, when fees dominate, and the architectural patterns that keep them low.
- S3 request cost surprise: when API calls beat storage on the bill
S3 charges per request, not just per GB stored, so a workload making millions of small GET, PUT, or LIST calls can pay more for requests than for storage. Here is why it happens and how to cut request cost.
- AWS Macie cost: per GB of S3 data evaluated for sensitive data
Macie bills a per-bucket inventory charge plus per GB of S3 objects analyzed for sensitive data. Scanning entire large buckets on every run drives the bill. Sampling and scoping to sensitive data are the levers. Here is the model.
- EFS vs EBS vs S3 cost: pick by access pattern, not the per-GB rate
S3 (~$0.023/GB) is cheapest, EBS (~$0.08) middle, EFS (~$0.30) priciest, but they're not interchangeable. Here's how to match the service to the access pattern and avoid paying 13x by using EFS where S3 would do.
Share this post
Try C3X on your own Terraform
Free and open source. No API key required. One command to install, one command to estimate.