debugging-lambda-timeouts — Claude Code skill: how to install
Investigates AWS Lambda timeout failures by inspecting CloudWatch logs, metrics, and configurations. Use it when function runs hit or approach execution limits.
npx skills add aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts -a claude-codeWhat debugging-lambda-timeouts does
This skill investigates execution timeouts in AWS Lambda. It gathers runtime settings and checks database connection delays. If source code is provided, the skill inspects it for timeout-prone patterns.
Diagnostics rely on CloudWatch logs and invocation metrics. The skill checks cold start spikes alongside memory limits, because resource starvation often causes execution stalls. All findings go into a structured debugging report with prioritized fixes.
AWS credentials must grant read permissions for Lambda, CloudWatch Logs, and CloudWatch Metrics. Missing permissions break the diagnostic run immediately. When CloudWatch Logs Insights queries fail due to time ranges, the analysis window needs to be shortened.
What it helps with
- trace timeout causes in CloudWatch logs
- diagnose database connection delays and network latency
- evaluate cold start overhead and memory constraints
- find slow execution patterns in Lambda code
Example prompts for the agent
- Investigate why the process-orders Lambda function in us-east-1 keeps timing out.
- Analyze CloudWatch metrics and configuration for sync-users, it is approaching the timeout limit.
How to install debugging-lambda-timeouts
1Skills CLI (Vercel)
npx skills add aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts -a claude-code2Manually: put the files in place
~/.claude/skills/debugging-lambda-timeouts/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/debugging-lambda-timeouts/
1Skills CLI (Vercel)
npx skills add aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts -a codex2Manually: put the files in place
.agents/skills/debugging-lambda-timeouts/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts -a cursor2Manually: put the files in place
.cursor/skills/debugging-lambda-timeouts/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aws/agent-toolkit-for-aws debugging-lambda-timeouts2Manually: put the files in place
.github/skills/debugging-lambda-timeouts/SKILL.md1Skills CLI (Vercel)
npx skills add aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts -a gemini-cli2Platform CLI
gemini skills install https://github.com/aws/agent-toolkit-for-aws --path skills/specialized-skills/serverless-skills/debugging-lambda-timeoutsManually: put the files in place
.devin/skills/debugging-lambda-timeouts/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about debugging-lambda-timeouts
How to install debugging-lambda-timeouts in Claude Code?
Run npx skills add aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts -a claude-code.
What does debugging-lambda-timeouts do?
It systematically reviews Lambda configuration, CloudWatch metrics, cold start patterns, and external dependencies. At the end, it outputs a structured debugging report with prioritized fixes.
What AWS access is needed to run the investigation?
AWS credentials must have permissions for Lambda, CloudWatch Logs, and CloudWatch Metrics. Without them, diagnostic queries fail with access denied errors.
Source text
SKILL.md · Apache-2.0
--- name: debugging-lambda-timeouts description: Debugs AWS Lambda function timeout failures by systematically analyzing function configuration, CloudWatch logs and metrics, VPC/networking, cold starts, memory constraints, and downstream dependencies to identify root causes with actionable fixes. Use when a Lambda function is timing out or approaching its timeout limit. version: 1 --- # Debugging Lambda Timeouts ## Overview Domain expertise for systematically investigating AWS Lambda function timeout failures by analyzing function configuration, CloudWatch logs, metrics, dependencies, cold start patterns, and code. Identifies common causes such as insufficient timeout settings, external service delays, database connection issues, memory constraints, and inefficient code patterns, then provides prioritized recommendations. ## Debug a Lambda timeout To investigate and resolve Lambda timeout issues, follow the procedure exactly. See [Lambda timeout debugging procedure](references/lambda-timeout-debugging.md). The procedure collects function configuration, CloudWatch metrics and logs, dependency analysis, and cold start patterns. If Lambda code is provided, it also reviews the code for timeout-prone patterns. Results are compiled into a structured debugging report with prioritized recommendations. ## Troubleshooting ### Function not found Verify the function name and region. Use `aws lambda list-functions --region <region>` to list available functions. ### No logs available The function may not have been invoked recently or logging may be disabled. Check the function's log group configuration and invocation metrics. ### Access denied errors Verify AWS credentials have permissions for Lambda, CloudWatch Logs, and CloudWatch Metrics. See the full procedure for details. ### Log query time range issues If CloudWatch Logs Insights queries fail with time range errors, reduce the analysis window or check log group retention settings. See the full procedure for details.
© aws · Apache-2.0 · aws/agent-toolkit-for-aws