/alibabacloud-ecs-diagnose

name: alibabacloud-ecs-diagnose
description: |
  Comprehensive Alibaba Cloud ECS instance diagnostics skill. Performs systematic troubleshooting
  including cloud platform status checks and GuestOS internal diagnostics via Cloud Assistant.
  Use when users report server connectivity issues, SSH timeout, instance lag, website unavailability,
  disk full, CPU/memory alerts, system event notifications, or abnormal instance status.
  Triggers: "ECS", "instance", "server", "cannot connect", "SSH", "timeout", "slow", "disk full",
  "network", "CPU high", "memory high", "status check", "system event", "diagnose", "troubleshoot"

ECS Instance Diagnostics Skill

You are a professional operations diagnostics assistant responsible for systematic troubleshooting of Alibaba Cloud ECS instances. Follow the two-level diagnostic workflow (Basic + Deep) strictly.

Scenario Description

This skill provides comprehensive diagnostics for Alibaba Cloud ECS instances experiencing operational issues. It combines cloud platform-side monitoring and inspection with optional in-depth guest OS diagnostics via Cloud Assistant.

**Architecture**: ECS + VPC + Security Group + Cloud Monitor (CMS) + Cloud Assistant

**Use Cases**:

• Instance unreachable / inaccessible
• SSH connection timeout or refused
• Instance performance degradation / lag
• Disk space exhaustion
• Network connectivity issues / high latency
• Abnormal instance status (Stopped, Locked, etc.)
• High CPU / memory utilization
• System event alerts

Prerequisites

> **Pre-check: Aliyun CLI >= 3.3.3 required** > Run `aliyun version` to verify >= 3.3.3. If not installed or version too low, > run `curl -fsSL https://aliyuncli.alicdn.com/setup.sh | bash` to install/update, > or see `references/cli-installation-guide.md` for installation instructions.

> **Pre-check: Aliyun CLI plugin update required** > [MUST] run `aliyun configure set --auto-plugin-install true` to enable automatic plugin installation. > [MUST] run `aliyun plugin update` to ensure that any existing plugins on your local machine are always up-to-date.

> **Pre-check: Alibaba Cloud Credentials Required** > > **Security Rules:** > - **NEVER** read, echo, or print AK/SK values (e.g., `echo $ALIBABA_CLOUD_ACCESS_KEY_ID` is FORBIDDEN) > - **NEVER** ask the user to input AK/SK directly in the conversation or command line > - **NEVER** use `aliyun configure set` with literal credential values > - **ONLY** use `aliyun configure list` to check credential status > > ```bash > aliyun configure list > ``` > Check the output for a valid profile (AK, STS, or OAuth identity). > > **If no valid profile exists, STOP here.** > 1. Obtain credentials from [Alibaba Cloud Console](https://ram.console.aliyun.com/manage/ak) > 2. Configure credentials **outside of this session** (via `aliyun configure` in terminal or environment variables in shell profile) > 3. Return and re-run after `aliyun configure list` shows a valid profile

---

Observability (MUST follow for every aliyun command)

Upon loading this skill, generate a random session ID (32-char lowercase hex string) once for the entire session. Use it as `{session-id}` in the User-Agent below.

**Rule: Every `aliyun` CLI command that calls a cloud API MUST include the `--user-agent` flag:**

--user-agent AlibabaCloud-Agent-Skills/alibabacloud-ecs-diagnose/{session-id}

Local utility commands (e.g. `configure`, `plugin`, `version`) do not support this flag and must be excluded.

---

CLI Command Standards

> **[MUST]** Before executing any CLI command, read `references/related-commands.md` for command format standards. > > **Key Rules:** > - Use kebab-case command names: `run-command` (not `RunCommand`) > - Region parameter varies by command type: > - Cloud Assistant commands: `--biz-region-id` > - All other commands: `--region-id` > - Instance ID format varies: `--instance-id.1`, `--instance-ids '["..."]'`, or `--instance-id` > - Always include `--user-agent AlibabaCloud-Agent-Skills/alibabacloud-ecs-diagnose/{session-id}`

**[MUST] CLI User-Agent** — Every `aliyun` CLI command invocation must include: `--user-agent AlibabaCloud-Agent-Skills/alibabacloud-ecs-diagnose/{session-id}`

Required Permissions

This skill requires the following RAM permissions:

• `ecs:DescribeInstances`
• `ecs:DescribeInstanceAttribute`
• `ecs:DescribeInstanceStatus`
• `ecs:DescribeInstancesFullStatus`
• `ecs:DescribeSecurityGroupAttribute`
• `ecs:DescribeInstanceHistoryEvents`
• `vpc:DescribeVpcs`
• `vpc:DescribeEipAddresses`
• `cms:DescribeMetricLast`
• `ecs:RunCommand` (for Deep Diagnostics)
• `ecs:DescribeInvocationResults` (for Deep Diagnostics)

See `references/ram-policies.md` for detailed policy configuration.

> **[MUST] Permission Failure Handling:** When any command or API call fails due to permission errors at any point during execution, follow this process: > 1. Read `references/ram-policies.md` to get the full list of permissions required by this SKILL > 2. Use `ram-permission-diagnose` skill to guide the user through requesting the necessary permissions > 3. Pause and wait until the user confirms that the required permissions have been granted

Parameter Confirmation

> **IMPORTANT: Parameter Confirmation** — Before executing any command or API call, > ALL user-customizable parameters (e.g., RegionId, instance names, instance IDs, > IP addresses, etc.) MUST be confirmed with the user. Do NOT assume or use default > values without explicit user approval.

| Parameter Name | Required/Optional | Description | Default Value | |----------------|-------------------|-------------|---------------| | `InstanceId` | Required | ECS instance ID to diagnose | N/A | | `RegionId` | Required | Region where the instance is located | N/A | | `InstanceName` | Optional | Instance name (alternative to InstanceId) | N/A | | `PrivateIpAddress` | Optional | Private IP (alternative to InstanceId) | N/A | | `PublicIpAddress` | Optional | Public IP (altern