Query AWS CloudWatch metrics for ECS/EC2/RDS and return charts.
Scanned 9/7/2026
Install to Claude Code
npx -y skills add modbender/skill-library-mcp --skill aws-cloud-watch --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Aws Cloud Watch?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/modbender-aws-cloud-watch)More formats (shields.io, HTML) on the badges page.
---
name: aws-cloud-watch
description: Query AWS CloudWatch metrics for ECS/EC2/RDS and return charts.
---
# AWS CloudWatch Skill
Use this skill to fetch CloudWatch metrics for ECS / EC2 / RDS and return text summaries.
## Entry
Preferred entry script:
```
node {baseDir}/src/skill.mjs --service ecs --metric cpu --resource <cluster-name> --hours 1
```
## Environment
Required (AK/SK):
- `AWS_ACCESS_KEY_ID`
- `AWS_SECRET_ACCESS_KEY`
Optional:
- `AWS_REGION` (default: `us-west-2`)
## Usage (internal)
Run the CLI script in `{baseDir}`:
```
node {baseDir}/src/cli.js --service ecs --metric CPUUtilization --resource <cluster-name-or-arn> --hours 1
node {baseDir}/src/cli.js --service ecs --metric cpu --resource <cluster-name>
```
You can define metric aliases in `{baseDir}/config.json` (see `config.example.json`).
### Supported services
- `ecs` (cluster-level metrics)
- `ec2`
- `rds`
### Defaults
- Region: `us-west-2`
- Period: 300 seconds (5 minutes)
- Time window: 1 hour
## Notes
- ECS metrics are cluster-level unless Container Insights is enabled.
- If the metric is unavailable, return a clear message.
- Text-only output (no chart rendering).
- Uses SigV4 signing via native crypto (no AWS SDK, no external packages).
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
Wire a service's OpenTelemetry output to Sematext Cloud. Walks through region, App-type, instrumentation flow (managed OTLP endpoint vs Sematext Agent), and signal selection (traces/metrics/logs), then produces the exact env-var block and points at a runnable reference example in this repo. Invoke when instrumenting a new app for Sematext.
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.