Amazon EventBridge

Amazon EventBridge is a serverless event bus service that receives, filters, and routes events from AWS services, custom applications, and supported SaaS partners to targets. It operates using event buses, rules with event patterns, and targets to deliver or invoke downstream consumers. It fits in architectures as the central event router for decoupled, event-driven integrations and workflow triggers.

🗂 Resource Category

Application Integration

🧠 Exam Memory Hook

Think: "Event bus + rule-based routing + SaaS ingestion = Amazon EventBridge"

📖 Ownership

Classification: AWS Managed Service

AWS responsibilities: AWS operates, secures, scales, and patches the underlying service infrastructure and managed runtime platform that implements the event bus, rule engine, delivery subsystem, schema registry, and archive/replay components. AWS is responsible for the availability of the managed control plane, service APIs, telemetry for the service itself, and the physical infrastructure that hosts EventBridge.

Customer responsibilities: The customer configures event buses, rules, event patterns, targets, input transformers, access control policies (IAM), event schemas, archives, and replay settings; secures who can put or consume events by configuring IAM and resource policies; monitors event flow, delivery failures, and target health; and implements retries, DLQs, and application-level idempotency in target consumers.

Patching responsibilities: AWS patches and maintains the physical infrastructure, hypervisor, operating system, and the managed runtime and service platform that runs EventBridge components. The customer is responsible for patching and maintaining any guest operating systems, container images, runtimes, libraries, dependencies, and applications that run in their targets (for example Lambda functions, EC2 instances, or containers) and for patching any code used to produce or consume events.

🏗 Typical Architecture

💡 Top 5 Features

Rule-based filtering and routing using event patterns to deliver events to one or more targets.
Schema registry and discovery for typed event schemas and code generation support.
SaaS partner event ingestion and partner event buses to receive events from supported external SaaS providers.
Event archive and replay capability to store events and replay them to targets for reprocessing.
Support for scheduled rules to trigger events on cron or rate-based schedules.

✅ Top 5 Use Cases

Decoupling microservices by routing domain events from producers to multiple asynchronous consumers without custom broker infrastructure.
Ingesting and routing events provided by supported SaaS applications into AWS targets for downstream processing and automation.
Driving serverless workflows where events trigger Lambda functions, Step Functions, or other targets to implement processing pipelines.
Implementing operational or security alert routing by forwarding events from AWS services or monitoring pipelines to queues, notification systems, or automation targets.
Replaying historical events from archives to reprocess data or recover processing after a consumer outage.

🏗 Architecture Placement

Amazon EventBridge typically sits as a regional, account-level event bus that receives events from AWS services, custom applications, and supported SaaS partners, then routes those events to configured targets such as Lambda, SQS, SNS, Step Functions, or HTTP endpoints. Producers PUT events to the bus or use integrated service event sources; rules inspect events and deliver them to targets. Cross-account or cross-region patterns are possible when configured, and the service is commonly used as the central router in event-driven architectures.

🎯 Commonly Used With

- AWS Lambda
- Amazon SQS
- Amazon SNS
- AWS Step Functions
- AWS Identity and Access Management

🌍 5 Real-World Examples

Retail: An e-commerce platform publishes order events to EventBridge so fulfillment Lambda functions, inventory update queues, and notification systems consume decoupled events for parallel processing.
Financial services: A payments pipeline routes transaction events to analytics consumers and fraud-detection workflows to enable asynchronous analysis and alerting without tight coupling.
Healthcare: Device telemetry events are ingested into EventBridge and routed to processing Lambdas and durable queues for validation, enrichment, and downstream storage.
Media: An ingestion system emits file-arrival events that EventBridge forwards to Step Functions to orchestrate transcoding, metadata extraction, and distribution workflows.
Logistics: Tracking updates are published to an event bus and routed to multiple consumers for routing optimization, ETA calculation, and customer notifications.

🎓 AWS Exam Clues

Choose EventBridge when requirements call for a managed event bus with rule-based filtering and multiple asynchronous targets.
Look for explicit mention of SaaS partner or partner event sources when EventBridge is likely the right service.
Consider EventBridge for use cases needing scheduled (cron) triggers and unified event routing across services and applications.
Check for IAM resource policies and cross-account event delivery requirements, which indicate EventBridge bus and permission configuration is required.
Evaluate operational considerations such as target retry behavior, DLQ configuration, monitoring of failed deliveries, and consumer idempotency when selecting EventBridge.

📝 Quick Revision

Amazon EventBridge is a serverless event bus for receiving, filtering, and routing events from AWS services, custom apps, and supported SaaS partners. Use it to decouple producers and consumers, but plan for IAM, monitoring, retry/DLQ handling, and consumer scaling and idempotency in production.

🏷 Keywords

event bus • event pattern • rule • target • partner event bus • schema registry • schema discovery • event archive • replay • scheduled rule • input transformer • dead-letter queue