eventbridge cost calculator

How EventBridge pricing works (without the confusion)

EventBridge is powerful because it decouples services and lets your architecture react to events in near real time. The pricing can look simple at first glance, but real bills depend on how many events you publish, how many rules match each event, and what optional features (archives, replay, Pipes, API destinations) are enabled.

The calculator above is designed to make this visible. Instead of one big number, it helps you understand each cost driver so you can forecast spend before traffic grows.

What this EventBridge cost calculator includes

1) Event ingestion

When your applications publish custom events or partner events, pricing is typically measured per million events. If your volume is high, this is often the first major cost line item.

2) Rule matching and fan-out

A common surprise: one event can match multiple rules, and each match can count toward billable invocations. If one event fans out to five targets, your invocation count can grow quickly.

3) Archives and replay

If you use EventBridge archives for compliance, debugging, or backfills, storage is usually billed per GB-month. Replaying archived events can add separate charges based on replay volume.

4) EventBridge Pipes and API destinations

Pipes and API destinations can simplify integration logic, but they also add usage-based pricing. Estimating these independently helps you avoid under-budgeting integration-heavy workloads.

How to estimate your monthly usage accurately

• Start from production metrics: Use CloudWatch or internal telemetry to get real event counts.
• Apply growth assumptions: Add a realistic growth factor (for example, 20–40%) for next quarter planning.
• Model fan-out explicitly: Track events published and rule matches separately.
• Include reprocessing scenarios: If your team replays events during incidents, include that volume.
• Review region-specific pricing: Rates can vary by region and over time.

Example: quick planning scenario

Suppose your platform publishes 10 million custom events monthly and each event matches 2.5 rules on average. That gives you 25 million rule matches. Add moderate archive storage and a small amount of Pipes/API destination usage, and the monthly total can look very different from your initial “events published” estimate.

That is exactly why this calculator separates inputs by cost component: ingestion, matches, storage, replay, and integration requests.

Ways to reduce EventBridge costs

• Tighten event patterns: Avoid broad rules that match more events than needed.
• Minimize unnecessary fan-out: Route events to only the services that truly need them.
• Use event filtering upstream: Filter early to reduce downstream invocations.
• Control archive retention: Keep only the retention window required for compliance and operations.
• Audit replay habits: Replay only relevant ranges instead of full-history reprocessing.

Common mistakes teams make

Ignoring the difference between events and matches

Publishing 5 million events does not mean only 5 million billable actions. If each event triggers multiple rules, total billable matches can be many times higher.

Assuming default rates are always current

Cloud pricing changes. Treat the default values in any calculator as placeholders and validate against official AWS pricing before committing budgets.

Forgetting non-EventBridge costs

EventBridge may trigger Lambda, Step Functions, API calls, or third-party services. Total system cost includes those downstream components too.

Final notes