Aws Debug
- 3 installs
- 12 repo stars
- Updated June 8, 2026
- aws-samples/sample-claude-code-plugins-for-startups
AWS Debug is a Claude skill that systematically diagnoses and resolves AWS infrastructure issues, deployment failures, and runtime errors.
About
This skill is an AWS debugging specialist that systematically diagnoses and resolves AWS infrastructure issues, deployment failures, and runtime errors. A developer uses it when troubleshooting CloudFormation stack failures, Lambda errors, ECS task failures, permission issues, or networking problems. It follows a symptom-to-fix workflow with ready AWS CLI investigation commands and a gotchas list.
- Systematic debugging workflow for AWS deployment failures and runtime errors
- Investigation commands for CloudFormation, Lambda, ECS, and IAM issues
- Gotchas list covering common AWS failure modes and their real causes
Aws Debug by the numbers
- 3 all-time installs (skills.sh)
- Ranked #458 of 596 Debugging skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
aws-debug capabilities & compatibility
- Capabilities
- debugging
- Works with
- aws
- Use cases
- debugging · devops
What aws-debug says it does
Debug AWS infrastructure issues, deployment failures, and runtime errors.
CloudFormation rollback errors often hide the real error — look at the FIRST failed resource
npx skills add https://github.com/aws-samples/sample-claude-code-plugins-for-startups --skill aws-debugAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 3 |
|---|---|
| repo stars | ★ 12 |
| Last updated | June 8, 2026 |
| Repository | aws-samples/sample-claude-code-plugins-for-startups ↗ |
What it does
Diagnose and resolve AWS deployment failures and runtime errors with targeted CLI commands.
Who is it for?
Troubleshooting CloudFormation, Lambda, ECS, IAM, and networking failures on AWS.
When should I use this skill?
A developer is troubleshooting an AWS deployment failure, runtime error, or permission issue.
What you get
Identifies root cause with supporting evidence and proposes the minimal fix plus prevention.
By the numbers
- 6-step debugging workflow
Files
You are an AWS debugging specialist. Systematically diagnose and resolve AWS issues.
Debugging Workflow
1. Identify the symptom: What failed? Error message, status code, behavior 2. Gather context: Check logs, events, and resource state using AWS CLI 3. Form hypothesis: Based on the evidence, what's most likely wrong? 4. Verify: Run targeted commands to confirm or reject the hypothesis 5. Fix: Propose the minimal change to resolve the issue 6. Prevent: Suggest how to catch this earlier next time
Common Investigation Commands
# CloudFormation stack failures
aws cloudformation describe-stack-events --stack-name <name> --query 'StackEvents[?ResourceStatus==`CREATE_FAILED` || ResourceStatus==`UPDATE_FAILED`]'
# Lambda errors
aws logs filter-log-events --log-group-name /aws/lambda/<function-name> --filter-pattern "ERROR"
# ECS task failures
aws ecs describe-tasks --cluster <cluster> --tasks <task-arn> --query 'tasks[].stoppedReason'
# IAM permission issues
aws sts get-caller-identity
aws iam simulate-principal-policy --policy-source-arn <role-arn> --action-names <action>Gotchas
- CloudFormation rollback errors often hide the real error — look at the FIRST failed resource
- Lambda timeout ≠ API Gateway timeout. API GW has a hard 29s limit
- "Access Denied" in S3 can mean bucket policy, IAM policy, ACL, OR VPC endpoint policy
- ECS tasks that fail immediately: check the container image exists and the task role has ECR pull permissions
- Security group "connection timeout" usually means missing inbound rule, not outbound
- CloudWatch Logs can take 1-2 minutes to appear — don't assume no logs means no execution
aws sts get-caller-identityis your best friend — always verify who you're authenticated as- Terraform state drift: run
terraform planbefore assuming your code matches reality - CDK bootstrap version mismatch causes cryptic deploy failures — check
cdk bootstrapversion
Output Format
For each issue found: 1. Root Cause: What went wrong and why 2. Evidence: The specific log line, error, or state that confirms it 3. Fix: Exact command or code change to resolve it 4. Prevention: How to avoid this in the future (monitoring, tests, guardrails)
Related skills
Azure DiagnosticsSystematically diagnose and resolve production issues on Microsoft Azure using official Microsoft guidance.495k1.3kAzure MessagingQuickly diagnose and fix connection, authentication, and message-processing failures when using Azure Event Hubs or Service Bus SDKs.483k1.3k
Diagnosing BugsGet a systematic, step-by-step process that surfaces the real root cause instead of guessing at bugs.291k200k
Use My BrowserWhen their agent task requires access to the live browser session, rendered DOM state, authenticated dashboards, localhost apps, or DevTools-selected elements instea269k71
Systematic DebuggingFollow a repeatable four-phase process that forces root-cause discovery before any code changes.210k265k
Safe DebugGet conservative, non-destructive diagnosis of deep learning and agent errors before any code changes are made.185k512FAQ
What AWS services does it debug?
CloudFormation, Lambda, ECS, IAM permissions, and networking issues, among other AWS service misbehavior.
How does it approach a bug?
It follows a workflow of identifying the symptom, gathering context, forming a hypothesis, verifying, fixing, and preventing recurrence.