← Back to Skills Marketplace
sdk-team

Alibabacloud Elasticsearch Instance Manage

by alibabacloud-skills-team · GitHub ↗ · v0.0.3 · MIT-0
cross-platform ⚠ suspicious
191
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install alibabacloud-elasticsearch-instance-manage
Description
Alibaba Cloud Elasticsearch Instance Management Skill. Use for creating, querying, listing, restarting, and upgrading/downgrading Elasticsearch instances on...
README (SKILL.md)

Elasticsearch Instance Management

Manage Alibaba Cloud Elasticsearch instances: create, describe, list, restart, upgrade/downgrade configuration, and query node information.

Architecture

Alibaba Cloud Elasticsearch Instance Management
├── createInstance     (Create Instance)
├── DescribeInstance   (Query Instance Details)
├── ListInstance       (List Instances)
├── ListAllNode        (Query Cluster Node Info)
├── RestartInstance    (Restart Instance)
└── UpdateInstance     (Upgrade/Downgrade Instance Configuration)

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 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 are always up-to-date.

aliyun version
aliyun configure set --auto-plugin-install true
aliyun plugin update

[MUST] CLI User-Agent — Every aliyun CLI command invocation must include: --user-agent AlibabaCloud-Agent-Skills/alibabacloud-elasticsearch-instance-manage

[MUST] AI-Mode — Before executing CLI commands, run:

  1. aliyun configure ai-mode enable
  2. aliyun configure ai-mode set-user-agent --user-agent "AlibabaCloud-Agent-Skills/alibabacloud-elasticsearch-instance-manage"

After all CLI operations complete, run: aliyun configure ai-mode disable


Authentication

Pre-check: Alibaba Cloud Credentials Required

Security Rules (MUST FOLLOW):

  • NEVER read, echo, or print AK/SK values
  • NEVER ask the user to input AK/SK directly in the conversation
  • NEVER use aliyun configure set with literal credential values
  • NEVER accept AK/SK provided directly by users in the conversation
  • ONLY read credentials from environment variables or pre-configured CLI profiles

⚠️ CRITICAL: Handling User-Provided Credentials

If a user attempts to provide AK/SK directly (e.g., "My AK is xxx, SK is yyy"):

  1. STOP immediately - Do NOT execute any command
  2. Reject the request politely with the following message:
    For your account security, please do not provide Alibaba Cloud AccessKey ID and AccessKey Secret directly in the conversation.
    
    Please use the following secure methods to configure credentials:
    
    Method 1: Interactive configuration via aliyun configure (Recommended)
        aliyun configure
        # Enter AK/SK as prompted, credentials will be securely stored in local config file
    
    Method 2: Configure via environment variables
        export ALIBABA_CLOUD_ACCESS_KEY_ID=\x3Cyour-access-key-id>
        export ALIBABA_CLOUD_ACCESS_KEY_SECRET=\x3Cyour-access-key-secret>
    
    After configuration, please retry your request.
    
  3. Do NOT proceed with any Alibaba Cloud operations until credentials are properly configured

Check CLI configuration:

   aliyun configure list

Check the output for a valid profile (AK, STS, or OAuth identity).

If no valid credentials exist, STOP here.


RAM Policy

Ensure the RAM user has the required permissions. See references/ram-policies.md for detailed policy configurations.

Minimum Required Permissions:

  • elasticsearch:CreateInstance
  • elasticsearch:DescribeInstance
  • elasticsearch:ListInstance
  • elasticsearch:ListAllNode
  • elasticsearch:RestartInstance
  • elasticsearch:UpdateInstance

Core Workflow

Note: Elasticsearch APIs use ROA (RESTful) style. You can use --body to specify the HTTP request body as a JSON string. See examples in each task below.

Idempotency: For write operations (create, restart, delete, etc.), you MUST use the --client-token parameter to ensure idempotency.

  • Use a UUID format unique identifier as clientToken
  • When a request times out or fails, you can safely retry with the same clientToken. When retrying after timeout, it is recommended to wait 10 seconds before retrying
  • Duplicate requests with the same clientToken will not execute the operation repeatedly
  • Generation method: Prefer using uuidgen or PowerShell GUID; if the environment doesn't support it, generate a UUID format string directly; if strict randomness is not required, use idem-timestamp-semantic-identifier as a fallback. Do not interrupt the process due to unavailable commands.

