Amazon EventBridge introduces Global endpoints for automatic failover and recovery
Amazon EventBridge now supports Global endpoints, a simpler and more reliable way for customers to improve the availability of their event-driven applications on AWS. Global endpoint is a new feature that makes it easier for customers to build robust and reliable applications by automatically failing over their event ingestion to a secondary region during service disruptions without the need for manual intervention. Customer can use replication to minimize the data at risk during these service disruptions.
Amazon EventBridge now supports Global endpoints, a simpler and more reliable way for customers to improve the availability of their event-driven applications on AWS. Global endpoint is a new feature that makes it easier for customers to build robust and reliable applications by automatically failing over their event ingestion to a secondary region during service disruptions without the need for manual intervention. Customer can use replication to minimize the data at risk during these service disruptions.
EventBridge is a Serverless event bus service that enables you to create scalable event-driven applications by routing events between your own applications, third-party SaaS applications, and other AWS services via built-in integrations. You can set up routing rules to determine where to send your data, allowing for applications to react to changes in your data and systems as they occur. Amazon EventBridge makes it easy to build event-driven applications because it takes care of event ingestion and delivery, security, authorization, and error handling.
With global endpoints, customers now have the flexibility to manage failures and configure failover criteria using CloudWatch Alarms (via Route53 health checks) to determine when to failover and route events back to the primary region. Once customers publish events to the global endpoint, the events are routed to the event bus in the primary region. If errors are detected in the primary region, a customer’s health check is marked as unhealthy and EventBridge routes incoming events to the secondary region.
You can get started in a few simple steps. First, you can choose your primary and secondary regions from the regions that global endpoints are available in (see below). Second, you can create an endpoint using the AWS Management Console or using the APIs. Third, you can archive your events in the secondary region to ensure none of your events are lost during a disruption. To recover quickly from disruptions, you can replicate your architecture in the secondary region to continue processing your events. Lastly, once the global endpoint is created, you can update your applications (by changing a single line of code) to publish events to the global endpoint.
Global endpoints are available at no additional charge. Today, global endpoints are available for custom events only and custom events published to the global endpoint are billed as per the custom events pricing. Customers are charged additionally for replication as per existing cross region pricing. To learn more, please visit the EventBridge pricing page.
Global endpoints are available in the following regions: US East (Ohio and N. Virginia), US West (Oregon and N. California), Canada (Central), EU (Stockholm, Paris, Ireland, Frankfurt, and London), Asia Pacific (Mumbai, Tokyo, Seoul, Singapore, Osaka, and Sydney), and South America (Sao Paulo). To learn more:
- Read Stephen Liedig’s blog post
- Read Amazon EventBridge Developer Guide
- Read our FAQ