Summary

  • The S3 price page prints five distinct numbers that decide one object's bill: a 128 KB minimum billable object size, minimum storage durations of 30, 90 and 180 days, and a 40 KB per-object metadata addition. Together they reach five storage classes and none of S3 Standard.
  • The billed unit is a GB-month, defined as total GB-hours divided by "the number of hours in that month" — a divisor no reviewed page fixes, and one that returns 10.7 percent more GB-months from a 28-day month than from a 31-day one for identical GB-hours.
  • Three surfaces report stored bytes before an invoice, and by their own printed definitions they measure three populations: the inventory listing excludes object metadata, delete markers and incomplete multipart parts, the CloudWatch bucket metric includes all three, and one reports base 2 where the other converts at base 10.

Stored, then billed as something else

The price page states the size rule twice — once for the infrequent-access classes, once for instant retrieval — and both sentences keep storage and charge in separate clauses:

S3 Standard-IA and S3 One Zone-IA storage have a minimum billable object size of 128 KB. Smaller objects may be stored but will be charged for 128 KB of storage at the appropriate storage class rate.

S3 Glacier Instant Retrieval has a minimum billable object size of 128 KB. Smaller objects may be stored but will be charged for 128 KB of storage at the appropriate storage class rate.

Both are printed with the pricing tables (S3 pricing). The User Guide says it to the operator's face — "If an object is less than 128 KB, Amazon S3 charges you for 128 KB" — and recommends these classes for "objects larger than 128 KB that you plan to store for at least 30 days" (storage classes).

Read the verbs and the object of the sentence. Nothing is refused: may be stored grants the write. What is synthesized is a quantity, 128 KB of "storage" for an object that occupies less. The floor does not act on the object. It acts on the multiplication that produces a charge.

Five numbers, three instruments, five classes — and one class carrying none

128 KB is a quantity of bytes. 30, 90 and 180 are durations. 40 KB is a quantity of bytes again, but it is not a floor underneath the object: the page calls it additional metadata for each archived object, and the lifecycle page describes it as storage added to each object. So five numbers in three instruments — a quantity substituted for the object's size, a period substituted for the time actually held, and a quantity added to the object.

The class list matters more than the count. The size rule names three classes. The durations name five. The addition names two. Together the five numbers reach S3 Standard-IA, S3 One Zone-IA, S3 Glacier Instant Retrieval, S3 Glacier Flexible Retrieval and S3 Glacier Deep Archive — five classes, and not S3 Standard.

S3 Standard appears in these sentences only as a rate: eight of the forty kilobytes are charged at S3 Standard rates. The floors are therefore not a condition of storing an object in Amazon S3. They are a condition of storing it somewhere other than the default class. The price of leaving is a different quantity from the price of the space.

The page that prices the exit names fewer classes

Three AWS documents state the durations. They do not state the same set.

The expiration page, which is where an operator goes to learn what a lifecycle rule will cost, names four classes and prints three durations:

If you create an S3 Lifecycle expiration rule that causes objects that have been in S3 Standard-IA or S3 One Zone-IA storage for less than 30 days to expire, you are charged for 30 days. If you create a Lifecycle expiration rule that causes objects that have been in S3 Glacier Flexible Retrieval storage for less than 90 days to expire, you are charged for 90 days. If you create a Lifecycle expiration rule that causes objects that have been in S3 Glacier Deep Archive storage for less than 180 days to expire, you are charged for 180 days.

S3 Glacier Instant Retrieval is absent from that passage (expiring objects), although the price page gives that class a 90-day duration. This is an omission inside a listed document, not a competing value: no reviewed page says instant retrieval carries no minimum duration. The transition page narrows the list again, to two classes — "The minimal storage duration period is 90 days for the S3 Glacier Flexible Retrieval storage class and 180 days for S3 Glacier Deep Archive" (transitioning objects).

Five classes on the page that prints the rates, four on the page that prices an expiration, two on the page that prices a transition. The closer a document sits to the action that triggers a minimum-duration charge, the fewer classes it covers.

Forty kilobytes that are rented, in two classes at once

The archive classes take no size floor. They take an addition, priced twice:

For each object that is stored in the S3 Glacier Flexible Retrieval and S3 Glacier Deep Archive storage classes, AWS charges for 40 KB of additional metadata for each archived object, with 8 KB charged at S3 Standard rates and 32 KB charged at S3 Glacier Flexible Retrieval or S3 Deep Archive rates.

The transition page splits the same 40 KB into its parts — 8 KB for the object's name and other metadata, 32 KB for index and related metadata — and writes the sentence that tells you what kind of charge this is: "You are charged S3 Standard rates for this additional storage" (transitioning objects). Storage, billed at storage rates, sitting beside an object that lives in the archive class. One fifth of it is denominated in S3 Standard, a class the object is not in.

