Amazon EventBridge Documentation

Amazon EventBridge is a serverless event bus that makes it easier to build event-driven applications at scale using events generated from your applications, integrated Software-as-a-Service (SaaS) applications, and services of Amazon Web Services. EventBridge delivers a stream of data from event sources to targets like Amazon Lambda and other SaaS applications. You can set up routing rules to determine where to send your data to build application architectures that react to your data sources.

API Destinations is a feature for EventBridge that allows developers to send events back to many on-premises or software as a service (SaaS) applications with the ability to control throughput and authentication. Customers can configure rules with input transformations that will map the event’s format to the receiving service format.

Event Replay is a feature for Amazon EventBridge that allows customers to reprocess past events back to an event bus or a specific EventBridge rule. This feature helps developers debug their applications quickly, extend them by hydrating targets with historic events, and recover from errors.

The EventBridge schema registry stores event schema in a registry that other developers can search and access in your organization. The registry also allows you to generate code bindings for programming languages such as Java, Python, or TypeScript directly in your IDE so that the event can be used as an object in your code. Schemas for all services of Amazon Web Services are visible in your schema registry, and the schemas for integrated SaaS applications are visible when you turn on schema discovery for the SaaS partner event bus.

Amazon EventBridge is a serverless, managed, and scalable event bus that allows applications to communicate using events.

Amazon EventBridge is natively integrated with SaaS applications from many providers including Datadog, OneLogin, PagerDuty, Savyint, Segment, SignalFX, SugarCRM, Symantec, Whispir, and Zendesk, with additional integrations planned.

Amazon EventBridge is directly integrated with over 130 event sources and over 35 targets, including Amazon Lambda, Amazon SQS, Amazon SNS, Amazon Step Functions, Amazon Kinesis Data Streams, Amazon Kinesis Data Firehose, with additional sources and targets planned.

Amazon EventBridge makes it easier for you to build event-driven application architectures. Applications or microservices can publish events to the event bus without awareness of subscribers. Applications or microservices can subscribe to events without awareness of the publisher. You can also send events from your own applications to an event bus via the service’s PutEvents API. Other applications can then receive events through any of the many supported target services of Amazon Web Services.

You can filter events with rules. A rule matches incoming events for a given event bus and routes them to targets for processing. A single rule can route to multiple targets, all of which are processed in parallel. Rules allow different application components to look for and process the events that are of interest to them. A rule can customize an event before it is sent to the target by passing along only certain parts or by overwriting it with a constant. You can also have multiple rules that match on the same event, so different microservices or applications can choose to match events based on specific filters.

Amazon EventBridge provides at-least-once event delivery to targets, including retry with exponential backoff for up to 24 hours. Events are stored across multiple Availability Zones (AZs).

Amazon EventBridge extends its predecessor, Amazon CloudWatch Events, and provides a near- real time stream of system events that describe changes to your Amazon Web Services resources. It allows you to respond quickly to operational changes and take corrective action. You can write rules to indicate which events are of interest to your application and what automated actions to take when a rule matches an event.

You can set up scheduled events using the popular Unix cron syntax. Scheduled events are generated on a periodic basis and invoke any of the supported target services of Amazon Web Services.

You can monitor your event bus using Amazon CloudWatch metrics, such as the number of times an event matches a rule, or the number of times a target is invoked. You can use Amazon CloudWatch Logs to store, monitor, and analyze events that are triggered in your environment. Amazon CloudTrail allows you to monitor the calls made to the Amazon EventBridge API.

Amazon EventBridge integrates with Amazon Identity and Access Management (IAM) so that you can control which users and resources have permission to access your data and how they can access it.

For additional information about service controls, security features and functionalities, including, as applicable, information about storing, retrieving, modifying, restricting, and deleting data, please see https://docs.amazonaws.cn/en_us/. This additional information does not form part of the Documentation for purposes of the Sinnet Customer Agreement for Amazon Web Services (Beijing Region), Western Cloud Data Customer Agreement for Amazon Web Services (Ningxia Region) or other agreement between you and Sinnet or NWCD governing your use of services of Amazon Web Services China Regions.