How to Use EventBridge Open API Target for Automated Cloud Resource Management

Alibaba Cloud users generate massive events daily—resource CRUD operations, configuration changes, and application alerts. These events, produced by user actions or system detections, reflect the real‑time state of cloud resources and can be leveraged for valuable automation.

EventBridge serves as a serverless event hub that aggregates events from Alibaba Cloud services, custom applications, and SaaS solutions via the CloudEvents 1.0 protocol. Users can enable the built‑in cloud‑service‑specific bus to listen to events without provisioning extra resources.

To extend EventBridge’s capabilities, Alibaba Cloud recently introduced the open API target , which can invoke any cloud product’s OpenAPI in response to events. This turns EventBridge into a trigger that calls cloud service APIs for resource management, completing a closed‑loop workflow for event generation, processing, and action.

Event Bus Types

Cloud Service Dedicated Bus : An immutable, built‑in bus that receives events only from official Alibaba Cloud event sources.

Custom Event Bus : User‑created bus for custom or legacy events; users must create and manage it.

Both buses support the same rule engine, but the dedicated bus requires no setup and provides out‑of‑the‑box integration with dozens of Alibaba Cloud services.

Official Event Sources

EventBridge consolidates events from nearly all Alibaba Cloud products into a single official source, including Elastic Compute, Storage, Databases, Security, Big Data, AI, CDN, Video, Containers, Middleware, DevOps, IoT, and enterprise applications.

Event types are grouped into:

Operation audit events (API calls, console operations, platform‑initiated actions).

Configuration audit events (configuration changes, compliance violations).

Cloud monitoring events.

Collected events automatically available once the corresponding service is enabled.

Reference: https://help.aliyun.com/document_detail/182243.html

Open API Target Basics

The open API target requires five parameters:

Cloud service name

API version

API name

API parameter list (constants or jsonPath expressions)

Invocation role (a custom RAM role granted to EventBridge)

The role must have the minimal permissions needed to call the specified API.

Step‑by‑Step Example: Create a RocketMQ Topic

Prepare an HTTP source for testing.

Create a rule on the chosen event bus.

Enter rule name and description.

Select the prepared HTTP source as the event pattern.

Configure the target: choose RocketMQ, version 2019‑02‑14, API OnsGroupCreate, and fill required parameters (e.g.,

{"InstanceId":"MQ_INST_****_BXvPp0bx","GroupId":"GID_openAPITest"}

). Set the invocation role.

Save the rule.

Send the test payload to the HTTP source.

Verify in the RocketMQ console that the topic was created.

Code snippet for the test payload:

{
  "InstanceId": "MQ_INST_****_BXvPp0bx",
  "GroupId": "GID_openAPITest"
}

Best Practice: On‑Demand Snapshot Creation

Snapshots capture a point‑in‑time copy of an ECS disk, useful for disaster recovery or environment replication. Using EventBridge, users can create a rule that triggers an open API target to call the ECS snapshot API whenever a deployment event occurs, enabling automated, on‑demand snapshots without embedding ECS SDK calls in application code.

Test Environment Resource Management

For automated test setups, define three rules:

Resource initialization rule with two targets: an open API target to create a RocketMQ topic and a MySQL target to insert test data.

Resource cleanup rule mirroring the initialization rule but invoking delete APIs.

Test start rule that triggers a Function Compute service to launch the test workflow.

After creating these rules, sending an event to the appropriate rule progresses the test lifecycle automatically.

Operations Automation

Common operational scenarios—temporarily silencing alerts during releases, updating alert contacts on employee changes, and adding host monitoring for new services—can be automated by configuring EventBridge rules that invoke CloudMonitor (CMS) open APIs. This reduces manual steps and ensures consistent configuration across environments.

Overall, EventBridge’s open API target transforms event streams into actionable API calls, enabling low‑cost, serverless automation for cloud resource governance, testing, and operations.