Read and write load is uneven across partition keys in a DynamoDB table. Investigate periods with no throttling as well.
Continuously identify the top contributing keys rather than only the table-wide totals.
Which feature and mode are most appropriate?
Enable Contributor Insights in Accessed and throttled keys mode to investigate top contributors.
Detailed explanation
It lacks Most Accessed Items and cannot rank unthrottled activity.
It lacks Most Accessed Items and cannot rank unthrottled activity.
These totals do not identify the contributing partition keys.
These totals do not identify the contributing partition keys.
Management auditing does not rank item traffic by key.
Management auditing does not rank item traffic by key.
This provides Most Accessed Items as well as throttled-key analysis.
This provides Most Accessed Items as well as throttled-key analysis.
Check official documentation
Compare the following points with the official documentation.
Read the mode-specific graphs and Most accessed items sections.
Official references
What to confirm
Accessed and throttled keys provides Most Accessed Items; its weighted traffic measure differs from raw request count.
Key points
- Contributor Insights
- DynamoDB
- Hot partition
Notes
- Environment: AWS SOA-C03 exam guide and the linked AWS documentation
- Reviewed against the linked AWS documentation on 2026-10-03.
Foundation review
Select the mode and resource
Accessed and throttled keys provides accessed and throttled graphs; Throttled keys provides only throttled graphs. Enable analysis on the relevant table or global secondary index.
Read the contributor measure
Most Accessed Items uses ConsumedThroughputUnits, a weighted read/write measure, rather than a raw API-call count. With sort keys, distinguish partition-key graphs from partition-and-sort-key graphs.