Hey does this just mean our EKS cluster hasn t whitelisted

Question

Hey does this just mean our EKS cluster hasn t whitelisted <http api prefect io|api prefect io>

Dylan · Answer

```urllib3 exceptions MaxRetryError HTTPSConnectionPool host= port=443 Max retries exceeded with url Caused by ReadTimeoutError HTTPSConnectionPool host= port=443 Read timed out read timeout=15 ```

Kevin Kho · Answer

No it could be you have a big API call happening You can increase that like by setting ```prefect context config cloud request timeout``` as seen <https github com PrefectHQ prefect pull 4119|here>

Dylan · Answer

What s the surface and size of the API calls

Dylan · Answer

And is there an environment variable for that setting we re running a prefect cloud agent so I m not using that config toml

Dylan · Answer

Dylan · Answer

Looking here for reference

Kevin Kho · Answer

Should be ```PREFECT CLOUD REQUEST TIMEOUT``` Size could depend on your Flow too Do you have any GraphQL queries could be under the hood of tasks too like `create flow run`

Dylan · Answer

I don t have any tasks that create their own flows pretty simple so far flow registration runs separately from flow execution flows executing are simple tasks not composing tasks from or within tasks for example but I am passing state between tasks Would it be possible that this is an error masking an underlying connection error for a failed `prefect engine results S3Result` I O operation

Kevin Kho · Answer

I don t think so because that would use the boto3 client I think this is specifically the Prefect Client Was this a one time thing yesterday

Kevin Kho · Answer

There was a spike in latency but I don t think it was an incident Or does this happen with some regularity

Dylan · Answer

Seems to just be once occurrence on 5 7

Kevin Kho · Answer

There may have been increased latency on 5 7 6pm ET so it might be a one off thing also