Application Integration
Amazon EventBridge
Serverless service that connects components using events: it receives events from AWS services, your own applications, and third-party software, filters and transforms them, and delivers them to the appropriate targets. It includes EventBridge Scheduler for scheduling tasks with cron or rate expressions.
Exam phrases that point here
«automatically react when an AWS resource changes state»
Many AWS services send their events to the account's default event bus; a rule with an event pattern detects the change (for example, an EC2 instance moving to stopped) and triggers a target, with nothing for you to poll.
When not: If the requirement is to find out who made an API call for auditing, the answer points to AWS CloudTrail; if the reaction depends on a metric crossing a threshold, an Amazon CloudWatch alarm is a better fit.
«route events to different targets based on their content»
The rules on a classic bus (or the filters on each subscriber in the new Custom Event Bus) compare every event against a pattern on its fields and send only the matching ones to their target; a single event can reach several targets.
When not: If the core requirement is to fan out the same message to a very large number of subscribers, including email, SMS, or mobile push notifications, Amazon SNS is usually a better fit; if messages must be held until a consumer pulls them at its own pace, the key component is usually Amazon SQS.
«receive events from a third-party SaaS application without writing polling code»
SaaS partners integrated with EventBridge publish to a partner event source which, once associated with an event bus in your account, lets you apply rules to those events.
When not: If the provider is not an EventBridge partner, another ingestion mechanism is needed; and if the requirement is to transfer data in bulk from a SaaS application to a destination such as Amazon S3, the answer points to Amazon AppFlow.
«run a task on a schedule without managing servers»
EventBridge Scheduler (or, previously, scheduled rules) invokes an AWS target based on a cron, rate, or one-time expression, with configurable retries.
When not: EventBridge only triggers the task: the target does the work. If the question is about where a long-running process runs, the answer lies in compute (for example, AWS Batch or Amazon ECS), not in the scheduler.
«reprocess past events after fixing a bug»
On a classic bus, Archive and Replay stores events and resends them later. The new Custom Event Bus retains them for 1 to 365 days, and a subscriber can start reading from a point in the past. It is useful for debugging, recovering, or populating a new target.
When not: If it is real-time streaming data (clicks, telemetry) that several applications process and reread, Amazon Kinesis Data Streams is usually a better fit. Note that ordering and rereading alone no longer rule out EventBridge, because the new Custom Event Bus retains events and delivers them in order per group.
«connect a source to a single target, with filtering and enrichment, without integration code»
EventBridge Pipes connects a source (such as an SQS queue or a Kinesis or DynamoDB stream) to a target, with optional filtering and enrichment in between.
When not: If there are many sources and many targets, the pattern is an event bus, not a pipe; and if it is enough for AWS Lambda to read from a queue, the Lambda event source mapping already solves it.
Often paired with
- AWS Lambda
- AWS Step Functions
- Amazon SQS