AWS Now Supports Max Retry Attempts
See original GitHub issueAdd support for the new lambda config option MaximumRetryAttempts
.
Retry attempts – The number of times Lambda retries when the function returns an error, between 0 and 2.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:18
- Comments:18 (7 by maintainers)
Top Results From Across the Web
Amazon Lambda Now Supports Maximum Event Age and ...
With Maximum Event Age, you can configure the lifetime of an event in the queue from 60 seconds to 6 hours. This allows...
Read more >How to set the number of retry attempts of AWS Lambda in ...
[2020-09 updated answer] As of v1.78.0, serverless now supports maximumRetryAttempts (and maximumEventAge ). [2020-01 original answer] At ...
Read more >How AWS Lambda Retry really works - Serverless Framework
In this post, we'll analyze the AWS Lambda Retry Policy, ... The quick and dirty approach is to set the Maximum Retry Attempt...
Read more >Let's Try Again: Making Retries Work With Cloud Services
Not surprisingly, Amazon's AWS enforces rate limits on their services. Their client libraries also incorporate automatic retries.
Read more >How to handle automatic retries in AWS Lambda ... - YouTube
Welcome to the video tutorial on How to handle default retry behavior in the AWS Lambda function. In this tutorial, I have explained...
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
Although the async config can be added as a custom resource, I would argue that limiting the retry attempts is a super common want. Common enough to be included in the main function definition (like
timeout
,reservedConcurrency
etc).What users want/need obviously isn’t considered a relevant factor in this project. Or just plain common sense.