
Alicloud Compute Ecs Test
- 296 installs
- 396 repo stars
- Updated July 18, 2026
- cinience/alicloud-skills
alicloud-compute-ecs-test is an Alibaba Cloud agent skill that validates ECS deployments with health checks, smoke tests, failover scenarios, and infrastructure test harnesses for developers gating production release on
About
alicloud-compute-ecs-test is an agent skill in cinience/alicloud-skills that validates Alibaba Cloud ECS deployments before production release using health checks, smoke tests, failover scenarios, and infrastructure test harnesses. The skill guides agents through OpenAPI-driven workflows to confirm instance status, load balancer readiness, autoscaling behavior, and recovery paths after simulated failures so teams catch misconfigured security groups, stale AMIs, or broken startup scripts early. Developers reach for alicloud-compute-ecs-test when ECS-backed services need automated pre-release verification beyond manual console checks, especially before blue-green cutovers or region migrations. The skill follows the alicloud-skills pattern documented across the repository: confirm region and resource identifiers, discover required API parameters, execute calls via SDK or OpenAPI Explorer, and verify results with describe or list endpoints. Install through cinience/alicloud-skills so Claude Code or Cursor sessions produce repeatable ECS smoke and failover tests aligned with Alibaba Cloud RPC API conventions during ship-phase infrastructure QA.
- Staging ECS smoke and health checks
- Network and security group validation
- Autoscaling and failover test cases
- Image and deployment rollback drills
- CI-friendly infrastructure test patterns
Alicloud Compute Ecs Test by the numbers
- 296 all-time installs (skills.sh)
- Ranked #708 of 2,153 Testing & QA skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/cinience/alicloud-skills --skill alicloud-compute-ecs-testAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 296 |
|---|---|
| repo stars | ★ 396 |
| Last updated | July 18, 2026 |
| Repository | cinience/alicloud-skills ↗ |
How do you smoke test ECS before production release?
Validate ECS deployments with health checks, smoke tests, failover scenarios, and infrastructure test harnesses before production release on Alibaba Cloud.
Who is it for?
DevOps and backend engineers deploying services on Alibaba Cloud ECS who need agent-assisted smoke and failover tests before production cutover.
Skip if: Teams not running workloads on Alibaba Cloud ECS or developers provisioning brand-new VPC infrastructure who need Terraform authoring instead of release testing.
When should I use this skill?
User asks to smoke test ECS instances, validate Alibaba Cloud compute health checks, run failover scenarios, or gate ECS deploys with infrastructure tests.
What you get
ECS health check results, smoke test logs, failover scenario reports, and infrastructure test harness scripts for pre-release sign-off.
- ECS smoke test logs
- Failover scenario reports
- Infrastructure test harness scripts
Files
Category: service
Cloud Backup
Use Alibaba Cloud OpenAPI (RPC) with official SDKs or OpenAPI Explorer to manage resources for Cloud Backup.
Workflow
1) Confirm region, resource identifiers, and desired action. 2) Discover API list and required parameters (see references). 3) Call API with SDK or OpenAPI Explorer. 4) Verify results with describe/list APIs.
AccessKey priority (must follow)
1) Environment variables: ALIBABACLOUD_ACCESS_KEY_ID / ALIBABACLOUD_ACCESS_KEY_SECRET / ALIBABACLOUD_REGION_ID Region policy: ALIBABACLOUD_REGION_ID is an optional default. If unset, decide the most reasonable region for the task; if unclear, ask the user. 2) Shared config file: ~/.alibabacloud/credentials
API discovery
- Product code:
hbr - Default API version:
2017-09-08 - Use OpenAPI metadata endpoints to list APIs and get schemas (see references).
High-frequency operation patterns
1) Inventory/list: prefer List* / Describe* APIs to get current resources. 2) Change/configure: prefer Create* / Update* / Modify* / Set* APIs for mutations. 3) Status/troubleshoot: prefer Get* / Query* / Describe*Status APIs for diagnosis.
Minimal executable quickstart
Use metadata-first discovery before calling business APIs:
python scripts/list_openapi_meta_apis.pyOptional overrides:
python scripts/list_openapi_meta_apis.py --product-code <ProductCode> --version <Version>The script writes API inventory artifacts under the skill output directory.
Output policy
If you need to save responses or generated artifacts, write them under: output/aliyun-hbr-backup/
Validation
mkdir -p output/aliyun-hbr-backup
for f in skills/backup/aliyun-hbr-backup/scripts/*.py; do
python3 -m py_compile "$f"
done
echo "py_compile_ok" > output/aliyun-hbr-backup/validate.txtPass criteria: command exits 0 and output/aliyun-hbr-backup/validate.txt is generated.
Output And Evidence
- Save artifacts, command outputs, and API response summaries under
output/aliyun-hbr-backup/. - Include key parameters (region/resource id/time range) in evidence files for reproducibility.
Prerequisites
- Configure least-privilege Alibaba Cloud credentials before execution.
- Prefer environment variables:
ALIBABACLOUD_ACCESS_KEY_ID,ALIBABACLOUD_ACCESS_KEY_SECRET, optionalALIBABACLOUD_REGION_ID. - If region is unclear, ask the user before running mutating operations.
References
- Sources:
references/sources.md
interface:
display_name: "Alibaba Cloud Backup HBR"
short_description: "Cloud Backup vault and job workflows"
default_prompt: "Use $aliyun-hbr-backup to complete this backup task on Alibaba Cloud."
Sources
- OpenAPI product page:
https://api.aliyun.com/product/hbr - API list (metadata):
https://api.aliyun.com/meta/v1/products/hbr/versions/2017-09-08/api-docs.json - API definition (single API):
https://api.aliyun.com/meta/v1/products/hbr/versions/2017-09-08/apis/{ApiName}/api.json
#!/usr/bin/env python3
"""Fetch OpenAPI metadata API list for one product/version and save to output/.
Env:
- OPENAPI_META_TIMEOUT (seconds, default: 20)
"""
from __future__ import annotations
import argparse
import json
import os
import pathlib
import urllib.request
DEFAULT_PRODUCT_CODE = "hbr"
DEFAULT_VERSION = "2017-09-08"
OUTPUT_DIR = pathlib.Path("output/aliyun-hbr-backup")
def fetch_json(url: str, timeout: int) -> dict:
req = urllib.request.Request(url, headers={"User-Agent": "codex-skill"})
with urllib.request.urlopen(req, timeout=timeout) as resp:
return json.loads(resp.read().decode("utf-8"))
def main() -> None:
parser = argparse.ArgumentParser()
parser.add_argument("--product-code", default=DEFAULT_PRODUCT_CODE)
parser.add_argument("--version", default=DEFAULT_VERSION)
parser.add_argument("--output-dir", default=str(OUTPUT_DIR))
args = parser.parse_args()
timeout = int(os.getenv("OPENAPI_META_TIMEOUT", "20"))
output_dir = pathlib.Path(args.output_dir)
output_dir.mkdir(parents=True, exist_ok=True)
url = (
f"https://api.aliyun.com/meta/v1/products/{args.product_code}"
f"/versions/{args.version}/api-docs.json"
)
payload = fetch_json(url, timeout)
raw_apis = payload.get("apis", {})
if isinstance(raw_apis, dict):
api_names = sorted(raw_apis.keys())
elif isinstance(raw_apis, list):
names = []
for item in raw_apis:
if isinstance(item, dict):
name = item.get("name") or item.get("apiName")
if name:
names.append(name)
elif isinstance(item, str):
names.append(item)
api_names = sorted(set(names))
else:
api_names = []
json_file = output_dir / f"{args.product_code}_{args.version}_api_docs.json"
md_file = output_dir / f"{args.product_code}_{args.version}_api_list.md"
json_file.write_text(json.dumps(payload, ensure_ascii=False, indent=2), encoding="utf-8")
md_lines = [
f"# {args.product_code} {args.version} API List",
"",
f"- Source: {url}",
f"- API count: {len(api_names)}",
"",
]
md_lines.extend([f"- `{name}`" for name in api_names])
md_file.write_text("\n".join(md_lines) + "\n", encoding="utf-8")
print(f"Saved: {json_file}")
print(f"Saved: {md_file}")
if __name__ == "__main__":
main()
Related skills
FAQ
What does alicloud-compute-ecs-test verify?
alicloud-compute-ecs-test verifies ECS deployment readiness through health checks, smoke tests, and failover scenarios. The cinience skill uses Alibaba Cloud OpenAPI calls and describe or list endpoints to confirm instances and recovery behavior before production release.
When should teams run ECS infrastructure tests?
Teams should run ECS infrastructure tests before production cutover, region migrations, or autoscaling changes when manual console checks are insufficient to prove instance health and failover recovery on Alibaba Cloud.