Examples / AWS

How does one EventBridge event feed both a pipeline and an archive?

Updated

EventBridge -> {(SQS -> Lambda -> DynamoDB), S3}: the parentheses nest a whole processing chain inside one branch of the broadcast, while the second branch archives the raw event to S3. Chartado animates both branches leaving EventBridge together: process and archive, in parallel.
Event Pipeline Diagram: EventBridge to SQS, Lambda and S3. One event bus feeding both a processing chain and a raw archive. Services drawn: EventBridge, SQS, Lambda, DynamoDB, S3.
A still of the animation above. Every export embeds the diagram source.

THE TEXT THAT DRAWS IT

EventBridge -> {(SQS -> Lambda -> DynamoDB), S3}

Edit it in the box above and the diagram redraws as you type. Export it as an animated GIF, WebM or WebP, or a still PNG. Every format embeds this text, so the file can be read back into the editor.

WHAT IT SHOWS

EventBridge receives an event and sends it two ways at once. One branch is a whole pipeline of its own: SQS buffers it, a Lambda transforms it, DynamoDB stores the result. The other branch drops the untouched event into S3.

The parentheses are doing the work in the text. A branch inside { } is normally a single service, but wrapping a chain in ( ) makes the entire chain one branch. It occupies one row and marches rightwards from the bus, while S3 sits alone on its own row.

Splitting processed data from raw data is one of the few architectural decisions that is almost always right and almost always put off. The processed table answers today’s questions. The S3 copy answers the ones you have not thought of, and it is the only branch that can rebuild the other after a bad deployment.

Two branches, two very different jobs, one event.

QUESTIONS

What do the parentheses in the DSL do?
They nest a chain inside a branch: the broadcast’s first copy enters SQS -> Lambda -> DynamoDB and keeps flowing hop by hop, while the second copy goes straight to S3.
Why archive raw events next to the processing chain?
Replays. When the Lambda logic changes or a bug corrupts writes, the S3 archive lets you re-drive every event through the fixed pipeline.

MORE AWS PATTERNS

Serverless REST API diagram

The request/response backbone of most serverless applications.

API Gateway -> Lambda -> DynamoDB

Pub/sub fan-out diagram

One event, several independent consumers, none of them waiting on each other.

SNS -> {Lambda Emailer, Lambda Analytics, SQS Archive}

Queue worker diagram

Accept the request quickly, do the slow part somewhere else.

API Gateway -> Lambda -> SQS -> Lambda Worker -> DynamoDB

Also on this site: RAG pipeline diagram, Multi-agent router diagram, ReAct tool-calling diagram, Human-in-the-loop diagram, MCP architecture diagram and Cloudflare Workers diagram. See all 10 patterns.

Chartado is a text-to-diagram tool: you type lines like A -> B, it draws the architecture and animates the flow.