Open shadabk96 opened 5 years ago
Found this reply from Amazon support:
If you're using NodeJS, make sure that you have completed all asynchronous processing prior to returning from your request handler; otherwise, you may have a socket connection that is frozen (and subsequently thawed) across requests, which will often lead to a connection reset. Async processing in NodeJS is a frequent source of this type of error.
Are you using that lambda on a VPC and if yes, have you set up a NAT gateway so the lambda can talk to the Internet?
@shadabk96 were you able to make any progress? I'm getting a similar problem in a lambda@edge function...
I'm trying to hit omdb api via an AWS Lambda function but it is throwing the following error. I'm using Node v12.10 and calling via https module. Another point to be noted is that the call is working perfectly from my local machine.
Full stack trace: