aws-cloud-watch
Query AWS CloudWatch metrics for ECS/EC2/RDS and return charts.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install openclaw-skills-aws-cloud-watch
Repository
Skill path: skills/delbertheihei/aws-cloud-watch
Query AWS CloudWatch metrics for ECS/EC2/RDS and return charts.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: openclaw.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install aws-cloud-watch into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/openclaw/skills before adding aws-cloud-watch to shared team environments
- Use aws-cloud-watch for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
---
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).
---
## Skill Companion Files
> Additional files collected from the skill directory layout.
### README.md
```markdown
# OpenClaw AWS CloudWatch Skill (Node.js)
This skill queries CloudWatch metrics for ECS/EC2/RDS and returns text summaries.
## Setup
No npm install required (zero external dependencies).
## Environment
```bash
set AWS_ACCESS_KEY_ID=xxx
set AWS_SECRET_ACCESS_KEY=yyy
set AWS_REGION=us-west-2
```
## Config (optional)
Copy `config.example.json` to `config.json` and adjust aliases/defaults.
## Run
```bash
node src/skill.mjs --service ecs --metric cpu --resource my-ecs-cluster --hours 1
node src/cli.mjs --service ecs --metric CPUUtilization --resource my-ecs-cluster --hours 1
node src/cli.mjs --service ecs --metric MemoryUtilization --resource my-ecs-cluster --serviceName my-ecs-service --hours 1
node src/cli.mjs --service ec2 --metric CPUUtilization --resource i-1234567890abcdef0 --hours 3
node src/cli.mjs --service rds --metric connections --resource mydbinstance --hours 6
```
## Output
- Text summary to stdout (min/max/avg).
## Notes
- ECS without Container Insights supports cluster-level `CPUUtilization` / `MemoryReservation`.
- Default period: 300s (5 minutes). Default region: `us-west-2`.
- You can use metric aliases (see `config.example.json`).
- Text-only output (no chart rendering).
```
### _meta.json
```json
{
"owner": "delbertheihei",
"slug": "aws-cloud-watch",
"displayName": "AWS CloudWatch",
"latest": {
"version": "0.0.1",
"publishedAt": 1772247913910,
"commit": "https://github.com/openclaw/skills/commit/a9599f5effd8979f36b0c220a909f8ab9d356b7a"
},
"history": []
}
```