ToolScore

AWS S3 (Standard)

Amazon Web Services · cloud storage · reviewed by Stan K. · Source: data snapshot · data as of 2026-11-12

The egress tax incumbent: $0.09/GB out makes egress ~94% of the bill — the same workload that costs $1.35 on R2 costs $38.30 here.

#12 of 12 in Cloud Storage

Get AWS S3 (Standard)
Real price
$38.3/mo
usage
Free tier
No
Storage $0.023/GB (us-east-1); regional prices vary (US-West page example: $0.0265/GB). Egress $0.09/GB with 1
Limits
2.5/10
$0.023/GB us-east-1 · egress $0.09/GB (100GB/mo free) · workload $38.30 — egress ~94% of the bill
Verdict
NICHE
No storage floors or minimums — but the free egress allowance is 100GB/mo aggregated across all AWS services a

ToolScore breakdown — why 35/100

Price / Value
1.0
Token & Rate Limits
2.5
Speed / Latency
3.5
Privacy & Retention
5.0
BYOK (Own API Key)
6.5
Output Quality
3.0
Stability
5.0
Ease of Setup
2.5
Billing Transparency
2.0
Support & Community
5.0

10 criteria × 10 points. Low pillars are visible on purpose — that's the point of a score you can audit. Methodology →

What it does well

  • ▸100GB/month free egress aggregated across all AWS services and regions (excl. China and GovCloud)
  • ▸CloudFront fronting: first 1TB/mo of CDN egress free, then $0.085/GB instead of $0.09 direct — it bends the curve
  • ▸The ecosystem default — the hub's "when paid wins" case: S3 when you are already married to the AWS ecosystem
  • ▸DELETE operations are free; GETs meter at $0.0004/1K — the op bill is at least explicit

Where it costs you

  • ▸Egress is ~94% of this bill: 400 billable GB × $0.09 = $36.00 of the $38.30
  • ▸$0.023/GB holds for us-east-1 only — regional prices vary (US-West page example: $0.0265/GB)
  • ▸At 2TB stored + 8TB out, S3 lands at ~$759/mo where Cloudflare R2 lands at $30/mo
  • ▸The pricing page renders dynamically and shows US examples — regional rates need checking per deployment

Hidden traps — the stuff the pricing page doesn't say

high riskEgress is ~94% of the bill

For our 100GB + 500GB workload, storage is $2.30 and billable egress is $36.00 — 400 billable GB × $0.09 after the 100GB free allowance. The line item you shopped for (storage) is 6% of the line item you didn't (egress).

medium risk$0.023/GB is us-east-1, not a promise

The headline rate holds for us-east-1 only — regional prices vary, and the US-West page example is $0.0265/GB. The page renders dynamically, so treat every quoted rate as an example until checked for your region.

medium riskCloudFront bends the curve; it never flattens it

The S3 workaround is CloudFront: the first 1TB/mo of CDN egress is free, then $0.085/GB instead of $0.09 direct. That is a discount on the tax, not its removal — at scale the egress bill still dominates, ~$759/mo vs R2's $30/mo at 2TB + 8TB.

Try AWS S3 (Standard)

Know the limits before you pay: read the traps above, then decide with eyes open.

Visit official site

Affiliate link where available — never affects the score.

What the advertised price hides
Storage $0.023/GB (us-east-1); regional prices vary (US-West page example: $0.0265/GB). Egress $0.09/GB with 100GB/mo free account-wide. Our workload: 100 × $0.023 = $2.30 + (500 − 100 free) × $0.09 = $36.00 → $38.30 — egress is ~94% of the bill. Operations: PUT $0.005/1K, GET $0.0004/1K, DELETE free. CloudFront fronting: first 1TB/mo of CDN egress free, then $0.085/GB instead of $0.09 direct. AWS figures come from the US examples on a page that renders dynamically — treat $0.023/GB as the us-east-1 rate, not a universal one.
Sources & freshness

Data as of 2026-11-12. Prices and limits change monthly — report anything stale. How we verify: methodology.

Closest alternatives

AWS S3 (Standard) review

In-depth analysis · last updated 2026-11-12

The egress tax, itemized

AWS S3 Standard is the incumbent every other row in this hub is priced against — and on our fixed workload (100GB stored, 500GB out) it lands at $38.30: 100 × $0.023 = $2.30 of storage plus (500 − 100 free) × $0.09 = $36.00 of egress. Egress is ~94% of the bill. The same bytes cost ≈$1.35 on Cloudflare R2 — a 28× gap that the hub's "$0.015/GB store vs $0.006/GB store" framing makes concrete: storage rates are the small half of the bill.

It scales badly in exactly one direction

The gap widens with traffic. At 2TB stored + 8TB egress, S3 lands at ~$759/mo while R2 lands at $30/mo. The official workaround, CloudFront, gives the first 1TB/mo of CDN egress free and then $0.085/GB instead of $0.09 direct — it bends the curve; it never flattens it. The free egress allowance (100GB/mo account-wide, aggregated across all AWS services and regions, excl. China and GovCloud) covers a fifth of our workload before the $0.09 meter starts.

The regional asterisk

The quoted $0.023/GB is the us-east-1 rate from the US examples on a page that renders dynamically; the US-West example on the same page is $0.0265/GB. Every rate in the S3 row is an example until verified for your region — a transparency problem unique to the incumbent, whose pricing page is the largest and least quotable in the table.

How the pillars land

Price/Value 1: 28× the value pick on identical bytes — this pillar alone explains the total. Pricing transparency 2: dynamic page, regional variance, and the dominant cost (egress) living one click away from the storage headline. Real limits 2.5: no floors or minimums — the punishment is priced, not capped — and the free egress allowance covers a fifth of the workload. Ease 2.5: budgeting S3 means modeling storage, tiered egress, per-call operations and CloudFront as one bill. Transfer speed 3.5 and Feature set 3: the direct path is the expensive path, and the features that fix the bill (CloudFront) cost extra. S3/API interop 6.5: the ecosystem is the one genuine strength — "married to the AWS ecosystem" is the hub's only buying case. Track record 5: the industry's reference storage, scored at neutral because a track record doesn't discount the egress bill on a new deployment. Privacy 5 and Support & docs 5, neutral: nothing verifiable in this snapshot.

Verdict — NICHE, 35/100

S3 wins exactly one case in the hub's playbook: you are already married to the AWS ecosystem. Then front it with CloudFront and budget the egress tier — and for anything that leaves the building regularly, run the numbers against R2 or B2 first.

From the insights