All Services
App Integration
Amazon EventBridge
Amazon EventBridge routes events from AWS services, custom applications, and SaaS sources through event buses, rules, pipes, and API destinations; EventBridge Scheduler handles large-scale timed invocation.
Explore pricing models, common use cases, infrastructure support, and the AWS services that commonly work with Amazon EventBridge.
Amazon EventBridge pricing and cost programs
Pricing model: Event and workflow usage
- On-Demand
- Available
- Reserved Instances or reserved capacity
- Not applicable
- Savings Plans
- Not applicable
- Spot
- Not applicable
Billing dimensions: Events published · Event delivery · Pipes requests · Scheduler invocations
Programs and modes: Event buses · Pipes · Scheduler · Schema Registry
Event type, source, target, and EventBridge capability determine billable operations.
Free Tier: Service-specific — verify current offers
Pricing reviewed 2026-07-25. Reviewed against the linked official AWS pricing page. Recheck regional rates and program terms before purchase.
Official AWS pricing
Official AWS sources reviewed 2026-07-21.
Why implement Amazon EventBridge?
- Decouples many event producers from many consumers through content-based routing without running a central event-broker cluster.
- Connects AWS, custom, SaaS, and HTTP destinations with cross-account buses, input transformation, Pipes enrichment, Scheduler, schema registry, archives, and replay.
- Lets consuming teams own narrow rules and targets while publishers emit stable domain facts rather than calling every downstream system.
How to implement Amazon EventBridge
- Choose an event bus for many-to-many routing, a Pipe for one-source-to-one-target integration, or Scheduler for timed invocations; define ownership, account boundaries, and routing policies.
- Publish versioned events with stable source, detail-type, identifiers, timestamps, and business detail, then create precise patterns and usually one target per rule with the required invocation role or resource policy.
- Configure retry age and attempts, DLQs, archives where replay is required, schema controls, transformations, CloudWatch alarms, and tests for duplicates, loops, throttling, target failure, cross-account denial, and replay.
Amazon EventBridge best practices
- Treat delivery as at least once and unordered, make targets idempotent, put durable buffering in front of constrained consumers, and preserve event identifiers for tracing and deduplication.
- Make patterns as precise as possible, include source and detail-type, guard against self-triggering loops, prefer one target per rule, and monitor unexpected match volume as publishers evolve.
- Use resource and identity policies with least privilege, separate sensitive event traffic where useful, validate schemas, configure DLQs, and rehearse archive replay without sending historical side effects twice.
Amazon EventBridge use cases and server impact
- Domain-event routing across microservices
- Cross-account AWS operational events
- SaaS integrations, point-to-point pipes, and scheduled automation
Replaces event-router and integration-broker infrastructure for supported patterns, while event contracts, consumer idempotency, ordering strategy, and failure recovery remain architectural responsibilities.
Official implementation resources
How Amazon EventBridge works with other AWS services
Arrows show the documented technical direction. Reciprocal navigation does not imply a reverse technical dependency.
Official AWS sources reviewed 2026-07-25.
Amazon EventBridge → AWS Lambda
EventBridge rules match event content and deliver matching events to Lambda as a target.
- Why teams use it
- Producers stay unaware of consumers while teams add filtered asynchronous processing.
- Permissions and networking
- Use resource policies or execution roles as required, define stable event contracts, configure retries and dead-letter handling, and prevent recursive event loops.
- Pricing and security caveats
- Event ingestion, rule matching, archive or replay, and Lambda execution can each add cost; delivery order is not guaranteed for a standard event bus.
Amazon EventBridge → Amazon Simple Queue Service
EventBridge rules or Pipes can send selected events to an SQS queue for buffered consumption.
- Why teams use it
- This combines content-based routing with durable queue-based backpressure.
- Permissions and networking
- Allow the EventBridge service to send to the queue, align encryption permissions, and configure retry and dead-letter behavior on both sides.
- Pricing and security caveats
- EventBridge and SQS requests are separately billed, and adding a queue increases delivery latency while improving buffering.
Amazon EventBridge → Amazon Simple Notification Service
An EventBridge rule can publish a matched event to an SNS topic, which then fans the message out to its subscriptions.
- Why teams use it
- Teams combine event filtering with one-to-many notification delivery.
- Permissions and networking
- Authorize topic publication, align encryption keys, filter subscriptions deliberately, and protect downstream endpoints from duplicate or unexpected messages.
- Pricing and security caveats
- Each service has separate request and delivery pricing, and SNS delivery semantics vary by subscription protocol.
Amazon EventBridge → AWS Step Functions
EventBridge can start a Step Functions state machine when a rule or pipe matches an event.
- Why teams use it
- The pairing moves multi-step coordination, retry, and branching out of producers and individual functions.
- Permissions and networking
- Use an execution role limited to the intended state machine, create idempotent start behavior, and select Standard or Express workflow semantics deliberately.
- Pricing and security caveats
- EventBridge delivery and Step Functions state transitions or requests are billed separately; workflow type changes durability, logging, and pricing behavior.
Architecture patterns using this service
- Design event-driven processing with EventBridge, SNS, SQS, Lambda, and Step Functions — Route events with EventBridge or fan them out with SNS, buffer work in SQS, process messages with Lambda, and orchestrate multi-step work in Step Functions when needed.
- Scan uploaded objects for malware and quarantine them on AWS — Land untrusted uploads in a private Amazon S3 bucket, scan them with GuardDuty Malware Protection for S3, route scan results through EventBridge and SQS, and promote only clean objects to a bucket consumers can read.
- Process images and media after an Amazon S3 upload — Take a presigned Amazon S3 upload through EventBridge and SQS to Lambda, Fargate, or AWS Batch workers, write derived assets to a separate bucket, and serve them through CloudFront.
- Fan out AWS events to isolated consumers — Publish one event to EventBridge or SNS, give every consumer its own SQS queue, retry policy, and dead-letter queue, and let each consumer scale, fail, and deploy without touching the others.
Planning guides that use Amazon EventBridge