aws-api-mcp-server: add ability to provide custom response timeout value #1874
Description
Describe the feature
Current timeout configuration is 10 seconds for connect timeout and 60 seconds for read timeout.
In some cases 60 seconds might be not sufficient - for example in case of synchronous lambda function invocation when expected lambda invocation time exceeds 60 seconds.
However response timeout might be different from socket read timeout, in cases when the response is sent back in chunks.
Use Case
When I use the call_aws for synchronous lambda function invocation when expected lambda invocation time exceeds 60 seconds the tool call times out.
Proposed Solution
No response
Other Information
No response
Acknowledgements
- I may be able to implement this feature request
- This feature might incur a breaking change