mcpField
D
debugging-lambda-timeouts

debugging-lambda-timeouts

github.com/awsCloud & DevOps3.3k6.5k installsUpdated today
Repository

About debugging-lambda-timeouts

A debugging skill for investigating AWS Lambda timeouts. It examines configuration, CloudWatch data, dependencies, cold starts, and supplied code, then organizes likely causes and prioritized recommendations.

Key features

  1. 01Review Lambda configuration and CloudWatch data
  2. 02Inspect dependencies and cold start patterns
  3. 03Analyze provided code for timeout risks
  4. 04Produce a prioritized debugging report

Use cases

  1. 01Investigating recurring Lambda timeouts
  2. 02Checking external service or database delays
  3. 03Assessing memory limits and inefficient code

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts

After installing, type/debugging-lambda-timeoutsin Claude Code to confirm it loaded.

Bundled filesreferences/lambda-timeout-debugging.md

Details

From the project README

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.

Comments

Markdown supported