Task 1: Create Elasticsearch Instance

node-specifications-by-region.md Different roles in different regions support different specifications when creating instances, refer to this document.

⚠️ CRITICAL: Required Parameters and Region Validation

When creating an ES instance, parameters such as --region, esAdminPassword, vpcId, vswitchId, vsArea, paymentType MUST be explicitly provided by the user.

Important Notes:

  • The --region parameter MUST NOT be guessed or use default values
  • If the user does not provide a region or provides an invalid region, you MUST clearly prompt the user to provide a valid region

For detailed validation rules, refer to related-apis.md - createInstance Required Parameters and Region Validation

Method 2: Using --body to specify HTTP request body (RESTful style)

# Generate idempotency token first
CLIENT_TOKEN=$(uuidgen)

aliyun elasticsearch create-instance \
  --region \x3CRegionId> \
  --client-token $CLIENT_TOKEN \
  --body '{
    "esAdminPassword": "\x3CPassword>",
    "esVersion": "7.10_with_X-Pack",
    "nodeAmount": 2,
    "nodeSpec": {"disk": 20, "diskType": "cloud_ssd","spec": "elasticsearch.sn2ne.large.new"},
    "networkConfig": {"vpcId": "\x3CVpcId>","vswitchId": "\x3CVswitchId>", "vsArea": "\x3CZoneId>", "type": "vpc"},
    "paymentType": "postpaid",
    "description": "\x3CInstanceName>"
  }' \
  --connect-timeout 3 \
  --read-timeout 10 \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-elasticsearch-instance-manage

Example: Create Single Availability Zone Instance

# Generate idempotency token (use the same token when retrying after timeout)
CLIENT_TOKEN=$(uuidgen)

aliyun elasticsearch create-instance \
  --region cn-hangzhou \
  --client-token $CLIENT_TOKEN \
  --body '{
    "esAdminPassword": "YourPassword123!",
    "esVersion": "7.10_with_X-Pack",
    "nodeAmount": 2,
    "nodeSpec": {
      "disk": 20,
      "diskType": "cloud_ssd",
      "spec": "elasticsearch.sn2ne.large.new"
    },
    "networkConfig": {
      "vpcId": "vpc-bp1xxx",
      "vswitchId": "vsw-bp1xxx",
      "vsArea": "cn-hangzhou-i",
      "type": "vpc"
    },
    "paymentType": "postpaid",
    "description": "my-es-instance",
    "kibanaConfiguration": {
      "spec": "elasticsearch.sn1ne.large",
      "amount": 1,
      "disk": 0
    }
  }' \
  --connect-timeout 3 \
  --read-timeout 10 \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-elasticsearch-instance-manage

Example: Create Multi-Availability Zone Instance

  1. For multi-AZ instances, networkConfig.vswitchId only supports the primary availability zone vSwitch, and networkConfig.vsArea only supports the primary availability zone name. Nodes will be automatically distributed to different availability zones. Do not specify availability zones and vSwitches through zoneInfos when creating, let the cloud provider allocate automatically.
  2. Specify the number of availability zones through zoneCount. For multi-AZ instances, you must create master nodes.
# Generate idempotency token
CLIENT_TOKEN=$(uuidgen)

aliyun elasticsearch create-instance \
  --region cn-hangzhou \
  --client-token $CLIENT_TOKEN \
  --body '{
    "esAdminPassword": "YourPassword123!",
    "esVersion": "7.10_with_X-Pack",
    "nodeAmount": 2,
    "nodeSpec": {
      "disk": 20,
      "diskType": "cloud_ssd",
      "spec": "elasticsearch.sn2ne.large.new"
    },
    "networkConfig": {
      "vpcId": "vpc-bp1xxx", "vswitchId": "vsw-bp1xxx", "vsArea": "cn-hangzhou-i", "type": "vpc"
    },
    "paymentType": "postpaid",
    "description": "my-es-instance",
    "zoneCount": "2",
    "kibanaConfiguration": {
      "spec": "elasticsearch.sn1ne.large",
      "amount": 1
    },
    "masterConfiguration": {
      "amount": 3,
      "disk": 20,
      "diskType": "cloud_essd",
      "spec": "elasticsearch.sn2ne.xlarge"
    }
  }' \
  --connect-timeout 3 \
  --read-timeout 10 \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-elasticsearch-instance-manage

