S3 SlowDown: Please reduce your request rate (503)
S3 is throttling requests to a prefix because the request rate is above what it can currently serve.
Please reduce your request rate503 Slow Down Meaning
S3 scales per prefix (about 3,500 writes and 5,500 reads per second each) and needs time to scale up. Bursts against one prefix, or many small requests (lists, HEADs) trigger 503 SlowDown. SDKs retry automatically but can exhaust retries.
Common causes
- Bursty traffic to a single prefix
- Many tiny objects/requests (per-file uploads, frequent LIST)
- Retries without backoff amplifying load
- Lifecycle/versioning delete storms
⚡ Quick fix
- Spread keys across prefixes
- Use exponential backoff (adaptive retry mode)
- Batch work (fewer, larger objects; S3 Batch Operations)
Detailed fix by platform
Python
- python
from botocore.config import Config s3 = boto3.client("s3", config=Config(retries={"max_attempts": 10, "mode": "adaptive"}))
How to diagnose
- Prefix — Are all keys under one prefix?
- Rate — CloudWatch request metrics
- Retries — SDK retry mode
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in AWS
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 12 Oct 2026