dynamodb-streams

Guidelines for processing DynamoDB Streams, records of changes made to a DynamoDB table. A Lambda function reads added, changed, or removed items and can pass the changes to another service such as OpenSearch.

In plain words
What is it for?
Building Lambda handlers for INSERT, MODIFY, and REMOVE events, converting DynamoDB data into normal objects, and synchronizing changes with OpenSearch, analytics, or caches.
Why use it?
They provide a consistent way to react to database changes without repeatedly checking the table for updates.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/goranerhartic/cursor-development-rules/dynamodb-streams
Clone the repo
git clone --depth 1 https://github.com/GoranErhartic/cursor-development-rules

Made for: Cursor.

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 672 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00027 $0.00672
Opus 5 $0.00014 $0.00336
Sonnet 5 $0.00005 $0.00134
Haiku 4.5 $0.00003 $0.00067

Measured 2d ago against content hash f8298de85171, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dynamodb-streams scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/languages/aws-lambda/dynamodb-streams.mdc · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DynamoDB Streams

Use DynamoDB Streams for event-driven processing (e.g. syncing to OpenSearch, analytics, cache invalidation). Enable streams on the table in CDK and add a Lambda event source mapping.

Stream Handler for OpenSearch Sync

// src/functions/sync-to-opensearch/handler.ts

import type { DynamoDBStreamHandler, DynamoDBRecord } from "aws-lambda";
import { unmarshall } from "@aws-sdk/util-dynamodb";
import type { AttributeValue } from "@aws-sdk/client-dynamodb";
import { logger } from "@/shared/logger";
import { opensearchClient } from "@/shared/clients/opensearch";

export const handler: DynamoDBStreamHandler = async (event) => {
  const bulkOperations: object[] = [];

  for (const record of event.Records) {
    const operation = processRecord(record);
    if (operation) {
      bulkOperations.push(...operation);
    }
  }

  if (bulkOperations.length > 0) {
    await opensearchClient.bulk({ body: bulkOperations });
    logger.info({ operationCount: bulkOperations.length / 2 }, "Bulk indexed to OpenSearch");
  }
};

function processRecord(record: DynamoDBRecord): object[] | null {
  const eventName = record.eventName;
  const newImage = record.dynamodb?.NewImage;
  const oldImage = record.dynamodb?.OldImage;

  if (!newImage && !oldImage) {
    return null;
  }

  const item = newImage
    ? unmarshall(newImage as Record<string, AttributeValue>)
    : unmarshall(oldImage as Record<string, AttributeValue>);

  if (item.entityType !== "Listing") {
    return null;
  }

  const documentId = `${item.propertyId}-${item.listingId}`;

  switch (eventName) {
    case "INSERT":
    case "MODIFY":
      return [
        { index: { _index: "listings", _id: documentId } },
        {
          propertyId: item.propertyId,
          listingId: item.listingId,
          agentId: item.agentId,
          price: item.price,
          listingType: item.listingType,
          status: item.status,
          description: item.description,
          photos: item.photos,
          createdAt: item.createdAt,
          updatedAt: item.updatedAt,
        },
      ];

    case "REMOVE":
      return [
        { delete: { _index: "listings", _id: documentId } },
      ];

    default:
      return null;
  }
}

Read the full file on GitHub · 93 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 93 lines · 27 tokens per session scan A f8298de85171

Subscribe to this mod's changes

dynamodb-streams is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 672 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.