aws-resource-health-diagnose

Diagnose AWS resource health using CloudWatch logs and metrics to produce remediation plans.

38.5k|4.9k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill aws-resource-health-diagnose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws-resource-health-diagnose
Source: https://github.com/github/awesome-copilot/tree/main/skills/aws-resource-health-diagnose
Command: npx skills add https://github.com/github/awesome-copilot --skill aws-resource-health-diagnose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Troubleshooting unhealthy AWS resources requires manually correlating CloudWatch metrics, logs, and service status across many CLI commands, which is slow and error-prone. This Skill automates the full diagnostic workflow from resource discovery through root cause analysis to a phased remediation plan.

Core Features & Use Cases

  • Multi-Service Health Assessment: Runs service-specific health checks for EC2, Lambda, RDS, ECS, ALB, SQS, DynamoDB, and API Gateway using AWS CLI and CloudWatch metrics.
  • Log & Root Cause Analysis: Executes CloudWatch Logs Insights queries to find error patterns, cold starts, and dependency failures, then classifies issues by severity and root cause category.
  • Actionable Remediation Plan: Generates immediate, short-term, and long-term fixes with ready-to-run AWS CLI commands, plus CloudWatch alarm recommendations.
  • Use Case: A Lambda function's error rate spikes overnight. Use this Skill to pull 24-hour error metrics, query logs for recurring exceptions, identify IAM permission denials as the root cause, and receive a step-by-step remediation plan.

Quick Start

Diagnose the health of my Lambda function named payment-processor and create a remediation plan for any issues found.

Frequently Asked Questions about aws-resource-health-diagnose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose AWS Lambda errors with CloudWatch?

Query the AWS/Lambda namespace for the Errors metric over the past 24 hours, then run CloudWatch Logs Insights queries on the /aws/lambda/<name> log group filtering for ERROR patterns. This Skill automates both steps and correlates findings into a root cause analysis.

How to check AWS resource health using the AWS CLI?

Use service-specific commands like aws ec2 describe-instance-status, aws rds describe-db-instances, or aws ecs describe-services to get status, then pull CloudWatch metrics for error rates, latency, and throttling. The Skill chains these commands into a single diagnostic workflow.

What AWS services does this health diagnosis support?

It supports EC2, Lambda, RDS, ECS, Application Load Balancer, SQS, DynamoDB, and API Gateway. Each service has dedicated discovery commands, health indicators, and log query patterns defined in the workflow.

What IAM permissions are needed for CloudWatch log analysis?

The diagnostic workflow requires IAM permissions for logs:*, cloudwatch:*, and pi:* (Performance Insights) actions. If permissions are insufficient, the Skill lists the required actions so you can update the IAM policy.

Why does CloudWatch log analysis return no results?

Empty results usually mean CloudWatch logging is not enabled on the resource, the log group prefix is wrong, or the time window is too narrow. Enable logging for the resource type or shorten the query time range to resolve timeouts.