# Amazon EventBridge limits and quotas

AWS limits and quotas · Updated 17 November 2026

**Short answer:** On a standard (rule-based) event bus you can have 300 rules per bus in most Regions (100 in Cape Town and Milan) and 5 targets per rule; rules are adjustable, targets are not. A PutEvents call takes up to 10 entries with a total size under 1 MB, and the PutEvents rate is a per-Region quota: 10,000 requests per second in us-east-1, us-west-2 and eu-west-1, and lower elsewhere. Matched events delivered to targets have a separate invocation throttle, which delays rather than drops events.

## Rule-based event bus quotas

These apply to the event bus that routes with rules and targets (the console now calls it **Custom Event Bus - Classic**; the default bus behaves the same way).

| Quota | Default | Adjustable |
|---|---|---|
| Rules per event bus | 300 (100 in af-south-1 and eu-south-1) | Yes |
| Targets per rule | 5 | No |
| Event buses per account | 100 | Yes |
| Event pattern size | 2,048 characters | Yes |
| Rules containing wildcards per bus | 30 | No |
| PutEvents rate | 10,000/s in us-east-1, us-west-2, eu-west-1; 2,400/s in us-east-2, eu-central-1; lower (down to 400/s) elsewhere | Yes |
| Invocations rate (events matched and sent to targets) | 18,750/s in the largest Regions, down to 750/s elsewhere | Yes |
| API destination invocations | 300/s per destination | Yes |
| API destinations / connections | 3,000 each | Yes |

The newer **Custom Event Bus** type (subscribers instead of rules) has its own quotas, prefixed `[EventsV2]` in Service Quotas, including 5 owned buses, 10,000 subscribers per bus and up to 100 entries per publish request. Check which kind of bus you are using before reading the numbers.

## Event size

For PutEvents, the sum of all entries in one request must be under 1 MB (1,048,576 bytes), and a single entry can use the full 1 MB if it is alone. A request carries at most 10 entries. Size is calculated from the entry's fields (`Time`, `Source`, `DetailType`, `Detail`, `Resources`), not the HTTP body, so JSON overhead counts. For anything larger, store the payload in S3 and put the object URL or key in the event. Older material quotes 256 KB; at the time of writing the documented limit is 1 MB.

## What happens at the limits

- **PutEvents throttled:** the call fails with `ThrottlingException`; SDKs retry with backoff. Partial failures are different: check `FailedEntryCount` in every response, because a 200 response can still contain failed entries.
- **Invocation throttle reached:** events are not lost; delivery to targets is delayed. Watch the `ThrottledRules` metric and target-side latency.
- **Target failures:** rule targets are retried for up to 24 hours and 185 attempts by default, configurable per target with a retry policy (0 to 185 attempts, 60 seconds to 24 hours event age). Add a dead-letter queue to each target so events that exhaust retries are kept.
- **Too many rules:** `PutRule` fails with `LimitExceededException`; consolidate patterns with prefix, numeric or `anything-but` matching, or split traffic across buses.

## Check usage

```
# Rules on a bus
aws events list-rules --event-bus-name orders --query 'length(Rules)'

# EventBridge quotas and codes in this Region
aws service-quotas list-service-quotas --service-code events \
  --query "Quotas[].[QuotaName,QuotaCode,Value]" --output table
```

CloudWatch metrics in `AWS/Events` worth an alarm: `ThrottledRules`, `FailedInvocations` and `InvocationsSentToDlq`.

## Design notes

- Five targets per rule is fixed. Fan out by pointing one target at an SNS topic or SQS queue, or create a second rule with the same pattern.
- Keep producers below the PutEvents quota by batching up to 10 entries per call.
- For scheduled jobs, EventBridge Scheduler has its own, separate quotas; its throttle metrics have [their own alarm guidance](https://cloudconsole.dev/alarms/eventbridge-scheduler-invocationthrottlecount).

## Questions

### How many targets can an EventBridge rule have?

Five per rule, and that quota can't be increased. Add more rules with the same pattern, or fan out through SNS or SQS.

### What is the maximum event size in EventBridge?

The total size of the entries in one PutEvents request must be under 1 MB, so a single event can be up to 1 MB.

### How many rules can an EventBridge event bus have?

300 per bus in most Regions by default (100 in Africa (Cape Town) and Europe (Milan)), adjustable through Service Quotas.

## When this happens away from your desk

EventBridge problems are quiet: events that don't match, or targets that silently fall behind. CloudConsole, a phone app for AWS, is being built to show failed-invocation and throttle alarms on your phone so quiet failures get noticed.

[About the CloudConsole app](https://cloudconsole.dev/aws-console-app) · [Download on the App Store](https://apps.apple.com/app/cloudconsole-for-aws/id6835419710)

## Sources

- [Amazon EventBridge quotas](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-quota.html)
- [Sending events with PutEvents (entry size)](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-putevents.html)
- [PutEvents (API reference)](https://docs.aws.amazon.com/eventbridge/latest/APIReference/API_PutEvents.html)

## Related

- [Amazon SNS limits and quotas](https://cloudconsole.dev/limits/sns-limits)
- [Amazon SQS limits and quotas](https://cloudconsole.dev/limits/sqs-limits)
- [AWS Step Functions limits and quotas](https://cloudconsole.dev/limits/step-functions-limits)
- [CloudWatch alarm: EventBridge Scheduler InvocationThrottleCount](https://cloudconsole.dev/alarms/eventbridge-scheduler-invocationthrottlecount)
- [ThrottlingException: Rate exceeded](https://cloudconsole.dev/errors/throttlingexception-rate-exceeded)
- [How to request an AWS service quota increase](https://cloudconsole.dev/limits/service-quotas-increase)

---

Source: https://cloudconsole.dev/limits/eventbridge-limits

CloudConsole is an independent iPhone and Android app for Amazon Web Services by Cloudconcur Ltd. It is not affiliated with Amazon Web Services.
