Hi - we’re experiencing a read_timeout issue with ...
# prefect-community
Hi - we’re experiencing a read_timeout issue with the
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 this task to create a function, there is
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. 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:
Copy code
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
seems you know the solution then? I think the AWS doc is helpful