# eb-event-bus

Part of **EB**

# EventBridge Event Bus Management Console Guide

## Operations Overview

| Operation | Console Navigation Path | Prerequisites | Description |
|----------|------------------------|---------------|-------------|
| Create Event Bus | Console > EventBridge > Event Buses > Create Event Bus | - Active Alibaba Cloud account<br>- Permissions to create and manage event buses (e.g., EventBridgeFullAccess) | Create a new standard event bus with a unique name and region. |
| View Event Bus Details | Console > EventBridge > Event Buses > View Details | - Access to the EventBridge console<br>- Permissions to view event bus details | View detailed information about a system or custom event bus, including name, ARN, creation time, and description. |
| Create Custom Event Bus | Console > EventBridge > Custom Event Buses > Create Custom Event Bus | - EventBridge service enabled<br>- Required permissions<br>- Understanding of CloudEvents specification | Create a custom event bus for SaaS platforms like DingTalk or Cloud Tmall, or for custom application events. |
| Create RabbitMQ Custom Event Source | Console > EventBridge > Custom Event Sources > Create Custom Event Source | - ApsaraMQ for RabbitMQ instance, vhost, and queue created<br>- EventBridge activated with RAM permissions<br>- Custom event bus created | Add an ApsaraMQ for RabbitMQ queue as a custom event source to trigger events in EventBridge. |
| Create SMQ Event Source | Console > EventBridge > Event Buses > Event Sources > Add Event Source | - SMQ activated and queue created<br>- EventBridge activated with RAM permissions<br>- Custom event bus created | Configure a Simple Message Queue (SMQ) queue as a custom event source. |
| Add Simple Log Service as Event Source | Console > EventBridge > Custom Event Sources > Create Custom Event Source | - SLS Project and Logstore created<br>- EventBridge activated with RAM permissions<br>- Custom event bus created | Set up Simple Log Service (SLS) as a custom event source by selecting a Logstore and IAM role. |

## Step-by-Step Instructions

### Create Event Bus

**Navigation**: Console > EventBridge > Event Buses > Create Event Bus

**Prerequisites**:
- An active Alibaba Cloud account
- Permissions to create and manage event buses (e.g., EventBridgeFullAccess)

1. Click the **Create Event Bus** button  
   - Element: **Create Event Bus** (button) — top-right corner of the Event Buses page

2. Enter a unique name for the event bus  
   - Element: **Event Bus Name** (text_input) — main content area  
   - Notes: The name must be unique within the region and cannot contain special characters.

3. Select a region from the dropdown menu  
   - Element: **Region** (dropdown) — top-left corner

4. Click **Next: Configure Event Rules**  
   - Element: **Next: Configure Event Rules** (button) — bottom of the form  
   - Notes: This step allows you to define rules that route events to targets.

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Event Bus Name | text_input | Yes | — | A unique identifier for the event bus. Used to route events from sources. |
| Region | dropdown | Yes | China (Beijing), China (Shanghai), International (US East), International (EU Central) | The geographical region where the event bus will be created. |

### View Event Bus Details

**Navigation**: Console > EventBridge > Event Buses > View Details

**Prerequisites**:
- Access to the EventBridge console
- Permissions to view event bus details

1. Navigate to the EventBridge service in the console  
   - Element: **EventBridge** (link) — left navigation panel

2. Select the event bus type (system or custom) from the list  
   - Element: **System Event Buses / Custom Event Buses** (tab) — main content area

3. Click on the event bus name to view its details  
   - Element: **Event Bus Name** (link) — table row

4. Review the event bus details including name, Alibaba Cloud resource name, creation time, and description  
   - Element: **Details Panel** (text_input) — right side panel

### Create Custom Event Bus

**Navigation**: Console > EventBridge > Custom Event Buses > Create Custom Event Bus

**Prerequisites**:
- Access to Alibaba Cloud account with EventBridge service enabled
- Permissions to create and manage event buses and rules
- Understanding of CloudEvents specification

1. Click on **Create Custom Event Bus**  
   - Element: **Create Custom Event Bus** (button) — top-right corner of the Custom Event Buses page

2. Enter a name and description for the event bus  
   - Element: **Name** (text_input) — main content area  
   - Notes: The name must be unique within your account and region.

3. Select the SaaS platform integration type (DingTalk or Cloud Tmall)  
   - Element: **Integration Type** (dropdown) — form fields section  
   - Notes: This determines the default event sources and targets available.

4. Click **Create** to finalize the event bus setup  
   - Element: **Create** (button) — bottom of the form  
   - Notes: After creation, you can configure event rules and targets.

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Name | text_input | Yes | — | Unique identifier for the custom event bus. |
| Description | text_input | No | — | Optional description to help identify the purpose of the event bus. |
| Integration Type | dropdown | Yes | DingTalk, Cloud Tmall | Specifies the SaaS platform context for which this event bus is designed. |

### Create RabbitMQ Custom Event Source

**Navigation**: Console > EventBridge > Custom Event Sources > Create Custom Event Source

**Prerequisites**:
- An ApsaraMQ for RabbitMQ instance, vhost, and queue must be created
- EventBridge must be activated and RAM user permissions granted
- A custom event bus must be created

1. Click the **Create Custom Event Source** button  
   - Element: **Create Custom Event Source** (button) — top-right corner of the page

