What problem does it solve? Investigating AWS service failures often means digging through massive log volumes and scattered metrics without a clear method, wasting time during incidents. This Skill provides a structured troubleshooting methodology for common AWS services so you can isolate root causes faster. ## Core Features & Use Cases - CloudWatch Logs Strategy: Partition-first query patterns using aggregation, error-rate binning, and latency percentiles instead of dumping raw logs. - Service-Specific Playbooks: Symptom-to-cause tables for EC2, Lambda, ECS/Fargate, and RDS, each listing the first check, typical causes, and key CloudWatch metrics. - Common Error Patterns: Guidance for permission errors, throttling, and resource-not-found failures with concrete remediation steps. - Use Case: A Lambda function starts timing out in production. Follow the Lambda playbook to query CloudWatch Insights for timeout patterns, analyze cold start metrics, and determine whether memory allocation or an external dependency is the cause. ## Quick Start Use the aws-troubleshoot skill to investigate why my Lambda function is timing out and analyze its CloudWatch logs.
