If something is suddenly taking three minutes to complete (when it didn't before) and there is a "remote node" involve I would suspect something network-wise as the problem. DNS. Reachability. Firewalls at the far end. Something.
I'm something of a Luddite here but if it were me I'd be putting debug statements with timestamps at every step of the way within the code and figuring out what is going on. Brute force: yes. Elegant: no. Good at figuring out the problem? Absolutely.
As you can see in the logs you shared, the Lambda functioned timed out:
Task timed out after 180.63 seconds.
I don't have enough information to tell you why it did. Good news is that there is a troubleshooting guide which you can use to identify the issue and then fix it.
Hope this helps.
- asked 2 months ago
- AWS OFFICIALUpdated a year ago
- How can I use the AWS CLI to register a Lambda function as a target behind my Application Load Balancer?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- How do I update Lambda environment variables without hardcoding a new function version into my application?AWS OFFICIALUpdated 3 years ago