DynamoDB query console
Find the existing DynamoDB docs for Search, PartiQL, saved queries, history, code generation and local JavaScript.
DynamoDB has more than one way to read a table. Search uses a condition builder that can route to a Query or a Scan and explains the cost of the choice. SQL is the PartiQL editor, with syntax highlighting and autocomplete. A query should remain read-only unless its write behavior is explicit and reviewed.
The Entities model can also explain which access patterns are supported by the keys and indexes inferred from loaded items. When a pattern requires a Scan, the interface can make that cost visible and suggest the shape of a secondary index without pretending that the migration has already happened.
Queries can be saved, revisited from history and turned into SDK or CLI code. The ›_ console panel runs JavaScript over rows already loaded in memory, so it is useful for local inspection without sending another request to AWS. None of these tools should hide the profile, region, table or read scope that produced the result.
For detailed workflows, open Search: Query vs Scan builder, The PartiQL editor, Saved queries & history, Code generation and JavaScript REPL.