AWS amazondynamodb documentation change
Summary
Added guidance on handling key-range throttling caused by unbounded sequential access during Scan operations
Security assessment
Change provides performance optimization advice for distributed read/write operations. No security vulnerabilities or security features are mentioned.
Diff
diff --git a/amazondynamodb/latest/developerguide/throttling-diagnosing-workflow.md b/amazondynamodb/latest/developerguide/throttling-diagnosing-workflow.md index a7d089dbf..e0765f83f 100644 --- a//amazondynamodb/latest/developerguide/throttling-diagnosing-workflow.md +++ b//amazondynamodb/latest/developerguide/throttling-diagnosing-workflow.md @@ -179,0 +180,2 @@ You can choose the _Throttled keys_ mode to focus exclusively on the most thrott + 3. If no individual keys show disproportionately high access or throttling rates, key-range throttling might be caused by _unbounded sequential access_ across a range of keys rather than a single hot key. When you run continued `Scan` operations, rate-limit the read traffic to stay below the per-partition maximum of 3,000 read units per second for a key range. To achieve higher overall read throughput, use parallel (segmented) scans to distribute read traffic more uniformly across partitions. Similarly, writing items in the same key order in which they are returned by a `Scan` concentrates writes on one key range at a time and can cause key-range throttling when the write rate to that range exceeds 1,000 write units per second. Rate-limit writes to a single key range to stay below that limit. +