Skip to content

Conversation

@ParidelPooya
Copy link
Contributor

Add connection and socket timeout configurations to LambdaClient:

  • connectionTimeout: 5000ms (5 seconds)
  • socketTimeout: 50000ms (50 seconds)

This helps prevent hanging requests and provides better error handling for Lambda API calls.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@ParidelPooya ParidelPooya force-pushed the feat/sdk-lambda-client-timeouts branch from 4c3da98 to f437545 Compare November 12, 2025 23:59
Add connection and socket timeout configurations to LambdaClient to improve reliability:
- connectionTimeout: 5000ms (5 seconds)
- socketTimeout: 50000ms (50 seconds)

This helps prevent hanging requests and provides better error handling for Lambda API calls.

Updated api-storage test to verify LambdaClient is initialized with timeout settings.
@ParidelPooya ParidelPooya force-pushed the feat/sdk-lambda-client-timeouts branch from f437545 to b7e642e Compare November 13, 2025 02:23
@bchampp bchampp merged commit 66bffe8 into development Nov 13, 2025
7 checks passed
@bchampp bchampp deleted the feat/sdk-lambda-client-timeouts branch November 13, 2025 02:47
requestHandler: {
connectionTimeout: 5000,
socketTimeout: 50000,
requestTimeout: 5000,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be requestTimeout: 50000 at least right? And we need to also specify throwOnRequestTimeout=true otherwise it only logs a warning

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants