How do you use AWS EventBridge to integrate different event sources and targets?

1 Event sources and targets

EventBridge supports three types of event sources: AWS services, partner services, and custom applications. AWS services are the ones that generate events natively in EventBridge, such as EC2, S3, or Lambda. Partner services are the ones that integrate with EventBridge through SaaS connectors, such as Zendesk, PagerDuty, or Datadog. Custom applications are the ones that you create and send events to EventBridge using the PutEvents API or SDKs. EventBridge supports four types of event targets: AWS services, partner services, custom applications, and HTTP endpoints. You can use EventBridge to route events from any source to any target, based on rules and filters that you define.

2 Event buses and rules

EventBridge uses event buses to store and process events from different sources. An event bus is a logical entity that receives events from one or more sources and delivers them to one or more targets. You can use the default event bus, which receives events from AWS services and partner services, or create custom event buses, which receive events from custom applications. You can also create partner event buses, which receive events from partner services that require authorization. EventBridge uses rules to match events from an event bus to targets. A rule consists of a pattern, which defines the criteria for matching events, and a target list, which defines the destinations for the matched events. You can create rules using the EventBridge console, API, SDKs, or CloudFormation templates.

3 Event patterns and content-based filtering

EventBridge allows you to use event patterns to filter events based on their content. An event pattern is a JSON object that specifies the fields and values that an event must contain to match the rule. You can use event patterns to filter events by source, detail type, time, region, account, or any custom field in the event detail. You can also use advanced operators, such as prefix, numeric, or boolean, to refine your filters. For example, you can use an event pattern to match events from EC2 that have a detail type of EC2 Instance State-change Notification and a state of running.

4 Event transformation and enrichment

EventBridge allows you to transform and enrich events before sending them to targets. You can use input transformers to modify the event structure, add or remove fields, or insert values from other sources. For example, you can use an input transformer to add a timestamp or a correlation ID to an event. You can also use input paths to extract specific fields from an event and pass them to a target. For example, you can use an input path to pass only the instance ID and state from an EC2 event to a Lambda function. Additionally, you can use input templates to create a new event based on a template that references fields from the original event. For example, you can use an input template to create a Slack message that includes the event source and detail.

5 Event delivery and retry policies

EventBridge delivers events to targets asynchronously and reliably. EventBridge uses a delivery stream for each target, which ensures that events are delivered in order and without duplication. EventBridge also uses a dead-letter queue for each target, which stores events that failed to be delivered after a number of retries. You can configure the retry policy and the dead-letter queue for each target using the EventBridge console, API, SDKs, or CloudFormation templates. You can also monitor the delivery status and metrics of your events using CloudWatch.

6 Event security and access control

EventBridge allows you to secure and control access to your events and resources using IAM and resource policies. You can use IAM roles and policies to grant permissions to users, groups, and services to send or receive events from EventBridge. You can also use resource policies to grant permissions to external accounts or services to send or receive events from your event buses. For example, you can use a resource policy to allow a partner service to send events to your partner event bus. You can also use encryption to protect your events in transit and at rest using AWS KMS.