AMPLIFY CLI SET TIME OUT FOR LAMBDA FUNCTIONS
See original GitHub issueWhich Category is your question related to?
Setting the Time Out for Lambda Functions via the CLI. I would like to also set time out for AppSync, but I don’t believe you can do that at this time.
Amplify CLI Version
4.18.1
What AWS Services are you utilizing?
AppSync, DynamoDB, ElasticSearch
Provide additional details e.g. code snippets
I want to increase the time out period for Lambda functions and am unsure where I should set this in the Amplify project. I think you set something like this, but am not sure and not sure where it should be set.
"Globals":{
"Function": {"Timeout": 300}
}
Issue Analytics
- State:
- Created 3 years ago
- Reactions:9
- Comments:10 (2 by maintainers)
Top Results From Across the Web
Functions - Build options - AWS Amplify Docs
Use build options for Amplify's function category to execute a script before a function is deployed, e.g. to transpile Typescript or ES6 with...
Read more >update-function-configuration — AWS CLI 1.27.37 Command ...
The amount of time (in seconds) that Lambda allows a function to run before stopping it. The default is 3 seconds. The maximum...
Read more >AWS Amplify lambda function timeout - Stack Overflow
I've also tried using an axios intercepter to increase the timeout on all requests in the code as some suggested, but it didn't...
Read more >Boosting Lambda performance with AWS Amplify - LinkedIn
Out of the box, Amplify allows us to bootstrap Lambda functions with just a few CLI prompts. During our beta testing cycle, ...
Read more >Amplify Not Pulling Remote Lambda Changes - ADocLib
The way to find out what is the reason for the timeout is digging into the ... Use Amplify CLI to add powerful...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I was able to change the timeout in the <function_name>-awscloudformation-template.json file in the lambda’s directory.
To do so, I added the following line to the “Resources” -> “Lambda Function” field (for 2 minutes):
Full documentation can be found here https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-lambda-function.html
Adding my voice of support to this!