Amazon EventBridge Documentation

EventBridge Pipes is a serverless integration resource that helps you build point-to-point integrations by providing a way to integrate event producers with event consumers without writing additional code. You can integrate with many AWS services. EventBridge Pipes has optional filtering, enrichment, and transformation capabilities. Learn more about EventBridge Pipes.

Amazon EventBridge Scheduler is a serverless scheduler that enables you to create, execute, and manage scheduled tasks at scale. You can schedule events and tasks that can invoke many AWS services as a target. EventBridge Scheduler provides a central location to manage your scheduled jobs across the cloud. Find out more about EventBridge Scheduler.

Global endpoints is a way that you can improve the availability of your event-driven applications on AWS. Global endpoint allows you to applications by failing over their event ingestion to a secondary Region during service disruptions, without manual intervention. Replication (optional) is available so that you can minimize the data at risk during these service disruptions. You also have the flexibility to configure failover criteria using Amazon CloudWatch Alarms (through Amazon Route 53 health checks) to determine when to failover and when to route events back to the primary Region. Get started in the console by providing a pre-populated stack for creating a CloudWatch Alarm and Route 53 health checks. Learn more in this blog post.

API Destinations is a feature for EventBridge that helps you send events back to many on-premises or software as a service (SaaS) applications with the ability to control throughput and authentication. You can send events to web-based applications that have a web address without writing custom code or using additional infrastructure. You can configure rules with input transformations that will map the event’s format to the receiving service format. Learn more in this blog post.

Event Replay is a new feature for EventBridge that helps you reprocess past events back to an event bus or a specific EventBridge rule. This feature helps you debug your applications quickly, extend them by hydrating targets with historic events, and recover from errors. Learn more in this blog post.

The EventBridge schema registry stores event schemas in a registry that other developers can search and access in your organization. Thus, you don’t have to find events and their structure manually. The registry also helps you generate code bindings for programming languages such as Java, Python, or TypeScript directly in your integrated development environment (IDE) so that the event can be used as an object in your code. By turning on schema discovery for an event bus, the schemas of events are discovered and added to the registry, without creating a schema for an event manually. Schemas for AWS 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. Learn more in this blog post.

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

Your AWS applications can take action based on events that SaaS applications generate. EventBridge is natively integrated with SaaS applications from many providers including Datadog, OneLogin, PagerDuty, Saviynt, Segment, SignalFx, SugarCRM, Symantec, Whispir, and Zendesk, with additional integrations planned.

EventBridge is directly integrated with over many event sources and targets, including AWS Lambda, Amazon Simple Queue Service (SQS), Amazon Simple Notification Service (SNS), AWS Step Functions, Amazon Kinesis Data Streams, and Amazon Kinesis Data Firehose, with additional sources and targets planned. All mutating API calls (all calls except Describe*, List*, and Get*) across AWS services generate events through AWS CloudTrail.

EventBridge allows 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 through the service’s PutEvents API. Other applications can then receive events through any of the many supported AWS target 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 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.

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).

EventBridge extends its predecessor, Amazon CloudWatch Events, and provides a near-real time stream of system events that describe changes to your AWS resources. It helps you to respond 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, for example, set a rule to invoke a Lambda function to remediate an issue or notify an Amazon SNS topic to alert an operator.

You can monitor your event bus using 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 initiated in your environment. CloudTrail helps you monitor calls made to the EventBridge API.

EventBridge integrates with AWS 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.thinkwithwp.com/index.html. This additional information does not form part of the Documentation for purposes of the AWS Customer Agreement available at http://thinkwithwp.com/agreement, or other agreement between you and AWS governing your use of AWS’s services.