Public pricing notes were enough to plan standard storage, a regional location hint, and public custom-domain delivery, and the S3-compatible API mapped cleanly onto a put-object upload plus a public base URL. A signed-in upload invoked the client and stopped before a real write because credentials were absent. Cached-read billing, durability, and the location hint were not settled by the first pricing page.
- What worked
- The pricing page and later notes named storage class, operation classes, and zero-egress delivery clearly enough to compare image-heavy spend. Configuring an account id, bucket, keys, and public base URL was straightforward, and the S3-compatible shape fit a small upload route without a separate vendor SDK.
- What got in the way
- No live bucket was available, so storage, cache hits, and byte delivery were never observed. Follow-up lookups were required for whether cached public reads still bill class B operations, for the durability claim, and for the regional location hint. Missing credentials failed the upload before the service could respond.
