The EventBridge schema registry stores event schema in a registry that can be easily searched and accessed by other developers in your organization, so you don’t have to manually find events and their structure. The registry also allows you to generate generate code bindings for programming languages such as Java, Python, or Typescript directly in your IDE, so 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 automatically discovered and added to the registry, removing the need to manually create a schema for an event. Schemas for all AWS services are automatically 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.
Fully managed and scalable event bus
Amazon EventBridge is a serverless, fully managed, and scalable event bus that allows applications to communicate using events. There is no infrastructure to manage and no capacity to provision.
Your AWS applications can take action based on events that SaaS applications generate. Amazon EventBridge is natively integrated with Software-as-a-service (SaaS) applications from many providers including Datadog, OneLogin, PagerDuty, Savyint, Segment, SignalFX, SugarCRM, Symantec, Whispir, and Zendesk, with additional integrations planned. You don’t need to manage any integration setup such as authentication or webhooks; events from your SaaS provider simply appear on your event bus.
Over 100 built-in event sources and targets
Amazon EventBridge is directly integrated with over 90 event sources and over 15 targets, including AWS Lambda, Amazon SQS, Amazon SNS, AWS Step Functions, Amazon Kinesis Data Streams, Amazon Kinesis Data Firehose, and more, with additional sources and targets planned. All mutating API calls (i.e., all calls except Describe*, List*, and Get*) across all AWS services generate events through AWS CloudTrail.
Send events from your own applications
You can use Amazon EventBridge as a centralized event bus for your enterprise applications and microservices. You can 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 AWS target services.
Decoupled event sources and targets
Amazon EventBridge makes it easy 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. This decoupling allows teams to work independently, leading to faster development and improved agility.
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.
Reliable event delivery
Amazon EventBridge provides at-least-once event delivery to targets, including retry with exponential backoff for up to 24 hours. Events are stored durably across multiple availability zones (AZs), providing additional assurance your events will be delivered to their destination. Amazon EventBridge also provides a 99.9% availability service level agreement (SLA), ensuring your applications are able to reliably access the service.
Automatic response to operational changes in AWS Services
Amazon 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 allows you to respond quickly to operational changes and take corrective action. You simply 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 an AWS Lambda function to remediate an issue, or notify an Amazon Simple Notification Service (SNS) topic to alert an operator.
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 AWS services.
Monitoring and auditing
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. AWS CloudTrail enables you to monitor the calls made to the Amazon EventBridge API.
Security and compliance
Amazon EventBridge is integrated 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. EventBridge supports VPC endpoints and encryption in transit using TLS 1.2. Amazon EventBridge is GDPR, SOC, ISO, DoD CC SRG, and FedRamp compliant and is also HIPAA-eligible.
Pay per event
Events generated by AWS services are free. You only pay for events generated by your own applications or SaaS applications (see pricing here).
Visit the Amazon EventBridge pricing page.
Get started building with Amazon EventBridge in the AWS Management Console.
Get a deeper understanding of EventBridge in the Developer Guide.