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.