/alibaba-cloud

name: alibaba-cloud
description: |
  Alibaba Cloud integration. Manage data, records, and automate workflows. Use when the user wants to interact with Alibaba Cloud data.
compatibility: Requires network access and a valid Membrane account (Free tier supported).
license: MIT
homepage: https://getmembrane.com
repository: https://github.com/membranedev/application-skills
metadata:
  author: membrane
  version: "1.0"
  categories: ""

Alibaba Cloud

Alibaba Cloud is a suite of cloud computing services, similar to AWS or Azure. It's used by businesses of all sizes for things like hosting websites, storing data, and running applications.

Official docs: https://www.alibabacloud.com/help/product

Alibaba Cloud Overview

• **Ecs Instance**
• **Disk**
• **Image**
• **Security Group**
• **Vpc**
• **VSwitch**
• **ApsaraDB RDS Instance**
• **ApsaraDB RDS Database**
• **ApsaraDB RDS Account**
• **ApsaraDB RDS Backup Policy**
• **ApsaraDB RDS Parameter**
• **ApsaraDB RDS Read Only Instance**
• **ApsaraDB RDS Temporary Instance**
• **ApsaraDB RDS Instance Replication**
• **ApsaraDB for Redis Instance**
• **ApsaraDB for Redis Account**
• **ApsaraDB for Redis Backup Policy**
• **ApsaraDB for Redis Node**
• **ApsaraDB for MongoDB Instance**
• **ApsaraDB for MongoDB Account**
• **ApsaraDB for MongoDB Backup Policy**
• **ApsaraDB for Lindorm Instance**
• **ApsaraDB for Lindorm Backup Policy**
• **ApsaraDB for Lindorm Data Disk**
• **ApsaraDB for Lindorm Instance Network Info**
• **ApsaraDB for Lindorm Node**
• **ApsaraDB for PolarDB Instance**
• **ApsaraDB for PolarDB Account**
• **ApsaraDB for PolarDB Backup Policy**
• **ApsaraDB for PolarDB Database**
• **ApsaraDB for PolarDB Global Database Network**
• **ApsaraDB for PolarDB Node**
• **ApsaraDB for PolarDB Read Only Instance**
• **ApsaraDB for PolarDB Serverless Instance**
• **Elastic Network Interface**
• **Load Balancer**
• **Listener**
• **Cdn Domain**
• **Oss Bucket**
• **Oss Object**
• **Cloud Firewall Instance**
• **Cloud Firewall Address Book**
• **Cloud Firewall Control Policy**
• **Cloud Firewall Vpc Firewall**
• **Container Service Kubernetes Cluster**
• **Container Service Kubernetes Node Pool**
• **Container Service Kubernetes Application**
• **Container Service Kubernetes Namespace**
• **Container Service Kubernetes Secret**
• **Container Service Kubernetes Service**
• **Resource Orchestration Service Stack**
• **Auto Scaling Group**
• **Domain**
• **Ddos Protection Plan**
• **Waf Instance**
• **Actiontrail Trail**

Use action names and parameters as needed.

Working with Alibaba Cloud

This skill uses the Membrane CLI to interact with Alibaba Cloud. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

npm install -g @membranehq/cli@latest

Authentication

membrane login --tenant --clientName=<agentType>

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

**Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

membrane login complete <code>

Add `--json` to any command for machine-readable JSON output.

**Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

Connecting to Alibaba Cloud

Use `membrane connection ensure` to find or create a connection by app URL or domain:

membrane connection ensure "https://www.alibabacloud.com/" --json

The user completes authentication in the browser. The output contains the new connection id.

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has `state: "READY"`, skip to **Step 2**.

1b. Wait for the connection to be ready

If the connection is in `BUILDING` state, poll until it's ready:

npx @membranehq/cli connection get <id> --wait --json

The `--wait` flag long-polls (up to `--timeout` seconds, default 30) until the state changes. Keep polling until `state` is no longer `BUILDING`.

The resulting state tells you what to do next:

• **`READY`** — connection is fully set up. Skip to **Step 2**.
• **`CLIENT_ACTION_REQUIRED`** — the user or agent needs to do something. The `clientAction` object describes the required action:
• `clientAction.type` — the kind of action needed:
• `"connect"` — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
• `"provide-input"` — more information is needed (e.g. which app to connect to).
• `clientAction.description` — human-readable explanation of what's needed.
• `clientAction.uiUrl` (optional) — URL to a pre-built UI where the user can complete the action. Show this to the user when present.
• `clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically.

After the user completes the action (e.g. authenticates in the browser), poll again with `membrane connection get <id> --json` to check if the state moved to `READY`.

• **`CONFIGURATION_ERROR`** or **`SETUP_FAILED`** — something went wrong. Check the `error` field for details.

Searching for actions

Search using a natural language description of what you want to do:

membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json

You should always search for actions in the context of a specific connection.

Each result includes `id`, `name`, `description`, `inputSchema` (what parameters the action accepts), and