aws-debug

Diagnose AWS infrastructure failures using CLI evidence and hypothesis validation.

15|20|Updated May 11, 2026
One-click install
npx skills add https://github.com/awslabs/startups --skill aws-debug-awslabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws-debug
Source: https://github.com/awslabs/startups/tree/main/solution-architecture/plugins/aws-dev-toolkit/skills/aws-debug
Command: npx skills add https://github.com/awslabs/startups --skill aws-debug-awslabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and resolve complex AWS infrastructure failures by turning unclear deployment errors, runtime issues, and service misbehavior into structured troubleshooting steps.

Core Features & Use Cases

  • AWS Failure Diagnosis: Investigate CloudFormation failures, Lambda errors, ECS task problems, IAM permission issues, and networking failures.
  • Evidence-Based Troubleshooting: Gather logs, events, and resource states with AWS CLI commands to identify root causes and verify fixes.
  • Use Case: When an AWS deployment fails unexpectedly, use this Skill to analyze the failure events, identify the problematic resource, and recommend the minimal corrective change.

Quick Start

Use the aws-debug skill to investigate why my AWS CloudFormation deployment failed and provide the root cause, fix, and prevention steps.

Frequently Asked Questions about aws-debug

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

FAQPage Schema
How do I debug a CloudFormation deployment failure in AWS?

To debug a CloudFormation deployment failure, this Skill systematically gathers deployment events and resource states using AWS CLI commands to identify the problematic resource. It then validates hypotheses and recommends the minimal corrective change to resolve the operational issue.

Why does my Lambda function fail at runtime and how can I find the root cause?

To resolve Lambda runtime errors, this Skill collects logs and runtime evidence to diagnose the failure. It applies structured troubleshooting workflows to validate root cause hypotheses and provides targeted remediation guidance for your AWS infrastructure.

How do I troubleshoot IAM permission issues affecting my ECS tasks?

Troubleshooting IAM permission issues affecting ECS tasks requires evidence-based investigation of task states and IAM policies. This Skill executes AWS CLI investigation commands to collect operational evidence, identify permission misconfigurations, and recommend precise fixes.

What is the best way to diagnose AWS networking failures and infrastructure misbehavior?

The best way to diagnose AWS networking failures is through evidence-based troubleshooting that collects events and resource states. This Skill transforms unclear infrastructure misbehavior into structured steps, validating root causes before recommending minimal corrective changes.

Does this troubleshooting workflow require specific AWS CLI investigation commands?

Yes, this troubleshooting workflow requires AWS CLI investigation commands to gather logs, events, and resource states. It uses these inputs to perform evidence collection and hypothesis validation, ensuring the root cause analysis is based on concrete operational data.

AWS infrastructure debugging not working with generic error messages, what are the limitations?

A limitation of AWS infrastructure debugging with generic error messages is the dependency on accessible CLI evidence. When AWS service debugging tasks lack sufficient logs or event data, hypothesis validation cannot pinpoint the root cause to recommend accurate remediation guidance.