Dual-stack service endpoints in Amazon EventBridge - Amazon EventBridge
Considerations
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Dual-stack service endpoints in Amazon EventBridge

In addition to the IPv4 service endpoints, EventBridge also provides dual-stack endpoints for the following resources. You can access these endpoints using either IPv4 or IPv6 requests.

Resource Region endpoint FIPS endpoint Regions

Event buses

HTTPS://events.region-code.api.amazonwebservices.com.cn

Pipes

HTTPS://pipes.region-code.api.amazonwebservices.com.cn

Scheduler

HTTPS://scheduler.region-code.api.amazonwebservices.com.cn

Schemas

HTTPS://schemas.region-code.api.amazonwebservices.com.cn

To make a request to a dual-stack endpoint, you must use the mechanism provided by the tool or Amazon SDK to specify the endpoint. For more information, see Dual-stack and FIPS endpoints in the Amazon SDKs and Tools Reference Guide.

For example, the Amazon CLI provides the --endpoint-url option. The following example uses --endpoint-url to specify the dual-stack endpoint for event buses in the Beijing Region.

aws events describe-event-bus --region cn-north-1 --endpoint-url https://events.cn-north-1.api.amazonwebservices.com.cn

For a list of Region codes to use when specifying regional endpoints, see Regional endpoints in the Amazon General Reference.

Considerations when using dual-stack endpoints

Keep the following considerations in mind when using dual-stack endpoints to access EventBridge resources.

For event buses:

  • Dual-stack support for event buses includes archives and replays.

  • EventBridge does not currently support dual-stack endpoints for global endpoints.

    If you configure the Amazon SDK to use dual-stack endpoints, calls to PutEvents will result in an error. This is because the SDK uses the dual-stack domain (events.region-code.api.amazonwebservices.com.cn) rather than events.region-code.amazonwebservices.com.cn when constructing the endpoint, resulting in the request being sent to an endpoint that does not exist.

For EventBridge Pipes: