DynamoOps
Operations and insights

Live Streams viewer

Watch INSERT, MODIFY and REMOVE events arrive in real time from DynamoDB Streams, with keys, timestamps and attribute-level change summaries. Pause, resume and clear at will.

Prerequisites

The table must have DynamoDB Streams enabled. DynamoOps reads the stream but does not enable or configure it; do that in the AWS Console under the table’s Exports and streams tab, or with the CLI.

bash
aws dynamodb update-table --table-name orders \
  --stream-specification StreamEnabled=true,StreamViewType=NEW_AND_OLD_IMAGES
Stream view typeWhat the feed can show
KEYS_ONLYOperation type and keys
NEW_IMAGEINSERT attribute counts; MODIFY without diffs
OLD_IMAGEREMOVE context; MODIFY without diffs
NEW_AND_OLD_IMAGESEverything, including added, removed and changed attributes on MODIFY

If the table has no stream, clicking the button shows “Stream is not enabled for this table” with a pointer to the console. The IAM principal needs dynamodb:DescribeStream, dynamodb:GetShardIterator and dynamodb:GetRecords.

Opening the feed

  1. Click ⚡ Stream

    A badge next to the button shows the stream view type in short form (KEYS, NEW, OLD or NEW+OLD); hover it for the full name. The Live Stream panel opens with a pulsing indicator and an event counter.

  2. Make a change

    Edit an item in another tab, run a PartiQL UPDATE or let your application write. Events appear within a few seconds, newest at the top.

  3. Control the feed

    ⏸ Pause stops polling and ▶ Resume drains the backlog; Clear empties the list.

The live feed. MODIFY rows summarise changed (~), added (+) and removed (−) attributes.

Reading events

Each row shows the local time, a colour-coded operation badge, the item keys and a change summary.

BadgeSummary
INSERTNumber of attributes in the new item
MODIFYUp to three attribute changes: +added, −removed, ~changed, then “+N more”. Requires NEW_AND_OLD_IMAGES.
REMOVEKeys only
Summaries, not full images
The feed is designed for watching activity, not for forensic inspection. It shows a one-line diff per event rather than the complete old and new images.

How polling works

  • DynamoOps describes the stream, keeps the open leaf shards and requests iterators positioned at LATEST. You see events that occur after the panel opens; there is no replay of history.
  • Polling runs every 3 seconds, fetching up to 100 records per shard per poll, using the tab’s connection. LocalStack endpoints work.
  • Up to 200 events are kept; older ones roll off.
  • The panel closes automatically when you switch tabs or disconnect. Reopening starts fresh from LATEST.
  • There is no filtering by event type or key; use Clear to start a clean window.

For a per-item change log that survives across sessions, pair Streams with Version History.

Related