EventBridge cost explained: what you pay for events and rules

Quick answer

EventBridge charges primarily per custom event published to a bus, commonly around one dollar per million events, while events delivered from AWS services to the default bus are free. Rules and targets themselves are not billed per invocation, but each matched event that fans out to multiple targets is delivered without extra per-target event charges. Extras apply for schema discovery, event replay, and cross-Region or cross-account delivery. For most workloads EventBridge is inexpensive; the cost only grows with very high event volumes or heavy archive and replay usage.

Amazon EventBridge is a serverless event bus that routes events from AWS services, your own applications, and SaaS partners to targets like Lambda, Step Functions, and SQS. Its pricing is simple in outline but has a few line items worth knowing, because the free default bus and the paid custom events behave differently.

What EventBridge charges for

Line item	How it is billed
AWS service events (default bus)	Free to receive and match
Custom and partner events	Per million events published (about a dollar per million)
Schema discovery	Per million events ingested for discovery
Event replay and archive	Archive storage plus replay processing
Cross-Region delivery	Per million events plus data transfer

The most important distinction: events emitted by AWS services (an EC2 state change, an S3 notification via the default bus) are free, while events you publish yourself with PutEvents cost approximately a dollar per million. Rules that match and route events do not add a separate per-invocation event charge, so fanning one event out to several targets does not multiply the event bill. You still pay the downstream target's own costs, such as Lambda invocations.

EventBridge Scheduler and Pipes

EventBridge Scheduler, which replaces cron-style scheduled rules, is billed per scheduled invocation at a very low per-million rate, so even millions of scheduled jobs cost a few dollars. EventBridge Pipes, which connect a source to a target with optional filtering and enrichment, charges per request processed by the pipe. Both are cheap for typical use but worth watching if you drive extremely high volumes, the same way you would watch a Lambda deep dive for invocation counts.

Where EventBridge cost can surprise you

The surprises are rarely the event charges themselves. They come from the targets: an event that triggers a heavy Lambda, a Step Functions workflow, or a chatty downstream API can cost far more than the event routing. Event replay over a large archive can also reprocess millions of events at once, driving both replay and downstream target costs. And cross-Region event delivery adds both a per-event charge and data transfer style costs, so keep event routing in-Region when you can.

Keeping EventBridge cheap

Use the free default bus for AWS service events rather than republishing them as custom events, filter aggressively with detailed event patterns so rules only match what matters, and avoid emitting high-frequency custom events when a single batched event would do. Watch archive retention and only replay the window you need. Because the target costs usually dominate, treat EventBridge as a cheap router and focus optimization on what the events trigger, alongside the broader hidden AWS costs that accumulate around serverless architectures. For a full price picture of the resources your events invoke, see the resource catalog.

FAQ

How much does EventBridge cost per event?

Custom and partner events published with PutEvents cost approximately one dollar per million events in most Regions. Events emitted by AWS services to the default event bus (EC2 state changes, S3 notifications, and similar) are free to receive and match. So a workload publishing a few million custom events a month typically pays only single-digit dollars for EventBridge itself.

Are EventBridge rules charged per invocation?

No. EventBridge does not add a separate per-invocation charge for rules matching and routing events, and fanning one event out to multiple targets does not multiply the event cost. You pay the per-event publishing charge (for custom events) once, plus the downstream cost of whatever targets the event triggers, such as Lambda invocations or Step Functions transitions.

Is the EventBridge default bus free?

Receiving and matching events that AWS services send to the default event bus is free. You only start paying when you publish your own custom events, use partner event sources, enable schema discovery, archive and replay events, or route events across Regions. For many architectures that rely mostly on AWS service events, EventBridge is nearly free.

How much does EventBridge Scheduler cost?

EventBridge Scheduler charges per scheduled invocation at a very low per-million rate, so even running millions of scheduled jobs a month costs only a few dollars. It is generally cheaper and more flexible than older cron-style scheduled rules, and the invocation cost is almost always dominated by whatever target the schedule triggers.

What makes EventBridge bills grow unexpectedly?

The event charges themselves rarely dominate. Growth usually comes from the targets events trigger (heavy Lambdas, long Step Functions workflows, chatty downstream calls), from event replay reprocessing a large archive at once, and from cross-Region delivery which adds both per-event and data-transfer style charges. Optimizing the targets and keeping routing in-Region controls most of the cost.

Does C3X price EventBridge and its targets?

C3X reads your Terraform and prices the resources you define, including event-driven components and the targets events invoke, against a live pricing catalog before you deploy. That lets you see the cost of an event-driven design (buses, schedules, and the Lambdas or workflows they trigger) in the pull request rather than discovering it on the bill.

What to do next

Price your event-driven architecture before it ships. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.