Amazon EventBridge endpoints and quotas
The following are the service endpoints and service quotas for this service. To connect programmatically to an AWS service, you use an endpoint. In addition to the standard AWS endpoints, some AWS services offer FIPS endpoints in selected Regions. For more information, see AWS service endpoints. Service quotas, also referred to as limits, are the maximum number of service resources or operations for your AWS account. For more information, see AWS service quotas.
Service endpoints
| Region Name | Region | Endpoint | Protocol |
|---|---|---|---|
| US East (Ohio) | us-east-2 |
events.us-east-2.amazonaws.com events-fips.us-east-2.amazonaws.com |
HTTPS HTTPS |
| US East (N. Virginia) | us-east-1 |
events.us-east-1.amazonaws.com events-fips.us-east-1.amazonaws.com |
HTTPS HTTPS |
| US West (N. California) | us-west-1 |
events.us-west-1.amazonaws.com events-fips.us-west-1.amazonaws.com |
HTTPS HTTPS |
| US West (Oregon) | us-west-2 |
events.us-west-2.amazonaws.com events-fips.us-west-2.amazonaws.com |
HTTPS HTTPS |
| Africa (Cape Town) | af-south-1 | events.af-south-1.amazonaws.com | HTTPS |
| Asia Pacific (Hong Kong) | ap-east-1 | events.ap-east-1.amazonaws.com | HTTPS |
| Asia Pacific (Hyderabad) | ap-south-2 | events.ap-south-2.amazonaws.com | HTTPS |
| Asia Pacific (Jakarta) | ap-southeast-3 | events.ap-southeast-3.amazonaws.com | HTTPS |
| Asia Pacific (Malaysia) | ap-southeast-5 | events.ap-southeast-5.amazonaws.com | HTTPS |
| Asia Pacific (Melbourne) | ap-southeast-4 | events.ap-southeast-4.amazonaws.com | HTTPS |
| Asia Pacific (Mumbai) | ap-south-1 | events.ap-south-1.amazonaws.com | HTTPS |
| Asia Pacific (Osaka) | ap-northeast-3 | events.ap-northeast-3.amazonaws.com | HTTPS |
| Asia Pacific (Seoul) | ap-northeast-2 | events.ap-northeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Singapore) | ap-southeast-1 | events.ap-southeast-1.amazonaws.com | HTTPS |
| Asia Pacific (Sydney) | ap-southeast-2 | events.ap-southeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Tokyo) | ap-northeast-1 | events.ap-northeast-1.amazonaws.com | HTTPS |
| Canada (Central) | ca-central-1 | events.ca-central-1.amazonaws.com | HTTPS |
| Canada West (Calgary) | ca-west-1 | events.ca-west-1.amazonaws.com | HTTPS |
| Europe (Frankfurt) | eu-central-1 | events.eu-central-1.amazonaws.com | HTTPS |
| Europe (Ireland) | eu-west-1 | events.eu-west-1.amazonaws.com | HTTPS |
| Europe (London) | eu-west-2 | events.eu-west-2.amazonaws.com | HTTPS |
| Europe (Milan) | eu-south-1 | events.eu-south-1.amazonaws.com | HTTPS |
| Europe (Paris) | eu-west-3 | events.eu-west-3.amazonaws.com | HTTPS |
| Europe (Spain) | eu-south-2 | events.eu-south-2.amazonaws.com | HTTPS |
| Europe (Stockholm) | eu-north-1 | events.eu-north-1.amazonaws.com | HTTPS |
| Europe (Zurich) | eu-central-2 | events.eu-central-2.amazonaws.com | HTTPS |
| Israel (Tel Aviv) | il-central-1 | events.il-central-1.amazonaws.com | HTTPS |
| Middle East (Bahrain) | me-south-1 | events.me-south-1.amazonaws.com | HTTPS |
| Middle East (UAE) | me-central-1 | events.me-central-1.amazonaws.com | HTTPS |
| South America (São Paulo) | sa-east-1 | events.sa-east-1.amazonaws.com | HTTPS |
| AWS GovCloud (US-East) | us-gov-east-1 | events.us-gov-east-1.amazonaws.com | HTTPS |
| AWS GovCloud (US-West) | us-gov-west-1 | events.us-gov-west-1.amazonaws.com | HTTPS |
Service quotas
| Name | Default | Adjustable | Description |
|---|---|---|---|
| Api destinations | Each supported Region: 3,000 |
Yes |
The maximum number of API destinations per account per Region. |
| Connections | Each supported Region: 3,000 |
Yes |
The maximum number of connections per account per Region. |
| CreateEndpoint throttle limit in transactions per second | Each supported Region: 5 per second | No | The maximum number of requests per second for CreateEndpoint API. Additional requests are throttled. |
| DeleteEndpoint throttle limit in transactions per second | Each supported Region: 5 per second | No | The maximum number of requests per second for DeleteEndpoint API. Additional requests are throttled. |
| Endpoints | Each supported Region: 100 |
Yes |
The maximum number of endpoints per account per Region. |
| Event bus policy size | Each supported Region: 10,240 |
Yes |
Maximum policy size, in characters. This policy size increases each time you grant access to another account. You can see your current policy and its size by using the DescribeEventBus API. |
| Event buses | Each supported Region: 100 |
Yes |
Maximum event buses per account. |
| Event pattern size | Each supported Region: 2,048 |
Yes |
Maximum size of an event pattern, in characters. |
| Invocations throttle limit in transactions per second |
us-east-1: 18,750 per second us-east-2: 4,500 per second us-west-1: 2,250 per second us-west-2: 18,750 per second af-south-1: 750 per second ap-northeast-1: 2,250 per second ap-northeast-3: 750 per second ap-southeast-1: 2,250 per second ap-southeast-2: 2,250 per second ap-southeast-3: 750 per second eu-central-1: 4,500 per second eu-south-1: 750 per second eu-west-1: 18,750 per second eu-west-2: 2,250 per second Each of the other supported Regions: 1,100 per second |
Yes |
An invocation is an event matching a rule and being sent on to the rules targets. After the limit is reached, the invocations are throttled; that is, they still happen but they are delayed. |
| Number of rules |
af-south-1: 100 eu-south-1: 100 Each of the other supported Regions: 300 |
Yes |
Maximum number of rules an account can have per event bus |
| PutEvents throttle limit in transactions per second |
us-east-1: 10,000 per second us-east-2: 2,400 per second us-west-1: 1,200 per second us-west-2: 10,000 per second af-south-1: 400 per second ap-northeast-1: 1,200 per second ap-northeast-3: 400 per second ap-southeast-1: 1,200 per second ap-southeast-2: 1,200 per second ap-southeast-3: 400 per second eu-central-1: 2,400 per second eu-south-1: 400 per second eu-west-1: 10,000 per second eu-west-2: 1,200 per second Each of the other supported Regions: 600 per second |
Yes |
Maximum number of requests per second for PutEvents API. Additional requests are throttled. |
| Rate of invocations per API destination | Each supported Region: 300 per second |
Yes |
The maximum number of invocations per second to send to each API destination endpoint per account per Region. Once the quota is met, future invocations to that API endpoint are throttled. The invocations will still occur, but are delayed. |
| Targets per rule | Each supported Region: 5 | No | Maximum number of targets that can be associated with a rule |
| Throttle limit in transactions per second for control plane APIs only, API name must be specified in the request (do not use for PutEvents) | Each supported Region: 50 per second |
Yes |
Maximum number of requests per second for EventBridge control plane API operations. Additional requests are throttled. The quota increase request should specify the API name (https://docs.aws.amazon.com/eventbridge/latest/APIReference/API_Operations.html) and the details on the use case. Should not be used for PutEvents |
| UpdateEndpoint throttle limit in transactions per second | Each supported Region: 5 per second | No | The maximum number of requests per second for UpdateEndpoint API. Additional requests are throttled. |
