Amazon DynamoDB · Rate Limits
Amazon Dynamodb Rate Limits
Amazon Dynamodb Rate Limits is the machine-readable rate-limit profile for Amazon DynamoDB on the APIs.io network, in the API Commons Rate Limits shape.
It captures 8 rate-limit definitions, measuring request_units_per_second, capacity_units_per_second, update_table_decreases, tables, and concurrent_readers.
Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 400.
The profile also includes response codes documented for throttled, quotaExceeded, serviceUnavailable, and note.
Tagged areas include Database, Document Store, Key-Value Store, NoSQL, and Serverless.
8 Limits
Exhausted: HTTP 400
Quota: 400
limitremainingresetretryAfter
Transcribed from the provider's documentation on 2026-09-18 — docs.aws.amazon.com/amazondynamodb/latest/developerguide/....
View Source
DatabaseDocument StoreKey-Value StoreNoSQLServerless
Limits
Per-table throughput, on-demand mode per-table
40000
40,000 read request units and 40,000 write request units per second per table (initial default, raisable via Service Quotas).
Per-table throughput, provisioned mode per-table
40000
40,000 RCU and 40,000 WCU per second for any table or any of its global secondary indexes.
Per-account provisioned throughput per-account-per-region
80000
80,000 RCU and 80,000 WCU per second summed across every table and GSI in a Region. Applies to provisioned mode only; on-demand tables carry no account-level throughput quota.
Provisioned capacity decreases per table per day per-table
27
4 decreases available at the start of each UTC day, 1 more per hour up to a ceiling of 4 available at once, totalling 27 across a full day. This is a control-plane rate limit an agent can hit while tuning capacity, and it is enforced per table and per GSI independently.
Tables per account per Region per-account-per-region
2500
Raisable to 10,000 through the account team; beyond that AWS recommends multiple accounts.
Simultaneous readers per DynamoDB Streams shard per-shard
2
Up to two simultaneous processes per shard for single-Region tables; AWS recommends one for global tables. Exceeding it throttles GetRecords.
Active reserved capacity per account per-account
1000000
Backfilled data for new global-table replicas per-account-per-region
10
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.