Making applications Regional-fault tolerant with global endpoints and event replication - Amazon EventBridge

Making applications Regional-fault tolerant with global endpoints and event replication

You can improve your application's availability with Amazon EventBridge global endpoints. Global endpoints help make your application regional-fault tolerant at no additional cost. To start, you assign an Amazon Route 53 health check to the endpoint. When failover is initiated, the health check reports an “unhealthy” state. Within minutes of failover initiation, all custom events are routed to an event bus in the secondary Region and are processed by that event bus. Once the health check reports a “healthy” state, events are processed by the event bus in the primary Region.

When you use global endpoints, you can enable event replication. Event replication sends all custom events to the event buses in the primary and secondary Regions using managed rules.


If you're using custom buses, you'll need a custom bus in each Region with the same name and in the same account for failover to work properly.

Recovery Time & Recovery Point Objectives

The Recovery Time Objective (RTO) is the time that it takes for the secondary Region to start receiving events after a failure. For RTO, the time includes time period for triggering CloudWatch alarms and updating statuses for Route 53 health checks. The Recovery Point Objective (RPO) is the measure of the data that will be left unprocessed during a failure. For RPO, the time includes events that are not replicated to the secondary Region and are stuck in the primary Region until the service or Region recovers. With global endpoints, if you follow our prescriptive guidance for alarm configuration, you can expect the RTO and RPO to be 360 seconds with a maximum of 420 seconds.

Event replication

Events are processed in the secondary Region asynchronously. This means that events are not guaranteed to be processed at the same time in both Regions. When failover is triggered, the events are processed by the secondary Region and will be processed by the primary Region when it’s available. Enabling event replication will increase your monthly costs. For more information, see Amazon EventBridge pricing

We recommend enabling event replication when setting up global endpoints for the following reasons:

  • Event replication helps you verify that your global endpoints are configured correctly. This helps to ensure that you’ll be covered in the event of failover.

  • Event replication is required to automatically recover from a failover event. If you don’t have event replication enabled, you’ll have to manually reset the Route 53 health check to “healthy” before events will go back to the primary Region.

Replicated event payload

The following is an example of a replicated event payload:


For region, the Region that the event was replicated from is listed.

{ "version": "0", "id": "a908baa3-65e5-ab77-367e-527c0e71bbc2", "detail-type": "Test", "source": "", "account": "0123456789", "time": "1900-01-01T00:00:00Z", "region": "us-east-1", "resources": [ "arn:aws:events:us-east-1:0123456789:endpoint/MyEndpoint" ], "detail": { "a": "b" } }

Create a global endpoint

Complete the following steps to set up a global endpoint:

  1. Make sure that you have matching event buses and rules in both the primary and secondary Region.

  2. Create a Route 53 health check to monitor your event buses. For assistance in creating your health check, choose New Health Check when creating your global endpoint.

  3. Create your global endpoint.

Once you have set up the Route 53 health check, you can create a global endpoint.

To create a global endpoint by using the console

  1. Open the Amazon EventBridge console at

  2. In the navigation pane, choose Global endpoints.

  3. Choose Create Endpoint.

  4. Enter a name and description for the endpoint.

  5. For Event bus in primary Region, choose the event bus you’d like the endpoint associated with.

  6. For Secondary Region, choose the Region you'd like to direct events to in the event of a failover.


    The Event bus in secondary Region is auto-filled and not editable.

  7. For Route 53 health check for triggering failover and recovery, choose the health check that the endpoint will monitor. If you don't already have a health check, choose New Health check to open the AWS CloudFormation console and create a health check using a CloudFormation template.


    Missing data will cause the health check to fail. If you only need to send events intermittently, consider using a longer MinimumEvaluationPeriod, or treat missing data as 'missing' instead of 'breaching'.

  8. (Optional) For Event replication do the following:

    1. Select Event replication enabled.

    2. For Execution role, choose whether to create a new AWS Identity and Access Management role or use an existing one. Do the following:

      • Choose Create a new role for this specific resource. Optionally, you can update the Role name to create a new role.

      • Choose Use existing role. Then, for Execution role, choose the desired role to use.

  9. Choose Create.

To create a global endpoint by using the API

To create a global endpoint using the EventBridge API, see CreateEndpoint in the Amazon EventBridge API Reference.

To create a global endpoint by using AWS CloudFormation

To create a global endpoint using the AWS CloudFormation API, see AWS::Events::Endpoints in the AWS CloudFormation User Guide.

Working with global endpoints by using an AWS SDK


Support for C++ is coming soon.

When using an AWS SDK to work with global endpoints, keep the following in mind:

  • You'll need to have the AWS Common Runtime (CRT) library installed for your specific SDK. If you don't have the CRT installed, you'll get an exception message indicating what needs to be installed. For more information, see the following:

  • Once you have created a global endpoint, you'll need to add the endpointId and EventBusName to any PutEvents calls that you use.

  • Global endpoints support Signature Version 4A. This version of SigV4 allows requests to be signed for multiple AWS Regions. This is useful in API operations that might result in data access from one of several Regions. When using the AWS SDK, you supply your credentials and the requests to global endpoints will use Signature Version 4A without additional configuration. For more information about SigV4A, see Signing AWS API requests in the AWS General Reference.

    If you request temporary credentials from the global AWS STS endpoint (, AWS STS vends credentials which, by default, do not support SigV4A. See Managing AWS STS in an AWS Region in the AWS Identity and Access Management User Guide for further information.

Available Regions

The following Regions support global endpoints:

  • US East (N. Virginia)

  • US East (Ohio)

  • US West (N. California)

  • US West (Oregon)

  • Canada (Central)

  • Europe (Frankfurt)

  • Europe (Ireland)

  • Europe (London)

  • Europe (Milan)

  • Europe (Paris)

  • Europe (Stockholm)

  • Asia Pacific (Mumbai)

  • Asia Pacific (Osaka)

  • Asia Pacific (Seoul)

  • Asia Pacific (Singapore)

  • Asia Pacific (Sydney)

  • Asia Pacific (Tokyo)

  • South America (São Paulo)