2. Configure parameters in the panel, select ApsaraMQ for RabbitMQ as the source type, and click **OK**  
   - Element: **OK** (button) — bottom of the configuration panel

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Name | text_input | Yes | — | The name of the custom event source. |
| Description | text_input | No | — | A description of the custom event source. |
| Region | dropdown | Yes | — | The region where the ApsaraMQ for RabbitMQ instance resides. |
| ApsaraMQ for RabbitMQ Instance | dropdown | Yes | — | The ApsaraMQ for RabbitMQ instance to use as the event source. |
| vhost | dropdown | Yes | — | The vhost within the ApsaraMQ for RabbitMQ instance. |
| Queue | dropdown | Yes | — | The queue within the selected vhost to monitor for events. |

### Create SMQ Event Source

**Navigation**: Console > EventBridge > Event Buses > Event Sources > Add Event Source

**Prerequisites**:
- SMQ activated and RAM users authorized to access SMQ
- An SMQ queue created
- EventBridge activated and RAM user granted permissions
- A custom event bus created

1. Log on to the EventBridge console  
   - Element: **EventBridge console** (link) — top navigation bar

2. Click **Event Buses** in the left-side navigation pane  
   - Element: **Event Buses** (menu) — left-side navigation panel

3. Select a region from the top navigation bar  
   - Element: **region dropdown** (dropdown) — top navigation bar

4. Click the name of the event bus to manage  
   - Element: **event bus name** (link) — Event Buses page

5. Click **Event Sources** in the left-side navigation pane  
   - Element: **Event Sources** (menu) — left-side navigation panel

6. Click **Add Event Source**  
   - Element: **Add Event Source** (button) — top-right corner

7. Configure event source parameters in the panel  
   - Element: **Add Event Source panel** (text_input) — main content area  
   - Notes: Enter name and description; select SMQ as type; choose target SMQ queue from dropdown

8. Click **OK** to confirm  
   - Element: **OK** (button) — bottom of form

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Name | text_input | Yes | — | Enter a name for the event source. |
| Description | text_input | No | — | Enter a description for the event source. |
| Type | dropdown | Yes | SMQ | Select the event source type. Choose SMQ from the list. |
| Queue | dropdown | Yes | — | Select the SMQ queue to use as the event source. |

### Add Simple Log Service as Event Source

**Navigation**: Console > EventBridge > Custom Event Sources > Create Custom Event Source

**Prerequisites**:
- Simple Log Service activated
- Project and Logstore created in SLS
- EventBridge activated with proper permissions
- Custom event bus created

1. Navigate to the EventBridge console and access the custom event sources section  
   - Element: **Create Custom Event Source** (button) — top-right corner of the EventBridge dashboard

2. Select the type of event source as Simple Log Service  
   - Element: **Select Source Type** (dropdown) — main content area

3. Enter a name for the event source and select the project and logstore from dropdowns  
   - Element: **Name** (text_input) — form fields section

4. Configure consumption position and select the role for EventBridge to assume  
   - Element: **Consume Position** (dropdown) — form fields section  
   - Notes: Options: earliest, latest, or specific time (UNIX timestamp)

5. Select the IAM role that EventBridge will use to read logs from SLS  
   - Element: **Role** (dropdown) — form fields section  
   - Notes: The selected role must have permissions to read logs and manage consumer groups in SLS.

6. Click **Confirm** to create the custom event source  
   - Element: **Confirm** (button) — bottom of the form  
   - Notes: A consumer group prefixed with 'eventbridge-' is automatically created in the Logstore.

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Name | text_input | Yes | — | The name of the custom event source. |
| Project | dropdown | Yes | — | Select the SLS Project that contains the Logstore. |
| Logstore | dropdown | Yes | — | Select the SLS Logstore to consume logs from. |
| Consume Position | dropdown | Yes | Earliest, Latest, Specific Time (UNIX timestamp) | The starting point for consuming logs. Can be earliest offset, latest offset, or a specific time. |
| Role | dropdown | Yes | — | The RAM role that EventBridge assumes to read logs from SLS and manage consumer groups. |

## FAQ

Q: Where can I find the list of all my event buses?
A: Go to the EventBridge console, then navigate to Event Buses. You can switch between System Event Buses and Custom Event Buses using the tabs.

Q: Can I change the region after creating an event bus?
A: No. The region is fixed at creation time and cannot be modified afterward.

Q: What happens if I leave the Description field empty when creating a custom event bus?
A: The Description field is optional. Leaving it empty will not affect functionality but may reduce clarity for team members managing the bus later.

Q: Do I need to create an event rule immediately after creating an event bus?
A: No. You can create event rules later by navigating to the event bus details and configuring rules under the Rules tab.

Q: What permissions are required to add an SLS event source?
A: The RAM role assigned during setup must have permissions to read logs from the specified Logstore and manage consumer groups in Simple Log Service.

## Pricing & Billing

### Billing Model
Billing is based on per-request usage. Each event processed (input or output) counts as one request.

### Price Reference
| Tier | Input Price | Output Price |
|------|-------------|--------------|
| Standard | 0.0001 / | 0.0001 / |

*Note: Some operations (e.g., custom application events) may have an output price of 0.0002 /.*

### Free Tier
- Monthly free allowance: 1,000 requests (for standard event bus creation and basic sources)
- Custom event buses for SaaS platforms: 100,000 free requests per month

### Billing Notes
- Events are billed per processing attempt, including both successful and failed deliveries.
- Minimum charge per consumption task is 1 request.
- Viewing event bus details is free and incurs no cost.
- Quota limits apply: up to 100 event buses per account, and maximum throughput of 10,000 events/second per bus.