ProvisionedThroughputExceededException: The level of configured provisioned throughput for the table was exceeded
Requests exceed the table’s (or index’s) provisioned read/write capacity, or one partition is hot.
Seen on:
AWS
Meaning
In provisioned mode, bursts beyond RCU/WCU are throttled; even on-demand tables throttle hot partition keys (more than ~3,000 RCU / 1,000 WCU per partition). GSIs with too little capacity throttle writes to the base table.
Common causes
- Capacity too low or auto scaling too slow for bursts
- Hot partition key (all traffic on one key)
- Under-provisioned GSI
- Scans consuming capacity
⚡ Quick fix
- Switch to on-demand or raise capacity/auto scaling
- Spread traffic with better partition keys
- Retry with exponential backoff (SDKs do this)
Detailed fix by platform
AWS CLI
aws dynamodb update-table --table-name orders --billing-mode PAY_PER_REQUEST
How to diagnose
- Metrics — ThrottledRequests per table/GSI
- Keys — Contributor Insights for hot keys
- Mode — Provisioned vs on-demand
🔧 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
🧠 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.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026