AutoGineer
Generated banner for Debugging Lambda Timeouts
Generated logo for Debugging Lambda Timeouts

Debugging Lambda Timeouts

AWSOfficialPublished by AWS

  • Skill
  • Review and audit
  • Cloud and DevOps
  • Apache-2.0
  • No issues found
Download ZIP

From the author

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.
— the description by AWS

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured approach to investigating AWS Lambda timeout issues. It guides the user through a multi-step diagnostic process that includes retrieving function configurations, analyzing CloudWatch metrics for duration and error trends, and reviewing log data. By correlating these findings with potential bottlenecks like memory constraints, cold starts, or downstream dependency delays, the skill helps identify the root cause of failures and provides actionable recommendations for remediation.

What it does

  • Retrieves and evaluates Lambda function configuration, including memory and timeout settings.
  • Analyzes CloudWatch metrics to identify duration trends and error patterns.
  • Checks log group availability and data for specific timeout events.
  • Reviews provided function code for common timeout-prone patterns.
  • Compiles diagnostic findings into a structured report with prioritized fixes.

When to use it

  • When an AWS Lambda function is consistently timing out.
  • When a function is approaching its configured timeout limit.
  • When you need to determine if a timeout is caused by code, configuration, or external dependencies.
  • During performance tuning to optimize Lambda execution duration.

Advantages

  • Provides a consistent, repeatable methodology for troubleshooting.
  • Reduces manual effort by automating data collection from AWS services.
  • Helps distinguish between infrastructure-related issues and code-level inefficiencies.
  • Delivers prioritized, actionable recommendations based on empirical data.

Usage examples

“My Lambda function 'order-processor' in us-east-1 is timing out. Can you help me debug it?”
The agent will request the required parameters (function name, region, and optional time window) and then initiate the systematic diagnostic workflow.
“Debug my Lambda function 'data-sync' in us-west-2. I've attached the code for analysis.”
The agent will analyze the provided code alongside the live AWS configuration and metrics to identify potential performance bottlenecks.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/aws/debugging-lambda-timeouts/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip debugging-lambda-timeouts.zip -d .agents/skills

Documentation by AWS

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.

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.

Files

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
AWS
Publisher
AWS (Official)
Source
aws/agent-toolkit-for-aws · skills/specialized-skills/serverless-skills/debugging-lambda-timeouts · commit 0a218f8
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • NOTICE (added by AutoGineer from NOTICE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by AWS.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download debugging-lambda-timeouts.zip