The divisor is a calendar

Storage is billed in GB-months, and S3's usage-report documentation defines the unit: "A GB-Month is derived by taking total GB-hours, aggregating them over the course of a month, and dividing by the number of hours in that month" (understanding your usage report). TimedStorage-ByteHrs is reported in GB-month units at daily granularity; an archived version of the same page says the volume billed each month is based on the average storage used throughout the month.

The divisor is not a rate. It is the length of a month, and no reviewed page states it — not 720 hours, not 730, not 744. The reader supplies it from a calendar.

128 KB, defined in a blog post

The price page defines its large units with real care: "1 GB is 2 30 bytes… also known as a gibibyte (GiB), defined by the International Electrotechnical Commission (IEC). Similarly, 1 TB is 2 40 bytes" (S3 pricing). It never defines KB. The conversion appears in an AWS Storage Blog post dated 12 September 2023 — "Therefore, 128 KB is 131,072 bytes" (archiving cold objects) — an article about cost optimisation, not the pricing document and not the User Guide.

Three counters, three populations, two bases

An operator who wants to check the bill before it lands has three surfaces. Each is accurate for the population its own definition names, and the definitions do not name the same population.

The inventory listing reports per object daily or weekly, weekly reports on Sundays in UTC, the first report within 48 hours. Its size field is "The object size in bytes, not including the size of incomplete multipart uploads, object metadata, and delete markers" — and Size is an optional field that has to be selected in the configuration (S3 Inventory).

The CloudWatch bucket metric is defined the other way round: "calculated by summing the size of all objects and metadata (such as bucket names) in the bucket (both current and noncurrent objects), including the size of all parts for all incomplete multipart uploads", while NumberOfObjects counts delete markers and multipart parts too (metrics and dimensions). These metrics are "reported once per day", free to all customers, and delivered on a best-effort basis, with completeness and timeliness not guaranteed and a data point possibly delayed or never delivered (CloudWatch monitoring).

And the bases differ: "The Amazon S3 console and S3 Storage Lens use base 2 conversion (/1024) to report storage metrics. CloudWatch uses base 10 conversion (/1000) by default" (AWS knowledge centre).

One counter excludes what the other includes, one may not arrive, and one divides by 1,000 where the billed unit is built on 1,024.

My arithmetic, clearly mine

None of the following is printed as a figure by any of the ten documents.

128 KB in base 2 is 131,072 bytes; read as 128,000 it is 2.4 percent smaller. A 100-byte object in Standard-IA is therefore billed at 1,310.72 times its stored size, and a one-byte object at 131,072 times its own.

A million one-byte objects hold 1,000,000 bytes between them and are billed as 131,072,000,000 bytes, which is 122.07 GB. The billable size of that estate is not its stored size; it is its stored size times 131,072, and the multiplier comes from a floor.

40 KB in base 2 is 40,960 bytes, exactly five sixteenths of 131,072. On an archived one-byte object, 8 KB — one fifth of the addition — is priced at S3 Standard rates.

An object deleted from Standard-IA on its first day is charged for 30 days: 30 times the duration it was held.

On the month divisor, 28 days is 672 hours and 31 days is 744, a difference of 72 hours, or 10.7 percent of 672. The same GB-hours divided by 672 return 10.7 percent more GB-months than divided by 744.

What the ten documents do not state

No reviewed page defines the KB used in the 128 KB and 40 KB figures. None states how many hours the billing division uses, or which calendar month it divides by. None carries a worked example combining the minimum billable size, the minimum duration and the metadata addition in one calculation for one object, and none shows a single object billed under two classes side by side. None states how the reporting surfaces reconcile to the billed quantity, which by their own definitions they cannot, since the inventory excludes what the bucket metric includes.

None states whether the 40 KB addition is charged once or for the object's whole residency, beyond describing it as storage added to each object and billed at storage rates. And the expiration page does not name S3 Glacier Instant Retrieval at all.

Reading limits

The price page was read as retrieved page text; its pricing tables load dynamically and their values were not inspected, so no dollar rate and no per-class rate appears here. The CloudWatch metric table was read as an excerpt of the daily storage metrics table. The lifecycle pages were read as search-retrieved page text rather than fully rendered pages. One AWS Storage Blog address returned HTTP 404 and contributed nothing.

The five numbers are printed in AWS's own words on pages anyone can open. What is not printed is the arithmetic that joins them — and for an estate built out of small objects, that arithmetic is the bill. Amazon Web Services, Inc. is tracked in the BTW directory (Amazon Web Services, Inc.).