tencent cloud

Event Bridge

Release Notes and Announcements
Release Notes
[July 19, 2024] Solution to CLS Billing Issues for EB Topics
User Tutorial
Product Introduction
Overview
Basic Concepts
Strengths
Use Cases
Limits
Purchase Guide
Billing Overview
Product Pricing
Overdue Payments and Service Suspension
Getting Started
Activating EventBridge
Quickly Delivering Custom Events
Quickly Configuring Cloud Monitor Event Alarm Push
Quickly Configuring Cloud Monitor Event Alarm Push
Event Source
Overview
Tencent Cloud Service Event Source
Event Structure
Connector
Event
Event Structure
Custom Event
Tencent Cloud Service Event
Event Bus
Overview
Creating Event Bus
Managing Event Bus
Linkage Tracing
Event Rule
Overview
Event Pattern
Creating Event Rule
Managing Event Rule
Configuring Data Conversion
Event Target
SCF Target
CLS Log Target
Message Push Target
CKafka Target
Practical Tutorial
Migrating Event Alarm
Real-Time Oceanus Alarm Message Push
Automatic Backup and Restart of Exceptional CVM Instance
Planning a EventBridge-based Midplatform for a Retail Business
API Documentation
History
Introduction
API Category
Making API Requests
Delivery Target APIs
Event Bus APIs
Event Rule APIs
Event Connector APIs
Data Transformer APIs
Event Storage APIs
Data Types
Error Codes
FAQs
Concept
Alarm
Billing
Contact Us
EB Policy
Privacy Policy
Data Processing And Security Agreement

Limits

PDF
Focus Mode
Font Size
Last updated: 2024-07-23 15:08:07
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.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback