Debugging Lambda Timeouts

When your Lambda hits timeout and you're digging through CloudWatch logs trying to figure out why, this walks you through a systematic investigation. It checks the obvious stuff like timeout configuration and memory settings, then digs into cold starts, VPC networking issues, downstream dependencies, and code patterns that burn through execution time. The structured procedure keeps you from randomly guessing or missing something critical when you're under pressure to fix it. Most useful when you're dealing with intermittent timeouts or inheriting someone else's Lambda that's mysteriously slow, since it forces you to look at metrics and logs in a specific order rather than just bumping the timeout and hoping.

skills.sh installs: 6.8K
GitHub stars: 3.4K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts --agent claude-code

Installs into .claude/skills of the current project.

Files

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.

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.