Practical guide
S3 Standard pricing: estimate storage and request costs
calculate S3 Standard storage and requests. Includes a worked example, calculator scope, and practical questions.
Updated · Sources checked
Storage is only one component of an S3 estimate
S3 Standard combines stored data with separately priced request activity and other applicable features. A bucket with frequent small operations can have a different cost shape from one that stores the same bytes with little activity.
The calculator covers first-tier S3 Standard storage and common read and write requests in US East. It is not a complete quote for replication, delivery, every request type, or other storage classes.
Worked example: stable storage and repeated reads
Suppose a bucket holds an average 2,000 GB throughout a hypothetical month. Applications make two million supported write requests and 20 million supported read requests.
Using S as the storage price per GB-month, W as the price per write request, and R as the price per read request, the modeled subtotal is 2,000S + 2,000,000W + 20,000,000R. If official request prices are listed per 1,000 requests, divide the counts by 1,000 before multiplying by those listed prices.
Now suppose caching reduces supported read requests to five million without changing storage or writes. The modeled difference is 15 million read requests times the read-request price. It does not reduce storage cost automatically or prove that all outbound transfer disappears.
Use average stored capacity
A bucket growing during the month should not be priced as though its ending balance existed for the entire month. Preserve a daily or interval-based capacity series when growth is material. Also count retained versions and other stored data that remain billable; the visible latest object versions may not represent the total.
The tool has a modeled storage-tier limit and excludes later storage tiers, transfer, replication, lifecycle transitions, and additional features. A workload outside that range needs a broader estimate instead of extrapolating the first-tier rate indefinitely.
Use actual request categories where available. Application operations can involve several storage requests, especially uploads with multiple parts or workflows that first check object metadata.
Frequently asked questions
Is one file upload always one request? Not necessarily; count the operations generated by the actual upload workflow.
Should I enter only the bucket size on the last day? Use representative stored capacity for the period, especially when the bucket grows or shrinks substantially.
Calculate your scenario
Use the s3 cost calculator. Keep the displayed region, pricing date, billing units, and exclusions alongside your result. The arithmetic examples above illustrate usage or explicitly hypothetical rates; they are not AWS quotes.
Source
Billing structure checked against official AWS documentation on September 6, 2026.