All Products
Search
Document Center

EventBridge:Manage custom event buses

更新時間:Sep 14, 2024

This topic describes how to create, view, and delete a custom event bus in the EventBridge console.

Prerequisites

Activate EventBridge and grant permissions to a RAM user

Create a custom event bus

  1. Log on to the EventBridge console. In the left-side navigation pane, click Event Buses.

  2. In the top navigation bar, select a region.

  3. On the Event Buses page, click Create in the Custom Event Buses section.

  4. Complete the Create Custom Event Bus wizard.

    1. In the Event Bus step, set the Name and Description parameters and click Next Step.

    2. Optional: In the Event Source step, configure the Event Source Name and Description parameters, select an event provider, configure resource information, and then click Next Step.

      If you do not want to create a custom event source, click Skip.

    3. Optional: In the Event Rule step, configure the Event Rule Name and Description parameters, specify an event pattern in the Pattern Content code editor, and then click Next Step.

      If you do not want to create an event rule or configure an event target, click Skip and then click OK in the Skip Subsequent Steps message.

    4. Optional: In the Event Target step, configure an event target and click Create.

      Important
      • You can configure up to five event targets for an event rule.

      • The event targets that you want to configure for an event rule must reside in the same region as the event rule.

      EventBridge supports the following event targets:

      • Function Compute: computes and processes events.

        For more information, see What is Function Compute?.

      • Message Queue for Apache RocketMQ: stores and forwards events.

        For more information, see What is Message Queue for Apache RocketMQ?

      • Message Queue for RabbitMQ: stores and forwards events.

        For more information, see What is Message Queue for RabbitMQ?

      • Message Service (MNS): stores events.

        For more information, see What is MNS?

      • EventBridge: filters and converts events.

        For more information, see What is EventBridge?

      • HTTP gateway: processes the business data of events.

      • HTTPS gateway: processes the business data of events.

      • Direct Mail: pushes events by using emails.

        For more information, see What is Direct Mail?

      • DingTalk: notifies you of events by using DingTalk messages.

      • ApsaraDB RDS for MySQL: stores and forwards events.

        For more information, see Overview of ApsaraDB RDS for MySQL.

      • Self-managed MySQL database: stores and forwards events.

      You can select an event transformation method as needed. For more information, see Event transformation.

      If you do not want to create an event rule or configure an event target, click Skip and then click OK in the Skip Subsequent Steps message.

View a custom event bus

  1. Log on to the EventBridge console. In the left-side navigation pane, click Event Buses.

  2. In the top navigation bar, select a region.

  3. On the Event Buses page, find the custom event bus that you want to view and click Details in the Actions column.

    The Overview page displays the basic information and endpoint information about the custom event bus.

Delete a custom event bus

You must delete all event sources and event rules created in a custom event bus before you delete the custom event bus. Otherwise, the custom event bus fails to be deleted.

  1. Log on to the EventBridge console.

  2. In the left-side navigation pane, click Event Buses.

  3. In the top navigation bar, select a region.

  4. On the Event Buses page, find the custom event bus that you want to delete and click Delete in the Actions column.

  5. Read the Note message and click OK.

  6. Optional: In the Verify Account Security dialog box, click Obtain Verification Code, enter the verification code in the Verification Code field, and then click OK.

    Warning

    After you delete a custom event bus, the data in the custom event bus cannot be restored.