DynamoDB Is Throttling but Capacity Looks Idle. Crank It Up?
DynamoDB throttles some requests while table capacity looks underused. A teammate wants to raise capacity or flip to on-demand. Defend the real cause.
Answer key reviewed by Branko Petric
Read first: AWS Databases: RDS and DynamoDB
Your decision
DynamoDB is returning throttling errors on certain requests, yet the table-level consumed capacity is far below what is provisioned. A teammate says just raise the capacity or switch to on-demand. What is really happening, and what do you do?
The situation
A subset of requests to a DynamoDB table return throttling errors during busy periods. When you open the table metrics, the consumed capacity sits well under the provisioned amount, so on paper the table is barely working.
Context
The table partitions on a key with only a handful of distinct values, and one of those values gets the overwhelming majority of traffic. The team provisions capacity generously. A teammate sees the throttling next to low average utilization and wants to either double the provisioned capacity or switch the table to on-demand to make it scale on its own.
Related challenges
- Lambda Is Exhausting Your RDS Connections. Raise the Limit?
Under load, Lambda functions fail with too many connections to RDS. A teammate wants to bump max_connections. Defend the real fix.
- The t3 Instance Got Slow. Just Size It Up?
An app on a t3 instance crawls under steady load and a teammate wants a bigger instance. Defend what is actually throttling it.
- Your S3 Website Returns 403. Make the Bucket Public?
Objects in S3 return 403 and a teammate wants to turn off Block Public Access to fix it fast. Defend the right way to grant access.
- Access Keys Are Hardcoded on the EC2 Box. Just Rotate Them?
An app on EC2 authenticates to AWS with long-lived IAM user keys in a config file. One leaked. Defend the real fix.