Error Handling

  1. When an error occurs indicating that order parameters do not meet validation conditions, it may be due to incorrect data node specifications. You should prompt the user to use the correct specifications and not guess on your own. Refer to the specifications document node-specifications-by-region.md

Task 2: Describe Instance Details

⚠️ Important: Required Parameters Must Be Provided by User When querying instance details, --region and --instance-id must be explicitly provided by the user. Do not guess the region. For detailed instructions, refer to related-apis.md - DescribeInstance Required Parameters

aliyun elasticsearch describe-instance \
  --region \x3CRegionId> \
  --instance-id \x3CInstanceId> \
  --connect-timeout 3 \
  --read-timeout 10 \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-elasticsearch-instance-manage

Task 3: List Instances

⚠️ Important: Required Parameters and Parameter Validation

aliyun elasticsearch list-instance \
  --region \x3CRegionId> \
  --page 1 \
  --size 10 \
  --connect-timeout 3 \
  --read-timeout 10 \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-elasticsearch-instance-manage

For detailed parameters, filter examples, and response format, refer to related-apis.md - ListInstance

Task 4: Restart Instance

⚠️ CRITICAL: Pre-restart Check Requirements

Before executing a restart operation, you must first query the instance status and confirm it is active: Pre-check Rules:

  • Only when the instance status is active can you execute the restart operation
  • If the instance status is abnormal (such as activating, inactive, invalid, etc.), restart operation is prohibited
  • If the instance status is abnormal, you should inform the user that the current status is not suitable for restart and recommend waiting for the instance to recover or contacting Alibaba Cloud technical support

Using --body to specify HTTP request body (RESTful style)

# Generate idempotency token
CLIENT_TOKEN=$(uuidgen)

aliyun elasticsearch restart-instance \
  --region \x3CRegionId> \
  --instance-id \x3CInstanceId> \
  --client-token $CLIENT_TOKEN \
  --body '\x3CJSON_BODY>' \
  --connect-timeout 3 \
  --read-timeout 10 \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-elasticsearch-instance-manage

Example (using --body):

# Generate idempotency token
CLIENT_TOKEN=$(uuidgen)

# Normal restart
aliyun elasticsearch restart-instance \
  --region cn-hangzhou \
  --instance-id es-cn-xxx**** \
  --client-token $CLIENT_TOKEN \
  --body '{"restartType":"instance"}' \
  --connect-timeout 3 \
  --read-timeout 10 \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-elasticsearch-instance-manage

# Force restart
aliyun elasticsearch restart-instance \
  --region cn-hangzhou \
  --instance-id es-cn-xxx**** \
  --client-token $CLIENT_TOKEN \
  --body '{"restartType":"instance","force":true}' \
  --connect-timeout 3 \
  --read-timeout 10 \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-elasticsearch-instance-manage

# Restart specific nodes
aliyun elasticsearch restart-instance \
  --region cn-hangzhou \
  --instance-id es-cn-xxx**** \
  --client-token $CLIENT_TOKEN \
  --body '{"restartType":"nodeIp","nodes":["10.0.XX.XX","10.0.XX.XX"]}' \
  --connect-timeout 3 \
  --read-timeout 10 \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-elasticsearch-instance-manage

Task 5: Update Instance Configuration (Upgrade/Downgrade)

⚠️ CRITICAL: Pre-update Check Requirements

Before executing an update operation, you must first query the instance status and confirm it is active:

  • Only when the instance status is active can you execute the update operation
  • If the instance status is abnormal (such as activating, inactive, invalid), update operation is prohibited
  • If the instance status is abnormal, inform the user that the current status is not suitable for configuration change and recommend waiting for the instance to recover

Important Constraints:

  • Each update call can only change one type of node (data node, dedicated master node, cold data node, coordinating node, Kibana node, or elastic node)
  • Upgrade: Cannot reduce storage size, storage type, node count, or spec CPU/memory
  • Downgrade: Cannot increase storage size, storage type, node count, or spec CPU/memory. The orderActionType query parameter MUST be set to downgrade. Cannot reduce node count via this API (use ShrinkNode instead). Force change and updateType are not supported for downgrade
  • Storage size reduction is not supported in either direction
  • Enabled nodes cannot be disabled

