aws / aws/aws-toolkit-vscode

Invoke Lambda Locally and TimeoutError: Connection timed out after 120000ms

Open
#2,894 4 comments 0 reactions 0 assignees View on GitHub
feature-request lambda
Dominant language
TypeScript
Stars
2k
Forks
807
Avg merge
10h 12m
Merged PRs (30d)
7

Description

## Problem
Invoke a Lambda locally from AWS toolkit in VSCode and showing this error although the timeout value of the Lambda has been set up to 15 minutes.
## Expected behavior
I did some research and looks like this questions is similar [https://stackoverflow.com/questions/51259150/occasionally-connection-timeout-from-lambda-function](https://stackoverflow.com/questions/51259150/occasionally-connection-timeout-from-lambda-function) but it is just for SDK and couldn't find any relevant settings in VSCode.
It should either respect its own timeout configuration from the Lambda or allow developer to adjust the HTTP timeout values in VSCode. Thanks.

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are identified. Start by reproducing a local Lambda invocation from the AWS Toolkit in VS Code with the Lambda timeout set to 15 minutes, then trace where the 120000ms connection timeout is applied. Done means local invocation either respects the Lambda timeout or exposes an adjustable HTTP timeout in VS Code.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
cloud, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.