Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Hi - we’re experiencing a read_timeout issue with the `invokeLambda` task.

I think we need to pass it some extra config through boto_kwargs. Has anyone came across needing to do this before?

You can set a timeout for your Lambda function when you create it. E.g., when you use <https://docs.prefect.io/api/latest/tasks/aws.html#lambdacreate|this task> to create a function, there is `function_timeout` that can be set. Invoking a function is just making a single API call to AWS to trigger this function in a fire-and-forget way. <https://aws.amazon.com/premiumsupport/knowledge-center/lambda-function-retry-timeout-sdk/|This AWS doc may help>

It’s lamdaInvoke we currently use and the lambda has a timeout of 900 seconds. In the logs we see:

```  raise ReadTimeoutError(
urllib3.exceptions.ReadTimeoutError: AWSHTTPSConnectionPool(host='<http://lambda.eu-west-2.amazonaws.com|lambda.eu-west-2.amazonaws.com>', port=443): Read timed out. (read timeout=60)```

calling it synchronously with `invocation_type="RequestResponse",`

seems you know the solution then? I think the AWS doc is helpful