- Release Notes and Announcements
- User Tutorial
- Product Introduction
- Purchase Guide
- Getting Started
- Event Source
- Event
- Event Bus
- Event Rule
- Event Target
- Best Practices
- API Documentation
- FAQs
- Contact Us
- EB Policy
- Release Notes and Announcements
- User Tutorial
- Product Introduction
- Purchase Guide
- Getting Started
- Event Source
- Event
- Event Bus
- Event Rule
- Event Target
- Best Practices
- API Documentation
- FAQs
- Contact Us
- EB Policy
EventBridge has certain quota limits for each user account. This document describes such quota limits.
Quota Limits
The quota limits for each user account are as follows:
Content | Default Quota Limit |
Maximum throughput of the PutEvents API per region | 5,000 TPS |
Maximum number of custom event buses per region | 10 |
Maximum number of rules that can be bound to a custom event bus | 10 |
Maximum number of rules that can be bound to a Tencent Cloud service event bus | 200 |
Maximum number of targets that can be configured in an event rule | 10 |
Maximum size of an event message body | 64 KB |
Maximum number of connectors supported by an event bus | 10 |
Maximum number of events delivered to a target | 2,000 events/day |
Note:
EventBridge currently supports 10,000-level concurrency, which can effectively support scenarios with high concurrency demand such as ecommerce promotions and parallel processing of medical and biological data. To request a quota increase, please submit a ticket.
You can specify the relevant limits by scopes such as region and event bus. To request a quota increase, please submit a ticket.
Rules and Limitations
Event bus
Event bus name: it can contain 2–60 letters, digits, underscores, and hyphens and must start with a letter and end with a digit or letter.
Event bus description: it can contain up to 200 characters of any type.
Event rule
Event rule name: it can contain 2–60 letters, digits, underscores, and hyphens and must start with a letter and end with a digit or letter.
Event rule description: it can contain up to 200 characters of any type.
Connector
Connector name: it can contain 2–60 letters, digits, underscores, and hyphens and must start with a letter and end with a digit or letter.
Deletion Exceptions
Event bus deletion: To delete an event bus, you need to delete all its trigger rules and connectors first; otherwise, the error message "An event rule/connector has been bound to this event bus. Please try again after deleting the bound event rule" will be displayed. After the event bus is deleted from the data flow, all corresponding resource information will also be deleted.
Event rule deletion: To delete an event rule, you need to delete all its targets first; otherwise, the error message "An event target has been bound to this event rule. Please try again after deleting the bound event target" will be displayed. After the event rule is deleted from the data flow, delivery of events related to the rule to the corresponding event bus will also stop.
Event target deletion: The component resources of the relevant delivery logic will be deleted from the data flow.
Connector deletion: The connector resources will be deleted from the data flow, and messages will no longer be delivered to the corresponding event bus.
Retrial upon Exceptions
EventBridge retries when the delivery of an event to a downstream target fails.
Yes
No
Was this page helpful?