- Newest
- Most votes
- Most comments
Hello! Step Functions would be the ideal implementation. However maybe it can be an overkill if your implementation is very simple or if you want a quick solution.
For example, if you are using an SQS Queue to trigger the Lambda, a quick implementation could be to delete the message from the queue and re-publish it using what is called a "MessageTimer" with a DelaySeconds
(more info here) property set to 10, 20, 30 minutes respectively (NOTE: minutes have to be specified in seconds within this property). Then, the queue will "hide" this message from publication until the specified delay has passed accomplishing the "retry" mechanism you are expecting.
Hope this helps!
PS: From the Amazon SQS documentation available here: "To set delay seconds on individual messages, rather than on an entire queue, use message timers to allow Amazon SQS to use the message timer's DelaySeconds value instead of the delay queue's DelaySeconds value."
Hi,
AWS Step Functions is a great service for use-cases like yours that involve orchestration. With Step Functions you can create a simple state machine that calls your AWS Lambda function. Step Functions has built-in retry and error handling, so you can configure the number of retries as well as the interval between them. For more information, please check: https://docs.aws.amazon.com/step-functions/latest/dg/concepts-error-handling.html
Please upvote/accept this answer if it was helpful.
Relevant content
- Accepted Answerasked 3 months ago
- asked 7 days ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
@kishore did my answer help?