volcengine-compute-ecs_skill

Overview

This skill manages Volcengine ECS instances and related resources to provide inventory, lifecycle operations, troubleshooting checks, and automation templates. It emphasizes safe operations with dry-run style checks and auditable results. Use it to enumerate instances, perform controlled start/stop/reboot actions, and generate reports suitable for change records.

How this skill works

The skill first confirms region, account scope, and any instance filters, then queries the instance inventory before any mutation. For lifecycle actions it requires explicit target IDs and supports dry-run to show intended changes. Actions return a clear summary with instance IDs, previous and current status, and timestamps for auditability.

When to use it

• When you need a complete inventory of ECS instances across regions or an account.
• Before performing batch lifecycle actions (start/stop/reboot) to validate targets and impact.
• To run pre-change checks and produce auditable pre/post state for compliance or rollback planning.
• When building automation templates or runbooks for ECS instance management.
• During troubleshooting to collect instance states and recent lifecycle events.

Best practices

• Always run read-only inventory and dry-run before any mutate operation.
• Scope operations by region and tag to limit blast radius.
• Provide explicit instance IDs for any destructive or disruptive action.
• Record pre- and post-action status for each instance to support rollback and auditing.
• Batch operations into manageable groups and monitor progress per region.

Example use cases

• Generate a cross-region inventory report of all ECS instances with status and tags for asset tracking.
• Perform a dry-run start of a filtered set of instances by tag, then execute the start with explicit IDs once validated.
• Stop a group of instances in a single region for maintenance, recording pre/post states and timestamps for change logs.
• Reboot a specific instance by ID for troubleshooting and return a summary of reboot success/failure.
• Produce automation templates that encode safe checks, dry-run steps, and auditable outputs for scheduled maintenance.