com.amazonaws.SdkClientException: Unable to execute HTTP request: Read timed out - AWS assertion timeout at 200K ms

Products

• CA API Gateway

Issue/Introduction

cluster wide property aws.requestTimeoutMillis set to 900,000 milliseconds (15 minutes).  Despite this, we are still seeing the AWS assertion throw the error:

{"Error":"com.amazonaws.SdkClientException: Unable to execute HTTP request: Read timed out"}

when the lambda runs for more than 200,000 ms. 

We are running AWSSolutionKit version 1.0.01

On the AWS side, the lambda is configured with maximum runtime of 15 minutes, and CloudWatch logs show it successfully completes execution each time,

so there's no timeout happening on the AWS side.

Environment

API GATEWAY

Resolution

Use aws.socketTimeoutMillis clusterwide property to resolve this issue

aws.socketTimeoutMillis - Specifies the AWS socket timeout value in milliseconds.
Default: 50 seconds

If the timeout expires, no logs are generated, and the SDK retries the request until aws.requestTimeoutMillis (default 200s) is reached. However, if aws.socketTimeoutMillis is explicitly set, an error triggers once the timeout is reached, preventing further Lambda retries.

Additional Information

This clusterwide property was added in 1.0.02 version.

Gateway 11.0 and 11.1 are now shipped with AWSSolutionKit-1.0.03.zip