For detailed API usage, parameters, and examples, refer to related-apis.md - UpdateInstance

node-specifications-by-region.md Different roles in different regions support different specifications, refer to this document.

CLI Command (using --body for RESTful HTTP body):

# Generate idempotency token
CLIENT_TOKEN=$(uuidgen)

aliyun elasticsearch update-instance \
  --region \x3CRegionId> \
  --instance-id \x3CInstanceId> \
  --client-token $CLIENT_TOKEN \
  --body '\x3CJSON_BODY>' \
  --connect-timeout 3 \
  --read-timeout 30 \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-elasticsearch-instance-manage

Example: Upgrade data node spec

CLIENT_TOKEN=$(uuidgen)

aliyun elasticsearch update-instance \
  --region cn-hangzhou \
  --instance-id es-cn-xxx**** \
  --client-token $CLIENT_TOKEN \
  --body '{"nodeSpec":{"spec":"elasticsearch.sn2ne.xlarge.new"}}' \
  --connect-timeout 3 \
  --read-timeout 30 \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-elasticsearch-instance-manage

Example: Downgrade data node spec (must set orderActionType=downgrade)

CLIENT_TOKEN=$(uuidgen)

aliyun elasticsearch update-instance \
  --region cn-hangzhou \
  --instance-id es-cn-xxx**** \
  --client-token $CLIENT_TOKEN \
  --order-action-type downgrade \
  --body '{"nodeSpec":{"spec":"elasticsearch.sn2ne.large.new"}}' \
  --connect-timeout 3 \
  --read-timeout 30 \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-elasticsearch-instance-manage

Request Body Examples:

The following examples show the --body JSON for each common upgrade/downgrade scenario.

Note: Each call can only change one type of node. For data nodes, nodeAmount and nodeSpec are considered the same type and can be combined in one call.

# Scenario Request Body (--body)
1 Data node disk upgrade/downgrade {"nodeSpec":{"disk":40}}
2 Data node spec upgrade/downgrade {"nodeSpec":{"spec":"elasticsearch.sn2ne.xlarge.new"}}
3 Data node disk + spec together {"nodeSpec":{"spec":"elasticsearch.sn2ne.xlarge.new","disk":40}}
4 Data node count increase/decrease {"nodeAmount":4}
5 Data node count + disk + spec together {"nodeAmount":4,"nodeSpec":{"spec":"elasticsearch.sn2ne.xlarge.new","disk":40}}
6 Master node spec upgrade/downgrade {"masterConfiguration":{"spec":"elasticsearch.sn2ne.xlarge"}}
7 Kibana node spec change {"kibanaConfiguration":{"spec":"elasticsearch.sn1ne.large"}}
8 Coordinating node count + spec {"clientNodeConfiguration":{"amount":3,"spec":"elasticsearch.sn1ne.large"}}
9 Cold node count + disk + spec {"warmNodeConfiguration":{"amount":3,"spec":"elasticsearch.sn1ne.large","disk":500}}

Error Handling

  1. When an error occurs indicating order parameters do not meet validation conditions, it may be due to incorrect node specifications. Refer to node-specifications-by-region.md
  2. If the instance status is not active, prompt the user to wait for the instance to recover before retrying
  3. If attempting to change multiple node types at once, inform the user that only one node type can be changed per operation

Task 6: List All Nodes (Query Cluster Node Information)

aliyun elasticsearch list-all-node \
  --region \x3CRegionId> \
  --instance-id \x3CInstanceId> \
  --connect-timeout 3 \
  --read-timeout 10 \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-elasticsearch-instance-manage

Parameters:

Parameter Required Description
--instance-id Yes Instance ID
--extended No Whether to return node monitoring information, default true

Example:

# List all nodes with monitoring info
aliyun elasticsearch list-all-node \
  --region cn-hangzhou \
  --instance-id es-cn-xxx**** \
  --connect-timeout 3 \
  --read-timeout 10 \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-elasticsearch-instance-manage

