Skip to content
Amazon S3
AWS track / Storage
Entry overview
Sub-page 5 of 8
Scaling & capacity limits

Staying Under the Per-Prefix Request-Rate Ceiling Before Getting Throttled

Decision drivers
  • Peak expected requests/second, and whether that load concentrates on one prefix or spreads naturally
  • Whether traffic is steady-state or bursty/spiky
  • Existing retry/backoff behavior in the client for 503 SlowDown
  • Number of prefixes the current key scheme actually produces

S3 supports at least 3,500 write (PUT/COPY/POST/DELETE) and 5,500 read (GET/HEAD) requests per second, per partitioned prefix — with no limit on the number of prefixes a bucket can have. This makes throughput a design choice, not a fixed ceiling, but only if the key scheme (page 1) actually spreads load across prefixes.

Gated · a free account unlocks the full catalog
Sign in to keep reading

This page is part of the AWS track's gated content. Sign in — free — to keep reading. A free account unlocks the full catalog.

Sign in