Cost visibility
Know the costbefore and while you run.
Dynomatic prices a read before you run it, warns while a filter throws away most of what DynamoDB is charging you to scan, and totals what every table and index consumed in Command history. Every figure is in read and write capacity units, from the numbers DynamoDB reports.
The price before you press Run. A strip under the Filters builder says what the next Run will read, in RCU, and follows every edit. A Scan shows this run's figure beside the whole table's. With a filter the run figure is a floor, because a filter drops items only after DynamoDB has read and charged for them. A Query says its cost depends on how many items match, and adds a ceiling only when the run size is the only limit. The figures average the item count and size DynamoDB reports, so the strip says Approximate, and it never stops a Run. See the query builder →
A warning while the filter does an index's job. Once a filter has discarded at least nine in ten of 1,000 or more scanned items, the progress pill says how much it threw away and names the attributes the filter read as GSI candidates. It updates with every page, stays after the run settles, and covers Scans and filtered Queries alike. It never blocks: Cancel and Load more stay beside it, and a read under 1,000 items, or one that keeps more than one item in ten, shows nothing.
What it cost, per table and per index. A consumed-capacity strip sits above the Command history timeline: read and write units apart, the operations it covers, and how many reported no units, over exactly the cards your filters leave listed. Switch between the retained window and this session. Per table breaks the total down by read units, with the share of scanned items each table's filters discarded, a Wasteful mark at ten or more scanned per item returned over at least 1,000 scanned, and rows for the base table and every GSI and LSI. Capacity units only, never a dollar figure. See command history →
Where the cost shows
The estimate changes as you add a pill, pick an index, or set a Limit, so it always describes the Run you are about to send.
Turning on consistent read doubles every figure as it flips and adds the consistent 2× tag.
A Query on a KEYS_ONLY or INCLUDE index says what that means: a GSI returns only the projected attributes, and an LSI fetches any other one from the table at extra cost.
When DynamoDB has not reported an item count and size for a table or index, the strip says there is no estimate.
PartiQL runs count as reads or writes by their statement, so a SELECT lands in read units and an UPDATE in write units.
None of it gates a Run. The strip informs, the warning rides the stream controls and fades with them, and history adds up what already ran.