# Query specific fields
aliyun elasticsearch list-all-node \
  --region cn-hangzhou \
  --instance-id es-cn-xxx**** \
  --cli-query "Result[].{Host:host,Type:nodeType,Health:health,CPU:cpuPercent,Heap:heapPercent,Disk:diskUsedPercent}" \
  --connect-timeout 3 \
  --read-timeout 10 \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-elasticsearch-instance-manage

Response Fields:

Field Description
host Node IP address
nodeType Node type: MASTER/WORKER/WORKER_WARM/COORDINATING/KIBANA
health Node health status: GREEN/YELLOW/RED/GRAY
cpuPercent CPU usage rate
heapPercent JVM memory usage rate
diskUsedPercent Disk usage rate
loadOneM One minute load
zoneId Availability zone where the node is located
port Node access port

Success Verification

See references/verification-method.md for detailed verification steps.

Quick Verification:

# Check instance status
aliyun elasticsearch describe-instance \
  --region cn-hangzhou \
  --instance-id es-cn-xxx**** \
  --cli-query "Result.status" \
  --connect-timeout 3 \
  --read-timeout 10 \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-elasticsearch-instance-manage

Expected status: active


Reference Links

Reference Description
related-apis.md API and CLI command details
ram-policies.md RAM permission policies
verification-method.md Verification steps
acceptance-criteria.md Correct/incorrect patterns
cli-installation-guide.md CLI installation guide
node-specifications-by-region.md Node specifications by region and role
Elasticsearch Product Page Official product page
Elasticsearch API Reference Official API reference
Usage Guidance
This skill appears to do what it claims (manage Alibaba Cloud Elasticsearch) but there are a few things to consider before installing or using it: - Credentials: The skill's docs expect the Aliyun CLI to find credentials via environment variables or CLI profiles (ALIBABA_CLOUD_ACCESS_KEY_ID, ALIBABA_CLOUD_ACCESS_KEY_SECRET, ALIBABA_CLOUD_PROFILE, STS tokens, or configured profiles). However, the registry metadata does not declare any required env variables — verify where and how you'll supply credentials and prefer a RAM user with least-privilege policies (resource-scoped policy recommended). - Installer risk: The guide recommends running a remote installer via 'curl ... | bash'. Even though the URL is an official Alibaba CDN, piping remote scripts to a shell is inherently risky. Prefer installing the CLI via package manager (brew/apt) or download+verify steps and check the installer contents before executing. - Auto-plugin-install and plugin updates: Enabling automatic plugin installation and updating will cause the CLI to fetch and run additional code. Only enable this if you trust the runtime environment and the plugin source; consider disabling auto-install in sensitive environments. - Operational caution: The skill requires high-impact permissions (create/update/delete operations). Use dedicated RAM users, scope permissions to the minimal resources/regions needed, and rotate keys or prefer temporary STS tokens or instance RAM roles. - Chat hygiene: The skill's instructions explicitly forbid pasting AK/SK into the conversation. Follow that guidance and configure credentials outside chat. If you need higher assurance, ask the publisher for: (1) explicit declaration of required environment variables in the registry metadata, (2) a signed/verified installer checksum for the CLI installer, and (3) confirmation that enabling AI-mode and auto-plugin-install is necessary and safe for your environment.
Capability Analysis
Type: OpenClaw Skill Name: alibabacloud-elasticsearch-instance-manage Version: 0.0.3 The skill bundle provides legitimate instructions and documentation for managing Alibaba Cloud Elasticsearch instances using the official Aliyun CLI. It includes strong security guardrails in SKILL.md and related-apis.md that explicitly instruct the AI agent to reject user-provided credentials (AK/SK) and never print them, which serves as a defense against credential theft. The use of an official installation script (aliyuncli.alicdn.com) and standard cloud management workflows aligns with the stated purpose without any signs of malicious intent or data exfiltration.
Capability Tags
cryptocan-make-purchasesrequires-oauth-tokenrequires-sensitive-credentials
Capability Assessment
Purpose & Capability
Name, description and all runtime instructions are about Alibaba Cloud Elasticsearch (create, describe, list, restart, update). The required operations and RAM permissions shown in the docs align with the stated purpose and are proportionate to instance management.
Instruction Scope
SKILL.md keeps runtime actions within the Elasticsearch management scope and enforces safe behaviors (do not echo AK/SK, require explicit user-supplied region/parameters, require client-token idempotency). It does, however, instruct running external installers (curl ... | bash) to install the Aliyun CLI and to enable auto-plugin-install and plugin update — actions that change the host environment and may pull plugins automatically. Those installer/plugin steps are outside pure API usage and increase risk; they are relevant to the skill's operation but should be treated cautiously.
Install Mechanism
The skill is instruction-only (no install spec in registry), but the docs recommend installing the Aliyun CLI and even provide a 'curl -fsSL https://aliyuncli.alicdn.com/setup.sh | bash' command. Although the URL points to an official Alibaba CDN domain, piping a remote script to bash is a high-risk pattern (download-and-exec). The doc also suggests auto-plugin-install and plugin updates which will cause the CLI to fetch and run plugins automatically — increasing attack surface if the runtime environment is not tightly controlled.
Credentials
The registry metadata declares no required environment variables or primary credential, but the SKILL.md and reference docs explicitly rely on standard Alibaba Cloud environment variables and CLI profiles (ALIBABA_CLOUD_ACCESS_KEY_ID, ALIBABA_CLOUD_ACCESS_KEY_SECRET, ALIBABA_CLOUD_SECURITY_TOKEN, ALIBABA_CLOUD_PROFILE, etc.). This mismatch (runtime expects credential sources but metadata does not declare them) is an inconsistency worth noting. The requested permissions (elasticsearch:CreateInstance, UpdateInstance, etc.) are appropriate for the stated tasks, but they are powerful and should be granted under least privilege (RAM user / resource-scoped policy).
Persistence & Privilege
The skill is not marked 'always: true' and does not request permanent system-wide presence. It asks agents to enable 'ai-mode' in the Aliyun CLI for the duration of operations and then disable it; this is a temporary change to CLI behavior rather than a platform-level privilege escalation. Autonomous invocation is allowed by default (not a unique concern here).
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install alibabacloud-elasticsearch-instance-manage
  3. After installation, invoke the skill by name or use /alibabacloud-elasticsearch-instance-manage
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.0.3
- Increased minimum required Aliyun CLI version to 3.3.3. - Added requirement to run `aliyun plugin update` and clarified plugin configuration steps. - Mandated inclusion of a custom User-Agent (`AlibabaCloud-Agent-Skills/alibabacloud-elasticsearch-instance-manage`) with all CLI commands. - Introduced new AI-Mode configuration steps using `aliyun configure ai-mode` before and after CLI operations. - Updated and clarified CLI installation, update, and prerequisite instructions for reliability.
v0.0.2
alibabacloud-elasticsearch-instance-manage v0.0.2 - Added support for upgrading and downgrading (scaling/resizing) Elasticsearch instance configurations. - Introduced the UpdateInstance operation for modifying instance resources. - Expanded triggers to include "upgrade ES", "downgrade ES", "scale ES", "resize ES". - Updated permissions requirements to include elasticsearch:UpdateInstance. - Revised documentation to describe new features and workflows.
v0.0.1
Alibaba Cloud Elasticsearch Instance Management Skill v0.0.1 - Initial release for managing Alibaba Cloud Elasticsearch instances. - Supports creation, description, listing, and restarting of ES instances. - Secure credential handling enforced; never accept AK/SK directly from users. - Detailed CLI usage examples and required parameter validations included. - Offers clear troubleshooting and user guidance for prerequisites and permissions.
Metadata
Slug alibabacloud-elasticsearch-instance-manage
Version 0.0.3
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 3
Frequently Asked Questions

What is Alibabacloud Elasticsearch Instance Manage?

Alibaba Cloud Elasticsearch Instance Management Skill. Use for creating, querying, listing, restarting, and upgrading/downgrading Elasticsearch instances on... It is an AI Agent Skill for Claude Code / OpenClaw, with 191 downloads so far.

How do I install Alibabacloud Elasticsearch Instance Manage?

Run "/install alibabacloud-elasticsearch-instance-manage" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Alibabacloud Elasticsearch Instance Manage free?

Yes, Alibabacloud Elasticsearch Instance Manage is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Alibabacloud Elasticsearch Instance Manage support?

Alibabacloud Elasticsearch Instance Manage is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Alibabacloud Elasticsearch Instance Manage?

It is built and maintained by alibabacloud-skills-team (@sdk-team); the current version is v0.0.3.

💬 Comments