AWS Lambda: Add support for Lambda Durable Functions #137
+292
−1
Conversation
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
Add Lambda Durable Functions support with: - durableConfig property in serverless.yml (executionTimeout, retentionPeriodInDays) - Auto-enable versioning when durableConfig is present (required for qualified ARNs) - CloudFormation DurableConfig property generation - Deploy function support for durable configuration Durable functions enable long-running workflows that can span multiple Lambda invocations with automatic state management and checkpointing.
Automatically attach AWSLambdaBasicDurableExecutionRolePolicy managed policy to Lambda execution roles when durableConfig is present. This grants the necessary permissions for durable function operations including checkpoint management and execution state access.
Add --durable-execution-name option to serverless invoke command: - Enables idempotent invocations with unique execution names - Supports both synchronous and asynchronous durable invocations - Execution names must be 1-64 chars (alphanumeric, hyphens, underscores) - Repeated invocations with same name return cached results Usage: serverless invoke -f myFunc --durable-execution-name order-12345
Document durable functions feature including: - Configuration properties (executionTimeout, retentionPeriodInDays) - Supported runtimes (Node.js 22+, Python 3.13+) - IAM permissions and managed policy - Invoke command --durable-execution-name option - Usage examples and limitations
mnapoli
reviewed
Jan 22, 2026
Contributor
|
This looks very clean, I added a minor comment but honestly the rest looks good to me 👍 |
Move durable execution example to a more appropriate location in the invoke.md documentation and update example to include contextPath parameter.
Author
|
@mnapoli moved that section below local invocation examples and used similar arguments for clarity |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
On December 2nd, 2025, AWS introduced Durable Lambda Executions, enabling long-running, fault-tolerant workflows without custom chaining, self-invocation, or continuation persistence (announcement).
This PR adds support for Lambda Durable Functions :
Features:
durableConfigproperty withexecutionTimeout(1-31536000 seconds) andretentionPeriodInDays(1-90 days)durableConfigis present (required for qualified ARNs)AWSLambdaBasicDurableExecutionRolePolicy)--durable-execution-nameoption for idempotent invocationsUsage: