Pain Point

Request Pricing Models

The cost structures imposed by S3-compatible storage providers where each API call (GET, PUT, LIST, HEAD, DELETE) incurs a per-request charge independent of data volume, creating a cost dimension that scales with operation count rather than storage size.

4 connections 3 resources

Summary

What it is

Where it fits

Request pricing is the hidden cost multiplier in S3-based architectures. While storage costs per GB get the attention, request costs dominate for workloads with many small files, frequent metadata operations, or high-concurrency query patterns. Understanding request pricing is essential for cost-effective lakehouse design.

Misconceptions / Traps

PUT requests cost 5-10x more than GET requests on most providers. Write-heavy workloads (streaming ingestion, frequent compaction) are disproportionately expensive.
LIST requests are the most expensive per-call and the most common source of cost surprises. Recursive listing of a prefix with millions of objects generates thousands of LIST calls.
S3-compatible providers (R2, B2, MinIO) have different pricing structures. Cloudflare R2 has zero egress fees but still charges for operations. Cost comparisons must include request costs, not just storage and egress.

Key Connections

scoped_to S3, Object Storage — the per-request cost model of S3 APIs
amplifies Small Files Problem — more files means more requests means higher cost
amplifies Request Amplification — architectural patterns that multiply requests also multiply cost
constrains Encryption / KMS — SSE-KMS adds KMS API calls to every S3 request

Definition

What it is

The cost structure where S3 charges per API request (PUT, GET, LIST, DELETE) in addition to storage and egress, making the number of operations as important as the volume of data stored.

Recent developments

Latest signals

S3 Standard 2026 request pricing: PUT/COPY/POST/LIST $0.005 per 1K; GET $0.0004 per 1K. AWS request pricing unchanged for 2026 — PUT operations are ~12.5× the cost of GETs, which makes write-heavy workloads structurally more expensive than read-heavy at the request layer. Per AWS S3 Pricing and go-cloud — Amazon S3 Pricing Explained 2026.
Express One Zone: ~50% cheaper per request than Standard. Express One Zone PUTs ~$0.0025/1K + GETs ~$0.0002/1K — half the Standard rate. Combined with single-digit-ms latency, it's now the production default for high-request-rate workloads regardless of latency need. Per go-cloud — Amazon S3 Pricing Explained 2026.
Request volume reduction often delivers faster savings than storage-class transitions. 2026 cost-optimization framing: chase request volume first (small files, lifecycle transitions, LIST patterns) — request-pricing optimization frequently outpaces storage-class optimization for fastest cost wins. Per Cloud Burn — Amazon S3 Pricing: 23x Cost Gap Between Storage Classes and Hyperglance — AWS S3 Pricing Guide 2026.
S3 Gateway VPC Endpoints free — eliminates $0.045/GB NAT Gateway processing. Free VPC Gateway Endpoint for S3 traffic eliminates NAT Gateway processing fees ($0.045/GB) — at 1 TB/month, that's $45/month savings. Adjacent to request-pricing but stacks meaningfully. Per Sedai — AWS S3 Pricing Explained 2026.
S3 Bucket Keys eliminate up to 99% of KMS requests for SSE-KMS workloads. Adjacent request-pricing optimization: encrypted-at-rest workloads were previously paying per-KMS-request + per-S3-request — Bucket Keys consolidate the KMS side, cutting that line up to 99%. Per Sedai — AWS S3 Pricing Explained 2026.
DELETE + CANCEL are always free — but versioned-bucket DELETE creates version markers. Often-missed: DELETE is free as a request, but on versioned buckets it creates delete markers (still billable storage). Lifecycle policies need NoncurrentVersionExpiration rules to actually reclaim space. Per Opsolute — The Practical Amazon S3 Cost Optimization Playbook.