DynamoDB Local
ff89bd48ff32 53 recorded runs
How to run it
Every way DynamoDB Local is distributed, each linking to the project's own documentation for it. These are the project's claims, not the suite's measurements.
Needs: JRE 17+ (bundled in the Docker route)
Per-region divergence
The headline is 2 regions, measured against 2 of 33 observed regions, and scored in eu-south-2. Real DynamoDB doesn't behave identically in every region, so a target can match some regions more closely than others. Each figure below is divergence in those regions, best first. eu-west-2 is marked as the historical baseline, and a region that couldn't be resolved this sweep is flagged rather than counted as a disagreement.
Feature support
Measured across the suite's tests for each feature. Compare with other emulators.
Core DynamoDB
- Vector search
- DynamoDB Local Vector search: not supported (52 skip)
- GSI
- DynamoDB Local GSI: partially supported (130 pass, 46 fail)
- LSI
- DynamoDB Local LSI: partially supported (115 pass, 43 fail)
- PartiQL
- DynamoDB Local PartiQL: partially supported (163 pass, 45 fail, 2 skip)
- Transactions
- DynamoDB Local Transactions: partially supported (95 pass, 32 fail)
- Streams
- DynamoDB Local Streams: supported (18 pass)
- TTL
- DynamoDB Local TTL: supported (7 pass)
- Legacy params
- DynamoDB Local Legacy params: partially supported (48 pass, 1 fail)
Other AWS services
- Backups / PITR
- DynamoDB Local Backups / PITR: not supported (5 skip)
- Export / import
- DynamoDB Local Export / import: not supported (2 skip)
- Kinesis
- DynamoDB Local Kinesis: not supported (1 skip)
- Resource policies
- DynamoDB Local Resource policies: not supported (2 skip)
- Contributor Insights
- DynamoDB Local Contributor Insights: not supported (2 skip)
- Account API
- DynamoDB Local Account API: partially supported (1 pass, 1 skip)
Fully supports
Operation areas this target implements completely - every test passes, nothing skipped. Areas it only partly gets wrong are in “Where it falls short” below; the ones it only partly attempts are in “What it doesn’t attempt”.
- batchGetItem tier 1
- deleteItem tier 1
- deleteTable tier 1
- getItem tier 1
- listTables tier 1
- scan tier 1
- streams tier 2
- ttl tier 2
Divergence and coverage over time
Both are plotted because neither reads correctly alone. Divergence falls when a target stops attempting an operation it used to get wrong, so a fall in the first plot is only an improvement if the second one holds.
Divergence
Coverage
By operation
Every operation this target implements, with how much of it diverges and how much of it it covers, on the same two axes as the figures above. The counts are fails over the operation's whole size. full, partial, failing, unsupported. The emulator directory lists support across targets.
Tier 1 - Core
- batchGetItem 0/15 0.0% 100.0% batchGetItem: supported, diverges on 0.0% of it, covers 100.0% (15 pass)
- batchWriteItem 3/18 16.7% 100.0% batchWriteItem: partially supported, diverges on 16.7% of it, covers 100.0% (15 pass, 3 fail)
- createTable 4/30 13.3% 100.0% createTable: partially supported, diverges on 13.3% of it, covers 100.0% (26 pass, 4 fail)
- deleteItem 0/13 0.0% 100.0% deleteItem: supported, diverges on 0.0% of it, covers 100.0% (13 pass)
- deleteTable 0/3 0.0% 100.0% deleteTable: supported, diverges on 0.0% of it, covers 100.0% (3 pass)
- describeTable 1/4 25.0% 100.0% describeTable: partially supported, diverges on 25.0% of it, covers 100.0% (3 pass, 1 fail)
- getItem 0/39 0.0% 100.0% getItem: supported, diverges on 0.0% of it, covers 100.0% (39 pass)
- listTables 0/5 0.0% 100.0% listTables: supported, diverges on 0.0% of it, covers 100.0% (5 pass)
- putItem 25/129 19.4% 100.0% putItem: partially supported, diverges on 19.4% of it, covers 100.0% (104 pass, 25 fail)
- query 2/95 2.1% 100.0% query: partially supported, diverges on 2.1% of it, covers 100.0% (93 pass, 2 fail)
- scan 0/60 0.0% 100.0% scan: supported, diverges on 0.0% of it, covers 100.0% (60 pass)
- updateItem 1/70 1.4% 100.0% updateItem: partially supported, diverges on 1.4% of it, covers 100.0% (69 pass, 1 fail)
- updateTable 1/15 6.7% 100.0% updateTable: partially supported, diverges on 6.7% of it, covers 100.0% (14 pass, 1 fail)
Tier 2 - Complete
- account 0/2 · 1 skip 0.0% 50.0% account: partially supported, diverges on 0.0% of it, covers 50.0% (1 pass, 1 skip)
- backups 0/5 · 5 skip n/a 0.0% backups: unsupported, implements none of it (5 skip)
- contributorInsights 0/2 · 2 skip n/a 0.0% contributorInsights: unsupported, implements none of it (2 skip)
- export 0/2 · 2 skip n/a 0.0% export: unsupported, implements none of it (2 skip)
- kinesis 0/1 · 1 skip n/a 0.0% kinesis: unsupported, implements none of it (1 skip)
- partiql 39/186 21.0% 100.0% partiql: partially supported, diverges on 21.0% of it, covers 100.0% (147 pass, 39 fail)
- resourcePolicy 0/2 · 2 skip n/a 0.0% resourcePolicy: unsupported, implements none of it (2 skip)
- streams 0/18 0.0% 100.0% streams: supported, diverges on 0.0% of it, covers 100.0% (18 pass)
- tags 0/8 · 8 skip n/a 0.0% tags: unsupported, implements none of it (8 skip)
- transactions 11/62 17.7% 100.0% transactions: partially supported, diverges on 17.7% of it, covers 100.0% (51 pass, 11 fail)
- ttl 0/7 0.0% 100.0% ttl: supported, diverges on 0.0% of it, covers 100.0% (7 pass)
- updateTable 3/14 21.4% 100.0% updateTable: partially supported, diverges on 21.4% of it, covers 100.0% (11 pass, 3 fail)
- vectorSearch 0/36 · 36 skip n/a 0.0% vectorSearch: unsupported, implements none of it (36 skip)
Tier 3 - Strict
- error-messages 70/185 · 16 skip 37.8% 91.4% error-messages: partially supported, diverges on 37.8% of it, covers 91.4% (99 pass, 70 fail, 16 skip)
- legacy-api 1/42 2.4% 100.0% legacy-api: partially supported, diverges on 2.4% of it, covers 100.0% (41 pass, 1 fail)
- limits 13/164 7.9% 100.0% limits: partially supported, diverges on 7.9% of it, covers 100.0% (151 pass, 13 fail)
- validation-ordering 24/34 70.6% 100.0% validation-ordering: partially supported, diverges on 70.6% of it, covers 100.0% (10 pass, 24 fail)
Where it falls short
Operations DynamoDB Local implements and answers differently from real DynamoDB, biggest gap first. This is what its divergence figure counts. Open one for the exact tests, or see the conformance suite.
-
error-messages Tier 3 70 diverging 16 not attempted
View these tests in the suite →- BatchGetItem - exact error messages empty RequestItems: full required-parameter error source:27
- BatchGetItem - exact error messages > 100 keys across all tables: interpolated full error source:47
- BatchGetItem - exact error messages non-existent table: full ResourceNotFoundException message source:70
- BatchWriteItem - exact error messages empty RequestItems: full required-parameter error source:44
- BatchWriteItem - exact error messages > 25 requests: anchored regex on the constraint phrase source:91
- BatchWriteItem - exact error messages non-existent table: full ResourceNotFoundException message source:134
- BatchWriteItem - exact error messages wrong-typed table key: full schema-mismatch message source:157
- BatchWriteItem - exact error messages non-scalar table key: full schema-mismatch message source:157
- CreateTable - exact error messages missing TableName: full required-parameter error source:32
- CreateTable - exact error messages short table name (2 chars): minimum length 3 error source:52
- CreateTable - exact error messages duplicate attribute in KeySchema source:75
- CreateTable - exact error messages more than 2 KeySchema elements source:112
- CreateTable - exact error messages invalid KeyType source:137
- CreateTable - exact error messages invalid AttributeType source:158
- CreateTable - exact error messages LSI without range key on base table source:191
- CreateTable - exact error messages duplicate index names source:233
- CreateTable - exact error messages PAY_PER_REQUEST with ProvisionedThroughput: full conflict message source:252
- CreateTable - exact error messages GSI INCLUDE projection without NonKeyAttributes: full missing-attributes message source:284
- CreateTable - exact error messages LSI INCLUDE projection without NonKeyAttributes: full missing-attributes message source:323
- CreateTable - exact error messages StreamSpecification StreamEnabled:false with a StreamViewType: full conflict message source:347
- DeleteItem - exact error messages non-existent table: full ResourceNotFoundException message source:29
- DeleteItem - exact error messages malformed Key (missing range key on composite table): full schema-mismatch error source:47
- GetItem - exact error messages non-existent table: full ResourceNotFoundException message source:32
- GetItem - exact error messages malformed Key (missing range key on composite table): full schema-mismatch error source:50
- BatchWriteItem - index key error messages wrong-typed index key: full type-mismatch message source:54
- BatchWriteItem - index key error messages non-scalar index key: full type-mismatch message source:54
- BatchWriteItem - index key error messages empty-string index key: full secondary-index-key message source:54
- PartiQL index qualifier - exact error messages unprojected filter attribute on a GSI - exact message source:24
- PartiQL index qualifier - exact error messages unprojected filter attribute on an LSI - same wording, no Local prefix source:24
- PartiQL index qualifier - exact error messages a qualifier naming no index - exact message, with no name appended source:96
- PartiQL index qualifier - exact error messages a qualifier naming the table itself - same message source:102
- PartiQL index qualifier - exact error messages ConsistentRead against a GSI qualifier - exact message source:127
- PutItem - exact error messages missing table name: full validation error string source:37
- PutItem - exact error messages empty table name: minimum length 1 error source:59
- PutItem - exact error messages table name too long (256 chars): maximum length 255 error source:80
- PutItem - exact error messages table name with invalid chars: regex pattern error source:98
- PutItem - exact error messages empty string member in NS: numeric conversion error source:198
- Query - exact error messages missing hash key in KeyConditionExpression source:30
- Query - exact error messages non-key attribute in KeyConditionExpression source:49
- Query - exact error messages invalid Select value source:90
- Query - exact error messages Limit of 0 source:110
- Query - exact error messages malformed ExclusiveStartKey: short invalid-starting-key error source:190
- Query - exact error messages Select SPECIFIC_ATTRIBUTES without ProjectionExpression: full required-projection message source:214
- Scan - exact error messages Segment without TotalSegments: full required-parameter error source:31
- Scan - exact error messages Segment >= TotalSegments: full out-of-range error source:62
- Scan - exact error messages TotalSegments without Segment: full required-parameter error source:80
- Scan - exact error messages Limit of 0: full minimum-value error source:103
- Scan - exact error messages negative Segment: full minimum-value error source:127
- Scan - exact error messages non-existent table: full ResourceNotFoundException message source:146
- Scan - exact error messages Select SPECIFIC_ATTRIBUTES without ProjectionExpression: full required-projection message source:236
- TransactGetItems - exact error messages empty TransactItems: full minimum-length error source:31
- TransactGetItems - exact error messages > 100 gets: anchored regex on the constraint phrase source:64
- TransactGetItems - exact error messages non-existent table: full ResourceNotFoundException message source:88
- TransactGetItems - exact error messages missing key attribute: action-level ValidationError surfaces as TransactionCanceledException source:143
- TransactWriteItems - index key error messages Put wrong-typed index key: cancelled with full ValidationError reason source:63
- TransactWriteItems - index key error messages Put non-scalar index key: cancelled with full ValidationError reason source:54
- TransactWriteItems - index key error messages Update wrong-typed index key: cancelled with full ValidationError reason source:63
- TransactWriteItems - index key error messages Update non-scalar index key: cancelled with full ValidationError reason source:54
- TransactWriteItems - index key error messages Put empty-string index key: top-level ValidationException source:77
- TransactWriteItems - exact error messages empty TransactItems: full minimum-length error source:54
- TransactWriteItems - exact error messages > 100 actions: anchored regex on the constraint phrase source:91
- TransactWriteItems - exact error messages non-existent table: full ResourceNotFoundException message source:145
- TransactWriteItems - exact error messages Put wrong-typed table key: cancelled with full ValidationError reason source:281
- TransactWriteItems - exact error messages Put non-scalar table key: cancelled with full ValidationError reason source:272
- TransactWriteItems - exact error messages Update wrong-typed Key: cancelled with schema-mismatch reason source:281
- TransactWriteItems - exact error messages Update non-scalar Key: cancelled with schema-mismatch reason source:272
- TransactWriteItems - exact error messages Delete wrong-typed Key: cancelled with schema-mismatch reason source:281
- TransactWriteItems - exact error messages Delete non-scalar Key: cancelled with schema-mismatch reason source:272
- TransactWriteItems - exact error messages ConditionCheck wrong-typed Key: cancelled with schema-mismatch reason source:281
- TransactWriteItems - exact error messages ConditionCheck non-scalar Key: cancelled with schema-mismatch reason source:272
- SearchVectors - exact error messages TopK above the maximum
- SearchVectors - exact error messages missing SearchConditionExpression against a HASH-schema index
- SearchVectors - exact error messages non-equality comparator on the HASH element
- SearchVectors - exact error messages non-equality comparator on an INLINE_FILTER element
- SearchVectors - exact error messages query vector dimension mismatch
- SearchVectors - exact error messages condition attribute outside the SearchSchema
- SearchVectors - exact error messages L-wrapped search vector
- CreateTable vector indexes - exact error messages vector index on a provisioned table
- CreateTable vector indexes - exact error messages SearchSchema attribute missing from AttributeDefinitions
- CreateTable vector indexes - exact error messages Dimensions above the 4096 maximum
- CreateTable vector indexes - exact error messages more vector indexes than the per-table limit
- CreateTable vector indexes - exact error messages two indexes on one attribute with different Dimensions
- PutItem vector writes - exact error messages vector with the wrong dimension count
- PutItem vector writes - exact error messages vector element that is not a number, naming the element
- PutItem vector writes - exact error messages vector attribute that is not a list
- PutItem vector writes - exact error messages empty string in the SearchSchema HASH attribute
-
partiql Tier 2 39 diverging
View these tests in the suite →- BatchExecuteStatement - PartiQL surfaces a malformed member statement as a per-statement ValidationError without failing the batch source:299
- BatchExecuteStatement - PartiQL ConsistentRead is honoured per member charges a small eventually-consistent read half a unit source:354
- BatchExecuteStatement - PartiQL a batch SELECT must name the table primary key rejects a member that filters on a non-key attribute source:396
- BatchExecuteStatement - PartiQL a batch SELECT must name the table primary key rejects an index-qualified member naming the index key source:404
- BatchExecuteStatement - PartiQL a batch SELECT must name the table primary key rejects one naming both the table primary key and the index key source:413
- ExecuteStatement - PartiQL rejects INSERT on an existing item (INSERT is not upsert) source:160
- ExecuteStatement - PartiQL returns a populated ConsumedCapacity block when requested source:394
- ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED NEW * over a nested path returns only the changed leaf source:824
- ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED OLD * over a nested path returns only the changed leaf at its old value source:844
- ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED NEW * on a list index returns only the changed element source:941
- ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED OLD * on a list index returns only the prior element source:967
- ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED NEW * on a non-zero list index returns only the changed element source:999
- ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED OLD * on a non-zero list index returns the prior element source:1023
- ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED NEW * over multiple list indices returns a dense pack of the changed elements source:1045
- ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED OLD * over multiple list indices returns the prior elements densely source:1069
- ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED NEW * packs changed indices in ascending index order, not statement order source:1091
- ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED OLD * packs changed indices in ascending index order, not statement order source:1117
- ExecuteStatement - PartiQL UPDATE RETURNING MODIFIED NEW * appending at exactly the list length returns the appended element source:1182
- ExecuteStatement - PartiQL UPDATE REMOVE RETURNING MODIFIED OLD * on a list index returns the removed element at its old value source:1224
- ExecuteStatement - PartiQL UPDATE REMOVE RETURNING MODIFIED NEW * on a list index returns the shifted element, not an empty list source:1252
- ExecuteStatement - PartiQL UPDATE REMOVE RETURNING MODIFIED OLD * on the last list index returns the removed element source:1302
- ExecuteTransaction - PartiQL idempotent replay under the same ClientRequestToken does not double-apply source:189
- ExecuteStatement - index qualifier the reach-back splits by index kind an LSI serves an unprojected attribute from the base table source:230
- ExecuteStatement - index qualifier the reach-back splits by index kind a bounded reach-back walks fewer rows and is charged less source:276
- ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition rejects a keyed GSI read filtering on an unprojected attribute source:88
- ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition rejects the LSI mirror, so the rule is not about index kind source:88
- ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition accepts the same GSI filter unkeyed, matching nothing source:306
- ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition accepts the same LSI filter unkeyed, matching nothing source:315
- ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition rejects a keyed read with IS MISSING on an unprojected attribute source:88
- ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition rejects a keyed read with IS NOT MISSING on an unprojected attribute source:88
- ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition rejects a keyed read with begins_with on an unprojected attribute source:88
- ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition rejects a keyed read with a negated filter on an unprojected attribute source:88
- ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition matches every index row when the negated filter names an absent attribute source:374
- ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition counts IN on the index partition key as keyed source:88
- ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition accepts an unprojected filter inside an OR branch source:395
- ExecuteStatement - index qualifier the unprojected-filter rejection turns on the key condition counts BETWEEN on the index sort key as keyed source:88
- ExecuteStatement - index qualifier pagination across a qualified read rejects a token minted against one index and replayed against another source:88
- ExecuteStatement - index qualifier capacity lands on the index arm a keyed GSI read charges the index and a zero table arm source:510
- ExecuteStatement - index qualifier capacity lands on the index arm a keyed LSI read charges the index and a zero table arm source:517
-
putItem Tier 1 25 diverging
View these tests in the suite →- ReturnItemCollectionMetrics PutItem with SIZE returns ItemCollectionMetrics source:37
- ReturnItemCollectionMetrics DeleteItem with SIZE returns ItemCollectionMetrics source:65
- ReturnItemCollectionMetrics UpdateItem with SIZE returns ItemCollectionMetrics source:95
- PutItem - number format rejects "+e2" source:96
- PutItem - number format rejects "e2" source:96
- PutItem - number format rejects "+1+2" source:96
- PutItem - number format rejects "1+2" source:96
- PutItem - number format rejects "+1.2.3" source:96
- PutItem - number format rejects "1.2.3" source:96
- PutItem - number format rejects "++5" source:96
- PutItem - number format rejects "+-5" source:96
- PutItem - number format rejects "-+5" source:96
- PutItem - number format rejects "+" source:96
- PutItem - number format rejects "-" source:96
- PutItem - number format rejects "1e" source:96
- PutItem - number format rejects "1e+" source:96
- PutItem - number format rejects "." source:96
- PutItem - number format rejects "1.2e3.4" source:96
- PutItem - number format rejects "0x5" source:96
- PutItem - number format rejects "NaN" source:96
- PutItem - number format rejects "Infinity" source:96
- PutItem - number format rejects "1_000" source:96
- PutItem - number format rejects " 5" source:96
- PutItem - number format rejects "5 " source:96
- PutItem - number format rejects "1 5" source:96
-
validation-ordering Tier 3 24 diverging
View these tests in the suite →- Batch operations - validation ordering BatchWriteItem rejects empty RequestItems source:37
- Batch operations - validation ordering BatchGetItem rejects empty RequestItems source:53
- CreateTable - validation ordering empty TableName reports only tableName constraint source:23
- CreateTable - validation ordering invalid table name pattern reports only tableName source:41
- CreateTable - validation ordering reports invalid BillingMode and invalid KeySchema element together source:61
- CreateTable - validation ordering rejects a duplicate attribute in KeySchema source:105
- CreateTable - validation ordering rejects more than two KeySchema elements source:134
- CreateTable - validation ordering rejects an invalid BillingMode on its own source:153
- DeleteItem - validation ordering empty TableName reports only tableName constraint source:25
- DeleteItem - validation ordering reports invalid ReturnValues and invalid ReturnConsumedCapacity together source:44
- DeleteItem - validation ordering invalid table name pattern reports only tableName source:66
- PutItem - validation ordering empty TableName reports tableName constraint (stops early) source:27
- PutItem - validation ordering empty TableName with invalid ReturnValues reports only tableName source:54
- PutItem - validation ordering reports invalid ReturnConsumedCapacity, ReturnItemCollectionMetrics, and ReturnValues together source:74
- PutItem - validation ordering reports invalid table name pattern source:98
- Query - validation ordering reports invalid TableName pattern source:28
- Query - validation ordering reports invalid ReturnConsumedCapacity source:71
- Scan - validation ordering rejects Segment without TotalSegments source:24
- Scan - validation ordering rejects Segment >= TotalSegments source:43
- Scan - validation ordering rejects TotalSegments without Segment source:61
- Scan - validation ordering rejects a negative Segment source:88
- UpdateItem - validation ordering empty TableName reports only tableName constraint source:26
- UpdateItem - validation ordering rejects invalid ReturnValues (UpdateItem reports the first enum error) source:50
- UpdateItem - validation ordering invalid table name pattern reports only tableName source:72
-
limits Tier 3 13 diverging
View these tests in the suite →- Empty values - strings, binary, and sets empty string member in NS is rejected (not a number) source:224
- Item size limit by surface - UpdateItem does not charge for the key sits below 409,600 at a one-byte key, so the exclusion binds source:416
- Item size limit by surface - UpdateItem does not charge for the key buys back the same headroom from the key name as from the key value source:416
- Item size limit by surface - UpdateItem does not charge for the key buys back a sort key’s own bytes as well source:416
- Item size limit by surface - UpdateItem charges per action charges a second SET clause exactly 19 bytes source:416
- Item size limit by surface - UpdateItem charges per action charges a REMOVE alongside a SET exactly 2 bytes source:416
- Item size limit by surface - UpdateItem charges per action charges the clause, not the value it writes source:416
- Item size limit by surface - UpdateItem charges per action does not charge for an attribute the statement leaves alone source:416
- Item size limit by surface - UpdateItem charges per action charges the clause, not the attribute name or its alias source:416
- Item size limit by surface - UpdateItem through a document path charges a SET through a list index exactly one byte more source:690
- Item size limit by surface - a PartiQL UPDATE does not inherit the exclusion writes what UpdateItem refuses at the same key source:709
- Item size limit by surface - a transacted Update does not inherit the exclusion writes what UpdateItem refuses at the same key source:709
- Nesting depth - 32-level document limit rejects a 32-level ExpressionAttributeValue with ValidationException source:113
-
transactions Tier 2 11 diverging
View these tests in the suite →- TransactGetItems - ConsumedCapacity INDEXES breakdown includes the table read capacity units source:305
- TransactGetItems - projection matching nothing omits Item when the projection matches no attribute on a present item source:342
- TransactWriteItems - validation Put with a non-scalar table key cancels with a ValidationError reason source:761
- TransactWriteItems - validation Update with a non-scalar Key cancels with a ValidationError reason source:761
- TransactWriteItems - validation Delete with a non-scalar Key cancels with a ValidationError reason source:761
- TransactWriteItems - validation ConditionCheck with a non-scalar Key cancels with a ValidationError reason source:761
- TransactWriteItems - ConsumedCapacity charges 2 write capacity units per item source:1299
- TransactWriteItems - ConsumedCapacity: conditional, check, replay, cancel a standalone ConditionCheck action costs 2 write capacity units source:1388
- TransactWriteItems - ConsumedCapacity: conditional, check, replay, cancel reports write capacity on the first call and read capacity on a same-token replay source:1417
- TransactWriteItems - index key validation Put with a non-scalar index key cancels with a ValidationError reason source:60
- TransactWriteItems - index key validation Update setting a non-scalar index key cancels with a ValidationError reason source:60
-
createTable Tier 1 4 diverging
View these tests in the suite →- CreateTable - TableId returns a TableId on CreateTable that matches the subsequent DescribeTable source:146
- CreateTable - validation rejects PAY_PER_REQUEST with ProvisionedThroughput specified source:248
- CreateTable - configuration parameters TableClass STANDARD_INFREQUENT_ACCESS round-trips source:50
- CreateTable - configuration parameters SSESpecification with the AWS-managed key round-trips source:61
-
batchWriteItem Tier 1 3 diverging
View these tests in the suite →- BatchWriteItem - index key validation rejects a non-scalar index key value source:38
- BatchWriteItem - validation rejects a wrong-typed table key value source:99
- BatchWriteItem - validation rejects a non-scalar table key value source:115
-
updateTable Tier 2 3 diverging
View these tests in the suite →- UpdateTable - add GSI accepts a conflicting redeclaration of an existing key attribute and keeps the stored type source:454
- UpdateTable - add GSI drops an unused AttributeDefinition supplied with a GSI add source:546
- UpdateTable - GSI validation rejects a GSI keyed on a table attribute omitted from the request AttributeDefinitions source:745
-
query Tier 1 2 diverging
View these tests in the suite →- Query - Limit + FilterExpression interaction rejects ExclusiveStartKey that does not match the table schema source:400
- Query - KeyConditionExpression semantics rejects a nested path on a key attribute source:54
-
describeTable Tier 1 1 diverging
View these tests in the suite →- DescribeTable - TableId returns a stable TableId across repeated DescribeTable calls source:44
-
updateItem Tier 1 1 diverging
View these tests in the suite →- UpdateItem - ReturnValues granularity UPDATED_NEW on a nested SET returns only the changed fragment source:962
-
updateTable Tier 1 1 diverging
View these tests in the suite →- UpdateTable - configuration parameters UpdateTable changes TableClass source:57
-
legacy-api Tier 3 1 diverging
View these tests in the suite →- Legacy API - AttributeUpdates (legacy UpdateExpression) AttributeUpdates with a Value and no Action defaults to PUT source:279
What it doesn't attempt
Operations DynamoDB Local declines rather than gets wrong, so none of this counts towards its divergence. It is what the gap in its 94.2% coverage is made of. Each test here skipped itself because the target's own feature probe said the operation isn't implemented, which is often a deliberate choice rather than a defect.
-
vectorSearch Tier 2 none of it 36 not attempted
View these tests in the suite →- SearchVectors - ConsumedCapacity shape reports VectorSearchRequestBytes with no classic capacity fields
- SearchVectors - ConsumedCapacity shape reports the same shape under INDEXES as under TOTAL
- SearchVectors - ConsumedCapacity shape reports nothing under NONE
- PutItem - vector write capacity shape INDEXES adds a per-index VectorWriteRequestBytes map beside the classic fields
- PutItem - vector write capacity shape TOTAL folds nothing in: no vector fields at all
- PutItem - vector write capacity shape a write not touching the vector attribute reports no vector write
- PutItem - vector write capacity shape an identical overwrite reports no vector write: replication is delta-based
- PutItem - a vector index is charged on the change to its stored view charges the index that projects the changed attribute, and not the one that does not
- PutItem - a vector index is charged on the change to its stored view charges neither when the write changes nothing either index holds
- PutItem - VectorWriteRequestBytes reports the 1024 floor for an entry below it on every term
- PutItem - VectorWriteRequestBytes applies the floor per index, not per write
- PutItem - VectorWriteRequestBytes charges four bytes per dimension
- PutItem - VectorWriteRequestBytes charges the vector attribute’s name by its own length
- PutItem - VectorWriteRequestBytes charges a projected non-vector attribute its own item size
- CreateTable - vector index lifecycle walks CREATING to ACTIVE and describes the index faithfully
- CreateTable - vector index lifecycle round-trips a SearchSchema of HASH and INLINE_FILTER elements
- CreateTable - vector index lifecycle accepts the 4096-dimension boundary
- SearchVectors - index readiness after CreateTable rejects retryably between ACTIVE and the first served search
- PartiQL - vector indexes are out of reach rejects a PartiQL read of a vector index
- PartiQL - vector indexes are out of reach reads the vector attribute off the base table like any other item
- SearchVectors - deterministic search behaviour COSINE: identical vector scores 0, opposite scores 2, lower is closer
- SearchVectors - deterministic search behaviour EUCLIDEAN: identical vector scores 0, straight-line distance otherwise
- SearchVectors - deterministic search behaviour DOT_PRODUCT: higher is closer and scores can be negative
- SearchVectors - deterministic search behaviour returns the identical vector as the top match
- SearchVectors - deterministic search behaviour omits the vector attribute by default and returns it when projected
- SearchVectors - deterministic search behaviour caps results at the item count with no pagination surface
- SearchVectors - deterministic search behaviour stores full precision on the base table and f32 in the index
- UpdateTable - vector index lifecycle adds an index that backfills like a GSI, enforces one online action, then deletes it
- UpdateTable - vector index lifecycle refuses to delete the table while a vector index is still being created
- UpdateTable - vector index lifecycle reports UPDATING with Backfilling false while allocating, and takes a cancel only once backfilling starts
- CreateTable - vector index request validation rejects Dimensions of 0 at the request model layer
- CreateTable - vector index request validation rejects an index name shorter than 3 characters
- SearchVectors - request validation rejects TopK of 0 at the request model layer
- SearchVectors - request validation rejects a search against an index the table does not have
- PutItem - vector index write validation accepts a write missing the HASH attribute but leaves it unreachable through that index
- PutItem - vector index write validation removes an item from the index when its vector attribute is removed
-
tags Tier 2 none of it 8 not attempted
View these tests in the suite →- Tags - basic adds tags to a table
- Tags - basic lists tags and verifies they match what was added
- Tags - basic adds additional tags and verifies all tags are present
- Tags - basic removes specific tag keys with UntagResource
- Tags - basic verifies removed tags are gone after untag
- Tags - basic overwrites an existing tag with the same key but different value
- Tags - validation rejects TagResource with an invalid ARN format
- Tags - validation rejects ListTagsOfResource with a non-existent ARN
-
backups Tier 2 none of it 5 not attempted
View these tests in the suite →- Continuous backups - PITR reports PITR DISABLED by default
- Continuous backups - PITR enabling PITR transitions PointInTimeRecoveryStatus to ENABLED
- On-demand backups - lifecycle and restore CreateBackup → DescribeBackup → ListBackups → DeleteBackup
- On-demand backups - lifecycle and restore RestoreTableFromBackup initiates a restore into a new table
- On-demand backups - lifecycle and restore DescribeBackup on a deleted backup throws BackupNotFoundException
-
contributorInsights Tier 2 none of it 2 not attempted
View these tests in the suite →- Contributor insights - enable/describe/list reports DISABLED by default
- Contributor insights - enable/describe/list enabling transitions the status and lists the table
-
export Tier 2 none of it 2 not attempted
View these tests in the suite →- Export and import - S3 ExportTableToPointInTime initiates an export and reports it
- Export and import - S3 ImportTable ingests S3 data into a new table
-
resourcePolicy Tier 2 none of it 2 not attempted
View these tests in the suite →- Resource policies - Put/Get/Delete GetResourcePolicy on a table with no policy throws PolicyNotFoundException
- Resource policies - Put/Get/Delete Put then Get round-trips the policy, and Delete removes it
-
account Tier 2 partly 1 not attempted
View these tests in the suite →- Account reads - DescribeLimits, DescribeEndpoints DescribeEndpoints returns at least one endpoint with an address
-
kinesis Tier 2 none of it 1 not attempted
View these tests in the suite →- Kinesis streaming destination enables a streaming destination and reports it via Describe
Run history
Every percentage here is divergence, per tier and over the whole suite, so lower is better in each column. Coverage is the exception it is named as.
| Run | Gradecurrent criteria | Divergence | Movement |
|---|---|---|---|
| Grade C | 14.7% | unchanged | |
|
Suite on 3.6.0 was cut but never published. eu-west-2 changed how it validates TransactWriteItems while the 3.6.0 measurement was running, so five tests failed against DynamoDB itself and no board was produced. This release carries the fix, and the changes listed under 3.6.0 are first measured here. eu-north-1 and ap-northeast-2 made the change first, and eu-west-2 followed on 2026-10-08, between two runs on main 30 minutes apart. The three now check a transaction's request before running it. An empty TransactItems gets the validation framework's generic constraint message. A 32-level value in the request is refused with a top-level ValidationException, where the transaction used to cancel on it or go on to evaluate the condition. A transacted Update that UpdateItem's statement-sized rule refuses is refused the same way, where it used to be stored. The other 30 regions still answer as before. The five tests accept either answer, exactly, until the regions settle. No engine loses a test over it, and on the 3.5.0 board's results the engines that already refuse a 32-level value up front pass tests they used to fail: three for LocalStack, and one each for DynamoDB Local, ExtendDB and ExtendDB (SQLite). The tests keep their names, which describe what the 30 regions do, until one answer is pinned, because a rename needs every committed results file re-run. The board and the results table now sort by grade, best first, and rows sharing a grade by the effective figure the letter is read from. They used to sort on divergence alone, and coverage lowers a letter without moving a row, so a target diverging slightly less over much less of the suite could sit above a better-graded one. No grade or figure changes. |
Grade C | 14.7% | diverged 0.1 percentage points less |
|
Suite on Five Scan error messages are now regional splits. The validation-framework
rollout reached Scan's parameter checks in September, and eu-west-2,
eu-central-1, us-west-1 and ap-northeast-2 now word the errors for The negative The nesting-depth row moves af-south-1, ap-southeast-3, ap-southeast-4, ap-southeast-5 and il-central-1 to the strict side, leaving 22 regions strict and 11 lax. ap-northeast-1 answers both ways and stays lax for now. UpdateItem's item size is now a regional split, across eleven tests. Twenty-two regions, eu-west-2 among them, size an update by what the statement writes, as the suite already pinned, while ten cap the finished item at 409,600 like any other write. Engines that apply the plain cap are credited in those ten. Fourteen cases from @exoego for the 4096-byte expression cap and the 32-level nesting cap on the batch and transact write surfaces, captured against eu-west-2 and us-east-1.
|
Grade C | 14.8% | diverged 0.9 percentage points less |
|
Suite on Kumo joins the board, suggested by @exoego. It is a Go emulator covering 82 AWS services, of which DynamoDB is one, and it runs from a container image or a single binary with nothing else to install. The board's separate support and capability pages are now one emulator directory, with each project's feature and operation support in a single entry. |
Grade C | 15.7% | unchanged |
| Grade C | 15.7% | unchanged | |
|
Suite on Thirteen captures against eu-west-2 turned into coverage, and the suite grew from 1056 tests to 1251. All of it was ground truth nothing asserted, so an engine could discard a PartiQL index qualifier or store an item AWS would refuse and still score a clean pass.
Two fixes came with it. A local run against real DynamoDB takes its own table
namespace, so it can no longer delete a CI run's tables. And a
The over-25-requests assertion beside it spans both cohorts instead of becoming a second row. Neither wording is byte-stable: the table name carries a per-run suffix, the old cohort echoes all 26 requests back, and seven regions echo them as a JVM object identity rather than expanded fields. A row records one verbatim answer per region and there is nothing verbatim here to record, so the anchored pattern grew a second branch instead. It still refuses a wrong limit and a wrong table, and it matches every one of the 33 answering regions. The capture harness can take that evidence without creating tables. |
Grade C | 15.7% | diverged 0.6 percentage points more |
| Grade C | 15.1% | unchanged | |
| Grade C | 15.1% | unchanged | |
| Grade C | 15.1% | unchanged | |
|
Suite on AWS corrected the vector index readiness documentation, prompted by a write-up of the earlier guidance that drew on the suite's measurements. The ACTIVE-plus-backfilling state the old advice was built around, and which no index ever occupies, is gone from the three pages that described it. The wait now reads "Backfilling is not true" rather than "is false", so a check written literally from it fires on both creation paths instead of neither. The tutorial no longer says a search during backfill can return incomplete results. Two things the suite had measured but nobody had written down are documented as well: that DescribeTable reporting ACTIVE leads the dedicated search endpoint, and that the readiness check depending on neither status field is a real search in a retry loop. That contract is now pinned rather than described. The UpdateTable walk asserts that Backfilling true is only ever reported alongside CREATING, that an ACTIVE index reports no Backfilling field at all, and that the base table goes ACTIVE while the index is still building, which is what makes a table waiter the wrong gate for a search. The first search that succeeds has to carry every seeded item, since the backfill window answers with an error rather than a partial view. On the CreateTable path a new test runs the documented check the way an application would, and every rejection before the first served response has to be the retryable ValidationException rather than a not-found. The suite's own search wait now absorbs those two rejections and rethrows every other answer, so a fixture waiting on an index that is ACTIVE but not yet served no longer fails on the lag it was waiting out. Two files asserting exact rejection messages wait for a served search rather than for ACTIVE: "does not have the specified index" is also what a freshly ACTIVE index says, and it would otherwise stand in for whichever message the case asked for. The tutorial's other new claim, that a table cannot be deleted while a vector index is being created, has a test of its own. Only the UpdateTable path can ask it. Across three runs an index created with its table reached ACTIVE in the same 250ms poll as the table, so the table is never ACTIVE with the index still building there, and a DeleteTable during creation is refused for the table's own status rather than with the documented index wording. Adding an index to a live table opens that window about thirty seconds in. The test cancels the index afterwards instead of waiting out the backfill, which a still-creating vector index turns out to accept the way a backfilling GSI does, so it costs a minute rather than seventeen. A release now dispatches its measurement as the results bot rather than with
the workflow's own token. GitHub raises no |
Grade C | 15.1% | unchanged |
|
Suite on The board now measures the most recent release tag rather than Every board now says what produced it. A board is graded against the suite manifest and split registry as they stood at the ref it measured. Region health is the exception and is read live, so a region dropped since the tag still counts against today's cohorts. That is the one input allowed to move under a board without a new measurement, and the board carries a health date beside its measurement date to say so. Releases are cut by one workflow dispatch: it bumps the version, dates this section, installs against the bumped tree, tags, and opens a draft release, then starts the measurement. The draft publishes itself when the board carrying that version lands, which takes about three hours. eu-west-2 has crossed to the validation framework's generic constraint message
for The matching validation-ordering row is retired. Both wordings refuse an empty
A probe absent from the baseline is no longer reported as drift. Adding a probe to the capture script leaves every older baseline without it, and a scheduled red then named the new probe as the thing that had moved. The weekly cross-region capture now includes eu-west-2, so the drift lens reads its baseline and the candidate regions from one capture taken at one moment rather than comparing today's candidates against an older baseline file. A scheduled red also keeps the eu-west-2 capture its drift verdict was read from, which was previously discarded with the runner. |
Grade C | 15.1% | unchanged |
| Grade C | 15.1% | unchanged | |
|
Suite on ExtendDB's SQLite backend joins the run, built from the same release as the PostgreSQL one and held to the same TLS, SigV4 and IAM posture, so the storage engine is the only thing that differs between them. A project's other builds now sit behind a disclosure on its row. Every build is measured in full and has a row of its own with its own figures; the disclosure starts closed only when every build under it reads the same grade, divergence and coverage as the row above, and only when each of them was measured in that run: a carried row on either side opens it, and so does a run the suite declined to score. It is read from each run, so a build can start closed on one and open on the next. The README table has no disclosure to offer, so it lists every build outright. Every target in the data endpoints gains two fields.
The |
Grade C | 15.1% | diverged 0.1 percentage points less |
| Grade C | 15.2% | diverged 0.8 percentage points less | |
|
Suite on Read this first if you consume the JSON. The data endpoints go from schema 2 to schema 4 in one step. Schema 3 was never published on its own, so everything on 2 crosses both steps at once. Schema 3 breaks in four ways:
Schema 4 is additive on top: each target carries its grade and the full criteria
in A score is two figures, never oneDivergence is the share of the whole suite a target answers differently from real DynamoDB. Coverage is the share it implements at all. They are reported apart and never summed, because a declined operation is discoverable in minutes and a wrong one in production. No target was re-run for the change and no pass, fail or skip moved: what changed is how the same counts are expressed. Everything else that was a percentage followed the headline down - tier figures, the per-region drilldown, the per-operation table, and the colour bands, which inverted with them. A target's history is two plots rather than one, because divergence falls when a target stops attempting something it used to get wrong, so a divergence line alone can render a withdrawal as an improvement. Every target wears a letterDivergence sets it - A under 5%, B under 15%, C under 25%, D under 35%, F beyond
These are grading criteria version 1, dated in the methodology, which carries the derivation. Where a threshold sits is a hand-picked input to a published letter, and moving one regrades targets whose results never changed, so any change to a band, the coverage weight or the A+ gate bumps the version. The suite grows from 998 tests to 1054Vector search (#125). 42 tests over the deterministic surface DynamoDB
shipped in August 2026: the index lifecycle on both creation paths, request
validation on each plane, rejection wording, write-path validation, search on a
fixture where the nearest neighbour is unambiguous, the two new capacity shapes,
and PartiQL's inability to reach a vector index. Every pinned value was
characterised against real DynamoDB in eu-west-2 before it was asserted. Two
findings worth naming: searching during a backfill is an error, which settles
which side of a contradiction in AWS's own documentation is right - three
developer-guide pages say the call fails, the tutorial page says results can be
incomplete - and an overwrite leaving the stored vector unchanged reports no
vector write capacity at all, because index replication is delta-based. Both
sides are captured in Index write costs (#124). 14 tests. The suite's only per-index capacity assertion was on a Query, so the write side - the half you get billed extra for - went unmeasured. A sub-1KB write costs one unit for the table and one for each index it lands in, and LSI units fold into the total exactly as GSI units do. Moving an item to a new GSI key costs two on that index, a delete and an insert; touching a projected attribute costs one; touching a non-projected attribute costs nothing, and the response carries no arm for that index rather than a zero. An overwrite that leaves the item unchanged reports no index cost whatsoever. The index exclusions create no indexed table (#116). Corrections
|
Grade C | 15.9% | diverged 0.1 percentage points less |
| Grade C | 16.0% | diverged 0.1 percentage points more | |
| Grade C | 15.9% | unchanged | |
| Grade C | 15.9% | unchanged | |
| Grade C | 15.9% | unchanged | |
| Grade C | 15.9% | unchanged | |
| Grade C | 15.9% | diverged 0.9 percentage points less | |
| Grade C | 16.8% | diverged 0.9 percentage points more | |
|
Suite on Grew to 982 tests, up 28, all characterised against real DynamoDB across the per-region ground truth 2.0.0 put in place. New coverage is PartiQL's RETURNING clause; the GSI lifecycle also joins the ground truth, and the sweep's drift classifier gains a converged case.
|
Grade C | 15.9% | unchanged |
| Grade C | 15.9% | unchanged |
Showing the 24 most recent runs. The chart above covers the full history, and every run is browsable from Runs.