Practical guide
S3 cold storage: check small objects and retention before moving data
evaluate S3 storage class minimum size and duration rules. Includes a worked example, calculator scope, and practical questions.
Updated · Sources checked
Logical bytes may differ from billable storage
A storage-only multiplication assumes the entered quantity matches billable capacity. For classes with minimum billable object sizes, many tiny objects can make that assumption wrong. Minimum storage durations can also create charges when data is removed or transitioned too early.
The comparison tool does not apply these per-object or lifecycle rules. Use it as a storage-rate comparison after determining the appropriate billable quantity, and keep any duration adjustments outside its subtotal.
Worked example using hypothetical minimums
Imagine a fictional class with a 100 KB minimum billable object size. One million objects of 10 KB contain ten billion logical bytes, but the hypothetical minimum produces 100 billion billable bytes. In decimal units, that is 10 GB of data priced as 100 GB.
This tenfold difference comes from the example’s per-object minimum, not from replication or a provider markup. These numbers are invented to explain the method and are not the current minimums of S3 Standard-IA or Glacier Instant Retrieval.
Now suppose the fictional class requires 90 days of storage and the data is removed after 30 days. A naive one-month storage estimate misses the remaining minimum-duration obligation. Use the actual class’s published rule to calculate the real adjustment rather than multiplying the calculator’s cheapest monthly row by the observed one-month lifetime.
Build an object-level inventory
Collect object count, size distribution, expected retention, and access needs. An average size can hide a large population of tiny files below a minimum even when a few large objects dominate total GB.
Compare options for that small-object population separately. Consolidating files may reduce per-object effects, but can change retrieval granularity and application processing. Preserve those tradeoffs instead of treating consolidation as a universal saving.
The tool compares S3 Standard, Standard-IA, and Glacier Instant Retrieval storage-only rates in US East. It excludes retrieval, requests, transitions, minimum rules, transfer, and other features. Check current official terms for the exact selected class before acting.
Frequently asked questions
Can I use total logical GB without checking object sizes? Only when that quantity appropriately represents billable storage for the selected class.
Does deleting data stop every future charge immediately? Minimum-duration rules can leave an early-deletion charge; verify the chosen class’s terms.
Calculate your scenario
Use the s3 storage class comparison 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.