AWS Services
Amazon EventBridge
Understand EventBridge as AWS event routing, including event buses, rules, event patterns, targets, Scheduler, Pipes, and SAA-C03 event architecture signals.
After this, you will understand
EventBridge is the event routing layer that helps services react to what happened without every producer knowing every consumer.
EventBridge receives events on an event bus, matches them with rules, and sends matching events to targets.
Learners use EventBridge like a queue, forget that rules match individual events, or confuse it with API Gateway request ingress.
Use EventBridge when producers emit business or AWS events and independent targets should react through filtering and routing.
Think before readingWhat is the core difference between EventBridge and SQS?
Reading in progress
This page is saved in your local study history so you can continue later.
Concepts Covered
- Event-driven architecture
- Event buses
- Events
- Rules
- Event patterns
- Targets
- Scheduled events
- EventBridge Scheduler
- EventBridge Pipes
- EventBridge versus SNS and SQS
1. Plain-English Mental Model
Amazon EventBridge is a serverless event routing service.
An event describes something that happened. It lands on an event bus. Rules inspect events using event patterns. When an event matches a rule, EventBridge sends it to one or more targets.
The simple model is:
event source -> event bus -> rule pattern -> target
Sources can be AWS services, your own applications, or SaaS partners. Targets can include Lambda, SQS, SNS, Step Functions, ECS tasks, API destinations, other event buses, and many more.
EventBridge is not a work queue. It is also not an API front door. It is an event routing layer.
2. Why This Service Exists
Modern systems often need to react to events without tightly coupling every producer to every consumer.
An order is placed. A payment is captured. An EC2 instance changes state. A deployment finishes. A SaaS provider emits a webhook. A nightly job should run. Multiple systems may care, but the producer should not need to know every target.
EventBridge exists to connect event producers and consumers through managed event buses, filtering, routing, schedules, and integrations.
For SAA-C03, EventBridge appears in questions about reacting to AWS service events, scheduled serverless tasks, decoupled event-driven architecture, SaaS integrations, event pattern filtering, routing to targets, and replacing custom polling or glue code.
The service often sits near Lambda, SQS, SNS, Step Functions, and CloudTrail.
3. The Naive Approach And Where It Breaks
The naive design has every producer call every consumer:
order service -> email service
order service -> analytics service
order service -> fulfillment service
This creates coupling. Adding a new consumer requires changing the producer. If a target changes protocol, the producer changes. If a target is down, the producer now owns retry logic.
Another naive design uses a scheduled Lambda with custom polling to check for AWS changes. Many AWS services already emit events that EventBridge can match.
Another mistake is using EventBridge as a queue for worker polling. EventBridge routes events to targets. If the target needs durable backlog and worker-controlled polling, use SQS as the target.
EventBridge is strongest when routing and filtering events is the core problem.
4. Core Primitives
An event is a JSON object describing something that happened. It has fields such as source, detail type, time, account, Region, resources, and detail.
An event bus receives events. The default bus receives many AWS service events. Custom buses are often used for application events. Partner buses can receive SaaS partner events.
A rule has an event pattern or schedule. Event patterns match event fields. A matching event is sent to rule targets.
A target is the destination for a matching event, such as Lambda, SQS, SNS, Step Functions, ECS task, API destination, or another event bus.
EventBridge Scheduler is a dedicated service for schedules at scale.
EventBridge Pipes connects a source to a target with optional filtering and enrichment.
5. Architecture Use Cases
Use EventBridge for application domain events:
order service -> custom event bus -> rules -> billing, email, analytics
Use EventBridge to react to AWS service events, such as EC2 state changes, CodePipeline state changes, or certain security findings.
Use Scheduler for cron-like or one-time scheduled tasks, such as running a Lambda or ECS task at a specific time.
Use EventBridge with SQS targets when each consumer needs a durable queue.
Use API destinations to route events to external HTTP APIs with managed authentication and retry behavior.
Use Pipes when you need point-to-point integration from sources such as SQS, Kinesis, or DynamoDB Streams to targets with filtering or enrichment.
7. Security Model
EventBridge access is controlled with IAM and resource policies.
Producers need permission to put events on a bus. Rules need permission to invoke targets, often through service roles or target resource policies.
Cross-account event buses require resource policies that allow the source account or organization.
Do not put sensitive data into broad events unless every matching target is authorized to receive it. Event routing can spread data.
Use event patterns to limit what reaches each target, but do not treat filtering as the only security boundary.
Monitor bus policies, rule changes, and target permissions because event routing can trigger powerful workflows.
8. Reliability And Resilience
EventBridge is managed, but target delivery can fail.
Configure retry policies and dead-letter queues for targets where supported. Use SQS targets when consumers need backlog and independent processing.
Rules evaluate events independently. They do not wait for multiple related events and combine them into a saga state unless you add stateful workflow logic elsewhere, such as Step Functions or a database-backed process manager.
EventBridge can decouple producers from consumers, but it does not guarantee every downstream workflow is correct. Consumers should be idempotent.
Use archives and replay when you need to replay past events for recovery or testing.
9. Performance And Scaling
EventBridge scales as a managed event routing service, but quotas, event size, and target capacity matter.
Rules with precise event patterns reduce unnecessary target invocations.
Fanout to many targets can multiply downstream load.
For high-throughput ordered streams, Kinesis may be a better fit. For worker backlogs, SQS may be a better fit. For simple broadcast notifications, SNS may be enough.
Use Pipes for integration patterns where filtering and enrichment can remove custom glue code.
Watch metrics for matched events, invocations, failed invocations, throttles, and DLQ depth.
10. Cost Model
EventBridge cost depends on published events, matched events, API destinations, archives, replay, Scheduler, Pipes, and data transfer depending on architecture.
Filtering can reduce downstream cost by avoiding unnecessary target invocation.
Archives and replay add cost but can be valuable for recovery and debugging.
Using EventBridge where SQS or SNS would be simpler may add unnecessary complexity and cost.
Using custom polling instead of events can waste compute and miss timely reactions.
12. SAA-C03 Exam Signals
"React to AWS service state changes" points to EventBridge.
"Serverless event bus" points to EventBridge.
"Route events based on event pattern" points to EventBridge rules.
"Run a task on a schedule" can point to EventBridge Scheduler or scheduled rules depending on wording.
"Connect SaaS events to AWS targets" points to EventBridge partner event sources.
"Durable queue for workers" points to SQS, often as an EventBridge target.
"Fan out simple notification to subscribers" may point to SNS.
13. Common Exam Traps
Do not use EventBridge as a replacement for a queue when consumers need polling and backlog.
Do not confuse API Gateway request ingress with EventBridge event routing.
Do not assume rules combine multiple events into stateful workflows.
Do not forget target permissions.
Do not send sensitive event payloads to broad buses without access design.
Do not ignore DLQs and retries for important targets.
15. Related Topics
Review Amazon API Gateway, AWS Lambda, Amazon SQS, and Amazon SNS.
Official AWS references:
What to study next
These links keep the session moving: read prerequisites first, then open the systems, concepts, and patterns that deepen this page.
Prerequisites
Read these first if the mechanics feel unfamiliar.
More Links
Additional references connected to this page.