New serverless pattern - Step Function to durable Lambda function#2975
Open
sin-ak wants to merge 2 commits intoaws-samples:mainfrom
Open
New serverless pattern - Step Function to durable Lambda function#2975sin-ak wants to merge 2 commits intoaws-samples:mainfrom
sin-ak wants to merge 2 commits intoaws-samples:mainfrom
Conversation
added 2 commits
February 25, 2026 14:24
embano1
reviewed
Mar 2, 2026
|
|
||
| ## When to Use This Pattern | ||
| Use this pattern when: | ||
| - Your Lambda function execution time exceeds 15 minutes and must be orchestrated by Step Functions |
Contributor
There was a problem hiding this comment.
nit: the 15min is not a differentiator for SFN vs DF - I think the reasons for combining both are 1/ existing SFN experience/workflows and 2/ simplifying Lambda orchestration logic e.g., reducing the number of functions, calls, and complexity when building hybrid workflows
|
|
||
| Important: this application uses various AWS services and there are costs associated with these services after the Free Tier usage - please see the [AWS Pricing page](https://aws.amazon.com/pricing/) for details. You are responsible for any AWS costs incurred. No warranty is implied in this example. | ||
|
|
||
| ## When to Use This Pattern |
Contributor
There was a problem hiding this comment.
note: I'm reading this section as "when to use this serverless pattern" but somehow the section seems to be more a DF vs SFN - consider streamlining this section to match the use case and refer to the user guide for more guidance
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #, if available: #2976
Description of changes:
This pattern demonstrates how to integrate AWS Lambda durable functions into an AWS Step Functions workflow. This pattern covers both the synchronous invocation (using default Request Response pattern) and asynchronous invocation (using the Step Function Wait for Callback with Task Token integration pattern) of the durable Lambda function. It addresses the challenge of running long-running Lambda functions (beyond 15 minutes) within a Step Functions orchestration, using asynchronous invocation and durable checkpointing.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.