AWS EventBridge Overview

What is Amazon EventBridge?

Amazon EventBridge is a new service that changed how we develop Serverless applications.

This service allow us to develop a fully event-driven application by connecting multiple services together - AWS services, custom services and third party services.

EventBridge was formerly called Amazon CloudWatch Events. Amazon CloudWatch Events and EventBridge are the same underlying service and API, however, EventBridge provides more features.

How it works

EventBridge delivers a stream of real-time data from AWS services, SaaS applications and your own applications to different types of targets without writing code.

The publisher sends a JSON event to an event bus, and to receive events, you create a rule. If the published event matches with a rule, the event is routed to up to five targets.

EventBridge is directly integrated with over 130 event sources and over 35 targets.

EventBridge Features

• Advanced event rules filtering
• Content-based event filtering
• API destinations
• Custom events
• Archive and replay events
• SaaS apps integration
• Schema registry
• Message transformation

EventBridge Building Blocks

Events

An event is a real-time change in a system, data, or environment. This change can be either in your application or in an AWS service or a SaaS partner service.

Event sources

An event source is used to ingest events from a SaaS partner, AWS Services, or your own applications.

Event buses

An event bus is a pipeline that receives events. Rules associated with the event bus evaluate events as they arrive. Each rule checks whether an event matches the rule’s criteria.

Event Bus Types:

1. Default event bus: Default bus created and receives events from any AWS service
2. Custom event bus: Receives events from custom applications you created and must be created manually
3. Partner event bus: Receives events from SaaS partner applications and must be created manually.

Rules

A rule matches incoming events and sends them to targets for processing. A single rule can send an event to multiple targets, which then run in parallel. Rules are based either on an event pattern or a schedule.

Targets

A target is a resource or endpoint that EventBridge sends an event to when the event matches the event pattern defined for a rule. The rule processes the event data and sends the pertinent information to the target. To deliver event data to a target, EventBridge needs permission to access the target resource. You can define up to five targets for each rule.