- by default, API processing stops the node VM using the callbackWaitsForEmptyEventLoop Lambda context parameter. This is to prevent runaway node.js events caused by third party libs causing the Lambda VM to become stuck after a request completes. If you really want the VM execution to continue until the event loop empties, even after your API process is done, then set
lambdaContext.callbackWaitsForEmptyEventLooptotruein your request handler.
- support for intercepting and modifying requests
- shortcut for configuring stage variables during deployment
- you can now provide a handler for unsupported event formats, and invoke the same Lambda from a source that's not API Gateway