aws-lambda

问题 I am running a Meteor (Node 4.4.7) application that performs long operations on AWS Lambda. I invoke the lambda function from my code and wait for the response before proceeding to the next invocation. I set the timeout to 300000ms as described in a former question (both on Lambda and in the AWS.Lambda object in my code). My problem is that sometimes the AWS.Lambda timeout value is reset to the default value of 120000ms. As my Lambda function takes more time to execute (but still less than

问题 I am running a Meteor (Node 4.4.7) application that performs long operations on AWS Lambda. I invoke the lambda function from my code and wait for the response before proceeding to the next invocation. I set the timeout to 300000ms as described in a former question (both on Lambda and in the AWS.Lambda object in my code). My problem is that sometimes the AWS.Lambda timeout value is reset to the default value of 120000ms. As my Lambda function takes more time to execute (but still less than

问题 I am running a Meteor (Node 4.4.7) application that performs long operations on AWS Lambda. I invoke the lambda function from my code and wait for the response before proceeding to the next invocation. I set the timeout to 300000ms as described in a former question (both on Lambda and in the AWS.Lambda object in my code). My problem is that sometimes the AWS.Lambda timeout value is reset to the default value of 120000ms. As my Lambda function takes more time to execute (but still less than

问题 I am deploying some apis to API Gateway using cdk. My problem is the file that contains the lambda(index.ts) can't import any files or npm modules outside that folder(folder named get-users ). I tried copying node_modules folder and other files (which were outside the folder get-users ) to the folder get-users and it worked perfectly. Example error when importing lodash is as follows, "errorType": "Runtime.ImportModuleError", "errorMessage": "Error: Cannot find module 'lodash'", "stack": [

问题 I am deploying some apis to API Gateway using cdk. My problem is the file that contains the lambda(index.ts) can't import any files or npm modules outside that folder(folder named get-users ). I tried copying node_modules folder and other files (which were outside the folder get-users ) to the folder get-users and it worked perfectly. Example error when importing lodash is as follows, "errorType": "Runtime.ImportModuleError", "errorMessage": "Error: Cannot find module 'lodash'", "stack": [

问题 I am deploying some apis to API Gateway using cdk. My problem is the file that contains the lambda(index.ts) can't import any files or npm modules outside that folder(folder named get-users ). I tried copying node_modules folder and other files (which were outside the folder get-users ) to the folder get-users and it worked perfectly. Example error when importing lodash is as follows, "errorType": "Runtime.ImportModuleError", "errorMessage": "Error: Cannot find module 'lodash'", "stack": [

问题 I create a new AWS Lambda .NET Core 3.1 project, then run it using AWS Lambda Test Tools, then I get this page as expected: However, if I install one of these packages: Microsoft.EntityFrameworkCore.SqlServer Microsoft.Data.SqlClient When I run, I get this error and the test page won't open: AWS .NET Core 3.1 Mock Lambda Test Tool (0.10.0) Unknown error occurred causing process exit: Dependency resolution failed for component C:\Users\siri\repos\bolao-futebol\website-core\AWSLambda1\bin\Debug

问题 I create a new AWS Lambda .NET Core 3.1 project, then run it using AWS Lambda Test Tools, then I get this page as expected: However, if I install one of these packages: Microsoft.EntityFrameworkCore.SqlServer Microsoft.Data.SqlClient When I run, I get this error and the test page won't open: AWS .NET Core 3.1 Mock Lambda Test Tool (0.10.0) Unknown error occurred causing process exit: Dependency resolution failed for component C:\Users\siri\repos\bolao-futebol\website-core\AWSLambda1\bin\Debug

问题 I create a new AWS Lambda .NET Core 3.1 project, then run it using AWS Lambda Test Tools, then I get this page as expected: However, if I install one of these packages: Microsoft.EntityFrameworkCore.SqlServer Microsoft.Data.SqlClient When I run, I get this error and the test page won't open: AWS .NET Core 3.1 Mock Lambda Test Tool (0.10.0) Unknown error occurred causing process exit: Dependency resolution failed for component C:\Users\siri\repos\bolao-futebol\website-core\AWSLambda1\bin\Debug

问题 There are a few pieces of my app that cannot afford the additional 1-2 second delay caused by the "freeze-thaw" cycle that Lambda functions go through when they're new or unused for some period of time. How can I keep these Lambda functions warm so AWS doesn't have to re-provision them all the time? This goes for both 1) infrequently-used functions and 2) recently-deployed functions. Ideally, there is a setting that I missed called "keep warm" that increases the cost of the Lambda functions,