CSAS Device Health Monitor

This skill performs only read-only CSAS API calls. A fleet scan may write a local resume file; it never alters CSAS devices.

Prerequisites

• Aliyun CLI version 3.3.3 or later and jq 1.6 or later are required. Check with aliyun version and jq --version.
• For first installation or a major CLI upgrade, use /bin/bash -c "$(curl -fsSL --connect-timeout 10 --max-time 120 https://aliyuncli.alicdn.com/setup.sh)". For routine updates on CLI 3.3.5 or later, use aliyun upgrade.
• Before the first CSAS call, the script checks for aliyun-cli-csas and, if needed, installs it non-interactively with aliyun plugin install --name aliyun-cli-csas < /dev/null. This prepares only a local CLI dependency; it does not modify global CLI configuration or any CSAS cloud resource.
• Verify only credential status with aliyun configure list. Do not read, print, enter, or embed credential values. If no valid profile is available, stop and have the user configure their identity outside this session.

Permissions and Confirmation

Read references/ram-policies.md before running the workflow. If a permission failure occurs, read that file, use the ram-permission-diagnose skill to request the listed permission, then pause until the user confirms it was granted.

Before a cloud call, confirm the device selector, region/profile context, lookback window, thresholds, scan limit, and any local resume path with the user.

Observability