From claude-devops
Investigate AWS resource issues by running run-investigation.sh with the service type, resource name, profile, and region.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-devops:aws-troubleshootingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The `/aws-investigate` command and `aws-investigator` agent run the automated investigation orchestrator:
The /aws-investigate command and aws-investigator agent run the automated investigation orchestrator:
bash skills/aws-troubleshooting/run-investigation.sh "<service-type>" "<resource-name>" "<profile>" "<region>"
lambda - Lambda function concurrency, errors, throttling, logsrds - RDS instance status, connections, storage, performanceec2 - EC2 instance status, system checks, CPU/network metricsecs - ECS service status, task state, container logss3 - S3 bucket configuration, access, replication statusalb - ALB health, target groups, listener statusvpc - VPC security groups, network ACLs, route tables/aws-investigate commandexamples/investigate-lambda.sh - Queries Lambda function metrics, errors, logsexamples/investigate-rds.sh - Queries RDS instance metrics, connections, eventsnpx claudepluginhub kjenney/claude-devopsAnalyze AWS resource health, diagnose issues from CloudWatch logs and metrics, and create a remediation plan for identified problems.
Runs deep root-cause investigation on AWS DevOps Agent for incidents, alarms, outages. Polls and streams progress, surfaces recommendations.
Investigates AWS incidents and observability gaps using CloudWatch metrics, logs, alarms, traces, EventBridge, and runbooks. Prefer RDS/Aurora for database-specific performance incidents.