If you end the execution with context. I would think that this would be standard procedure before letting the public have at it. This gives a nice separation between application code and configuration and it allows you to deploy code packages across different stages i.
Just make sure the function is already warmed up, so you can measure the right execution time. And make it outside the handler.
Lambda function timeout
Have a question about this project. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. TableNames ; } ; }; And I get timeout. Can you set maxRetries to 1 or 0. Do you have many tables to list. You could also try limiting the number of tables that get returned by listTables by setting to see if that's the issue. Data : ' + data. It's the only one dynamodb table. Data : ' + data. Feel free to close the issue. This guy saved my life: Thanks.
Where do I think Lambda has some things it could improve on? If you end the execution with context. Everything you wrote and more! Then deploy with relative ease a little more involved than deploying Lambdas, but I could make a Gruntfile or shell script or something. In this case, downstream failures are handled and the user experience is downgraded gracefully as opposed to simply surfacing the failures to the user. So how can we know how to define these nodes accurately? The first time I called the function it worked, but all subsequent calls return the error Cannot enqueue Handshake after invoking quit. I'm still not sure what was causing the delay, possibly Java network stack initialization? Just make sure the function is already warmed up, so you can measure the right execution time. Do you have many tables to list?