Event fan-out architecture
One published event, several independent consumers, each with its own queue and failure path.
AWSeventbridgesnsfan-outdecoupling
What is in it
Every resource, and what it costs.
Projections from August 2026 list prices for always-on resources. Connect an account and these become the figures your provider actually bills.
| Node | Type | What it is | Projected |
|---|---|---|---|
| EventBridge bus | Messaging | 2M events | $2.00/mo |
| SNS topic | Messaging | 1M notifications | $1.00/mo |
| Email queue | Messaging | 5M requests | $2.00/mo |
| Analytics queue | Messaging | 5M requests | $2.00/mo |
| Email consumer | Compute | 5M invocations · 512 MB · ~150 ms | from $8.00/mo |
| Analytics consumer | Compute | 5M invocations · 512 MB · ~150 ms | from $8.00/mo |
| Email provider | External | 50k sends | $15/mo |
Agent steps are priced from provider-reported token usage once the agent runs, not estimated. Guardrails cost nothing and are the reason a runaway agent cannot. 2 rows show from because those services bill by usage, so the total is a scenario at the stated volumes, not a quote.
Open Event fan-out on the canvas.
It loads as an editable graph. Connect an account or instrument an agent and the projected figures above become measured ones.