aws-resource-health-diagnose
Analyze AWS resource health, diagnose issues from CloudWatch logs and metrics, and create a remediation plan for identified problems.
Profile →npx skills add github/awesome-copilot --skill aws-resource-health-diagnose --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# AWS Resource Health & Issue Diagnosis This workflow analyzes a specific AWS resource to assess its health status, diagnose potential issues using CloudWatch logs and metrics, and develop a comprehensive remediation plan for any problems discovered. ## Prerequisites - AWS CLI configured and authenticated - Target AWS resource identified (name, type, and optionally region/account) - CloudWatch logging and metrics enabled on the target resource ## Workflow Steps ### Step 1: Get AWS Diagnostic Best Practices Fetch `https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/` for monitoring and troubleshooting guidance to inform the diagnostic approach. ### Step 2: Resource Discovery & Identification Locate the target resource using the appropriate AWS CLI command for its type: ```bash # EC2 aws ec2 describe-instances --filters "Name=tag:Name,Values=<name>" # Lambda aws lambda get-function --function-name <name> # RDS aws rds describe-db-instances --db-instance-identifier <name> # ECS aws ecs describe-services --cluster <cluster> --services <name> # ALB aws elbv2 describe-load-balancers --names <name> # DynamoDB aws dynamodb describe-table --table-name <name> # SQS aws sqs get-que
- Prerequisites
- Workflow Steps
- Step 1: Get AWS Diagnostic Best Practices
- Step 2: Resource Discovery & Identification
- Step 3: Health Status Assessment
- Step 4: Log & Metrics Analysis
- Step 5: Issue Classification & Root Cause Analysis
- Step 6: Generate Remediation Plan
- Step 7: Report & User Confirmation
- Error Handling
- Success Criteria
EC2 aws ec2 describe-instances --filters "Name=tag:Name,Values=<name>" Lambda aws lambda get-function --function-name <name> RDS aws rds describe-db-instances --db-instance-identifier <name> ECS aws ecs describe-services --cluster <cluster> --services <name> ALB aws elbv2 describe-load-balancers --names <name>
What does the aws-resource-health-diagnose skill do?
Analyze AWS resource health, diagnose issues from CloudWatch logs and metrics, and create a remediation plan for identified problems.
How do I install it?
Run `npx skills add github/awesome-copilot --skill aws-resource-health-diagnose --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.