How to Use Alibaba Cloud OOS AI Assistant for Instant Ops via DingTalk

Background: Operations Challenges in the Mobile Era

In traditional operations, engineers rely on a computer to log into the console for resource management, but incidents can occur anywhere—during meetings, commuting, or late at night at home—making timely response difficult and risking business interruption.

Pain Points

Device limitation: No computer on hand, cannot log in.

Response delay: Need to wait for a colleague or find a temporary device, taking minutes to hours.

Complex operations: Using a mobile browser to log in is limited and cumbersome.

Solution

The Alibaba Cloud OOS AI Assistant is an intelligent operations tool based on natural‑language interaction. By sending text commands in a DingTalk group, users can query cloud resources, monitor, and perform operations without logging in, across devices, with second‑level response.

Real‑World Case: 10‑Minute Night‑Time Recovery

Time: 01:23 AM Location: Engineer Zhang Wei’s home

At 1:23 AM, Zhang Wei’s phone vibrated with an alert from DingTalk: "[Alibaba Cloud Monitoring] Beijing ECS memory usage 98% for 5 minutes" . He couldn’t find his computer, so he opened the DingTalk group and sent the command:

@AI Assistant restart Beijing ECS instance i-*******

The robot replied with a confirmation prompt:

"About to call ECS RestartInstance API to restart instance i-*******, confirm? (Y/N)"

Zhang entered “Y”. The operation completed automatically, and five minutes later the memory usage dropped to 30%, restoring the service.

How to Use OOS AI Assistant

Quick experience via OOS console: enable the “OOS AI Assistant” in the right‑hand menu.

Integrate the assistant into a DingTalk bot:

Enable login‑free operations: query, monitor, and act on resources directly from DingTalk.

Zero‑gap emergency response: handle incidents from any device.

Permission granularity: bind RAM roles to limit command scope.

Alert automation: cloud monitoring alerts are pushed to DingTalk and can trigger operations.

Configuration Steps

Create a DingTalk application (requires developer permissions).

Obtain the application’s Client ID and Client Secret.

Create a message card template in the DingTalk Card Platform and note its Template ID.

Grant the application Card.Streaming.Write and Card.Instance.Write permissions.

In the OOS console, create a ChatOps configuration for DingTalk, providing the Client ID, Client Secret, and Template ID, and bind a RAM role for OOS.

Copy the generated Webhook URL.

Configure the DingTalk bot to use the HTTP mode and set the Webhook URL as the message receiving address.

Publish the DingTalk application version.

Add the bot to a group and interact with it, e.g.:

@AI Assistant list running ECS instances in Hangzhou

The bot will automatically call Alibaba Cloud OpenAPI to return the requested information.

Applicable Scenarios & Value

Enables true “anytime, anywhere” operations, removing device and location constraints, improving incident response speed and business stability.

Precautions

Principle of least privilege: assign only necessary RAM permissions.

Two‑step confirmation for sensitive actions (e.g., delete, scale) to prevent accidental execution.

For any issues, join the DingTalk feedback group (QR code shown).

Related links: Alibaba Cloud OOS console, AppFlow connection flow, DingTalk developer permissions, DingTalk Open Platform, Card Platform, etc.