What is Amazon EventBridge?
Understand EventBridge event buses, rules, pipes, schemas, targets, schedules, permissions, delivery, and recovery in event-driven AWS systems.
What is Amazon EventBridge?
Amazon EventBridge is a managed serverless service that ingests, filters, transforms, and delivers events between applications, AWS services, and supported third-party sources. Event buses route many sources to many targets, while pipes connect one source to one target with optional filtering and enrichment.
How this topic fits
Messaging & events
Choose between queues, topics, event buses, and streams, then design delivery, ordering, replay, and idempotent consumers.
How EventBridge routes events
An event source publishes a structured event to a bus. Rules evaluate event patterns and send matching events to one or more targets such as Lambda, Step Functions, SQS, SNS, another event bus, or an API destination.
The producer does not need to call each consumer or know how many consumers exist. Each target integration still needs an owner, an IAM path, retry behavior, monitoring, and a recovery decision.
Route events from many application, AWS, or partner sources to zero or more matching targets.
Connect one supported source to one target with filtering, transformation, and optional enrichment.
Create one-time or recurring schedules with delivery windows, retries, and failure retention controls.
Events, patterns, and schemas
EventBridge events include common envelope fields and a detail object owned by the producer. Rules should match stable business or service attributes instead of relying on accidental payload structure.
Define schemas and compatibility expectations for custom events. Keep sensitive data out of broad event distribution, and review which accounts, rules, archives, logs, and targets can read each field.
Delivery, retries, archives, and replay
A successful publish means EventBridge accepted the event, not that every consumer completed its business work. Monitor failed and throttled target delivery, configure dead-letter queues where appropriate, and make consumers safe for duplicate processing.
Archives and replay can help reprocess historical events, but replay is a deliberate production action. Confirm that consumers remain compatible and idempotent, and constrain replay scope so old events do not repeat irreversible effects.
Account and ownership boundaries
Custom buses and resource policies can connect accounts, but cross-account routing expands the trust boundary. Make the event owner, allowed publishers, allowed consumers, and data classification explicit.
Use EventBridge when routing meaningful events reduces coupling. Use SQS when one consumer needs a durable work queue, SNS for straightforward fan-out, or a stream when ordering and retained high-throughput records are central requirements.
Go deeper with AWS
Read the primary AWS documentation behind the service definitions and architecture guidance in this guide.
Next steps
Continue with the concepts that most directly shape this decision.
What is event-driven architecture?
Learn how producers, routers, and consumers communicate through events, and how to design schemas, delivery, retries, and ownership deliberately.
What are serverless workflows?
Learn when explicit workflow state improves retries, branching, parallel work, human approval, visibility, and recovery in distributed applications.
What is Amazon SNS?
Understand SNS topics, publish-and-subscribe fanout, subscription filtering, delivery endpoints, and durable queue-based consumers.
Event delivery and idempotency
Design safe event consumers around at-least-once delivery, duplicate messages, ordering boundaries, deduplication records, and transactional side effects.
Questions about this topic
Browse all serverless concepts
Explore compute, APIs, events, workflows, data, security, reliability, operations, delivery, and AI from one connected AWS serverless learning path.
What is serverless?
Learn what serverless computing means, how it works on AWS, what the cloud provider manages, and which trade-offs still belong to your team.
What is AWS Lambda?
Understand how AWS Lambda runs code, how functions are invoked, where permissions and state live, and when Lambda is a good compute choice.
What is serverless architecture?
Learn how managed compute, APIs, events, queues, workflows, data, identity, and observability fit together in a serverless architecture on AWS.
AWS serverless security
A practical guide to identity, least privilege, event validation, secrets, data protection, dependencies, and incident visibility in AWS serverless systems.
What is agentic AI?
Learn what makes an AI system agentic, how models, tools, memory, orchestration, identity, and evaluation fit together, and where serverless patterns help on AWS.
What is cloud computing?
Understand how on-demand infrastructure and managed services change the way teams provision, scale, pay for, and operate software systems.
What is event-driven architecture?
Learn how producers, routers, and consumers communicate through events, and how to design schemas, delivery, retries, and ownership deliberately.
What is a serverless API?
Understand the request path, authentication, routing, compute, data, throttling, observability, and failure controls behind a serverless API on AWS.
What are serverless workflows?
Learn when explicit workflow state improves retries, branching, parallel work, human approval, visibility, and recovery in distributed applications.
What is Amazon API Gateway?
Learn how API Gateway creates, publishes, secures, monitors, and operates HTTP, REST, and WebSocket APIs for AWS and external backends.
What is Amazon EventBridge?
Understand EventBridge event buses, rules, pipes, schemas, targets, schedules, permissions, delivery, and recovery in event-driven AWS systems.
Make the next serverless decision explicit.
Explore focused products for repeatable work, or bring the architecture decision that needs context and experienced review.