NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io · #2306 most downloaded on crates.io
AWS Lambda Runtime
Last release 1 months ago
02 Sep 2026
Ships fairly regularly
a new release about every 5 weeks
Rarely documented
notes for 7 of 43 stable releases
1 version withdrawn
withdrawn after publishing
8 years old
45 releases · first in 2018
add lambda-runtime-invocation-id header
feat: add SnapStart support via SnapStartResource trait by @bnusunny in #1150
Full Changelog: lambda_runtime-v1.2.1...lambda_runtime-v1.3.0
One column per quarter.
(deps) update opentelemetry-semantic-conventions requirement
Add VPC Lattice as an upstream source for lambda-http
remove non exhaustive from time structs
fix handling of null groupConfiguration
Thank you to all the contributors who helped make this release possible. We appreciate your time, effort, and passion for the Rust Lambda community. ❤
Thank you to all the contributors who helped make this release possible. We appreciate your time, effort, and passion for the Rust Lambda community. ❤️
The runtime now supports Lambda Managed Instances via the concurrency-tokio feature flag (previously experimental-concurrency). Lambda Managed Instances allow multiple concurrent requests to be processed within a single execution environment. When AWS_LAMBDA_MAX_CONCURRENCY is set, the runtime spawns multiple independent long-poll workers to handle concurrent invocations. If the env var is unset or <= 1, it falls back to sequential behavior automatically — so the same handler works on both classic Lambda and Lambda Managed Instances. (#1067)
[dependencies]
lambda_runtime = { version = "1.1", features = ["concurrency-tokio"] }
lambda_runtime::run_concurrent(service_fn(my_handler)).await?;
For a complete working example, see examples/basic-lambda-concurrent. For detailed guidance on building functions for multi-concurrency, including shared state patterns and database connection pools, see the Rust runtime for Lambda Managed Instances documentation.
We would like also to involve the community in a broader discussion about improving our approach on multiconcurrency. You can find the discussion in (#1120)
tenant_id is available in the context.tenant_id field (Option<String>) and is automatically extracted from the lambda-runtime-aws-tenant-id header when present (#1082)Context instead of environment variables (#1067)tokio_unstable to known cfgs to avoid linter warns (#1095)run() with AWS_LAMBDA_MAX_CONCURRENCY, rename feature experimental-concurrency to concurrency-tokio (#1095)*(lambda-managed-instances)* Lambda Managed Instances support via concurrency-tokio feature flag
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →