Closed Hodir22 closed 3 months ago
Hi @Hodir22, thanks for reaching out. I wasn't able to reproduce this behavior. In my testing, I eventually would get a response from Lambda. Are you able to get this working if you set max_attempts
to be higher in your retry configuration? That might be the simplest approach.
Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.
Describe the bug
I use the
aws lambda invoke
command as following:The lambda runs for 5 - 10 minutes and should return a response afterwards. However, the response is not returned. Instead, the lambda is retried until the maximum attempts have been reached. Note that no error occurs during the execution of the lambda, which finishes successfully.
I have configured the read and connection time-out to see if the problem that I am facing is related to this, but tried different values. This does not make a difference. After a while, the following debugging lines show:
I have seen somewhat similar issues on Github, but there the connection was explicitly terminated and an exception was thrown by boto3. In my case, this does not happen until the max. attempts have been reached.
What can be the cause of this issue, and is there any approach to resolve or further debug this issue?
Expected Behavior
The lambda invocation returns a response when its execution has ended.
Current Behavior
The event is retried until the maximum number of attempts (3) is exceeded. When the execution finishes, no response is returned and another invocation is executed.
The below stacktrace shows the CLI call with --debug enabled:
Reproduction Steps
Possible Solution
No response
Additional Information/Context
We run the CLI command from an Azure pipeline agent.
CLI version used
aws-cli/2.15.22 Python/3.11.6
Environment details (OS name and version, etc.)
Linux/6.2.0-1019-azure exe/x86_64.ubuntu.22