NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io
crates.io, #2350 most downloaded on crates.io
AWS Lambda Runtime
Latest stable
1.5.0
Last release 1 months ago
21 Oct 2026
Ships fairly regularly
a new release about every 5 weeks
Most releases are documented
notes for 33 of 44 stable releases
1 version withdrawn
withdrawn after publishing
8 years old
46 releases · first in 2018
Drag across the ruler to compare, or tap a release to open it.
log worker count and max concurrency
Your coding agent can read these notes before it upgrades. Set up the MCP server →
feat: add SnapStart support via SnapStartResource trait by @bnusunny in https://github.com/aws/aws-lambda-rust-runtime/pull/1150
Full Changelog: https://github.com/aws/aws-lambda-rust-runtime/compare/lambda_runtime-v1.2.1...lambda_runtime-v1.3.0
(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
*(api gateway)* deprecate authorizer-specific fields in ApiGatewayV2httpRequest
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. This lets you use the same handler for 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)
lambda_runtime - 1.1.1tenant_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)concurrency-tokio feature flag (#1067)Context instead of environment variables (#1067)lambda_http - 1.1.1concurrency-tokio feature flag with run_concurrent() and BoxCloneService for concurrent streaming responses (#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)concurrency-tokio feature flag with run_concurrent() and BoxCloneService for concurrent streaming responses (#1067)lambda_runtime_api_client - 1.0.2lambda-extension - 1.0.3aws_lambda_events - 1.1.1SqsBatchResponse and KinesisEventResponse (#1063)claims_to_add_or_override type in CognitoEventUserPoolsPreTokenGenV2 (#1100)ApiGatewayV2httpRequest (#1089)@alessandrobologna, @jlizen, @FullyTyped, @dap0am, @nstilt1, @raphael-theriault-swi, @abhu85, @flobz, @salmanmkc, @darklight3it, @lmammino, @andrew, @abhigya, @martinmadsen, @haroldsun
AWS Lambda Rust Runtime 1.1.0-rc1 adds multi-tenancy support via tenant_id in Context and experimental concurrent execution through Lambda Managed Ins
AWS Lambda Rust Runtime 1.1.0-rc1 adds multi-tenancy support via tenant_id in Context and experimental concurrent execution through Lambda Managed Instances via worker pools. Updates minimum Rust to 1.84.0.
Concurrent execution is currently experimental and should not be used for production workloads at this time.
• MSRV: Updated minimum supported Rust version from 1.82.0 to 1.84.0 • X-Ray Tracing: X-Ray trace ID now sourced from Context instead of environment variables • Cargo Resolver: Updated to resolver version 3 with MSRV awareness
• Authentication: Resolved auth issue in integration tests • Worker Isolation: Enhanced worker supervision and error handling for concurrent execution
• Automated Releases: Added release-plz configuration for automated version management • Enhanced Testing: Improved RIE (Runtime Interface Emulator) testing with LMI support • CI Updates: Updated GitHub Actions workflows for new features
• Updated reqwest from 0.12.5 to 0.13.1 • Various npm package updates in examples
• lambda-runtime: 1.0.2 → 1.1.0-rc1 • lambda-http: 1.0.2 → 1.1.0-rc1
• lambda-events: 1.0.2 → 1.0.3 • lambda-extension: 1.0.1 → 1.0.2 • lambda-runtime-api-client: 1.0.1 → 1.0.2
None. All new features are additive or behind feature flags.
• Tenant ID: Access via context.tenant_id (optional field, no migration required) • Concurrent Execution: Enable experimental-concurrency feature and use run_concurrent() instead of run() • MSRV: Ensure Rust 1.84.0 or later for compilation
Full Changelog: https://github.com/aws/aws-lambda-rust-runtime/compare/v1.0.2...v1.1.0-rc1
concurrency-tokio feature flag (#1067)This is a minor bug fix release.
This is a minor bug fix release.
SqsBatchResponse and KinesisEventResponse by @lmammino in https://github.com/aws/aws-lambda-rust-runtime/pull/1063Full Changelog: https://github.com/aws/aws-lambda-rust-runtime/compare/v1.0.1...v1.0.2
Nothing published for this version
Today, AWS Lambda is promoting Rust support from Experimental to Generally Available. This means you can now use Rust to build business-critical serve
Today, AWS Lambda is promoting Rust support from Experimental to Generally Available. This means you can now use Rust to build business-critical serverless applications, backed by AWS Support and the Lambda availability SLA.
Full Changelog: https://github.com/aws/aws-lambda-rust-runtime/compare/v0.8.0...v1.0
fix(semver): bump lamda-http to 0.16.0 due to breaking change in dependency, aws_lambda_events by @jlizen in https://github.com/awslabs/aws-lambda-rus…
0.16.0 due to breaking change in dependency, aws_lambda_events by @jlizen in https://github.com/awslabs/aws-lambda-rust-runtime/pull/1025AlbTargetGroupRequest::query_string_parameters value to string by @DiscreteTom in https://github.com/awslabs/aws-lambda-rust-runtime/pull/955#1013
lambda-http : Added StreamAdapter API. This allows adding layers to lambda runtime (ie, prior to it converting a request from LambdaEvent<LambdaRequest> to a http Request, or the http request back to a lambda response). Previously the streaming API only supported layers on the http server. This is useful for eg adding otel layers that wrap the lambda conversion.examples: new examples for simple lambda-http streaming, and streaming with open-telemetryFull Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/lambda-runtime-0.14.3...lambda
fix(ci): cut run-integration-test.yml over to "mlugg/setup-zig@v2", clippy fixes by @jlizen in https://github.com/awslabs/aws-lambda-rust-runtime/pull
String Panic Messages by @George-lewis in https://github.com/awslabs/aws-lambda-rust-runtime/pull/962Full Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/lambda-runtime-0.14.2...lambda-runtime-0.14.3
feat: derive Deserialize, Clone, PartialEq, Eq for MetadataPrelude by @DiscreteTom in https://github.com/awslabs/aws-lambda-rust-runtime/pull/956
Full Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/lambda-runtime-0.14.1...lambda-runtime-0.14.2
feat(ci): build and check rustdocs for warnings; fix(docs): add missing cfg flag to allow displaying features on doc.rs, fix various warnings by @jliz
Full Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/lambda-runtime-0.14.0...lambda-runtime-0.14.1
Release runtime 0.14.0 with graceful shutdown hook
Release runtime 0.14.0 with graceful shutdown hook
lambda-runtime-api-client 0.12.0 lambda-runtime 0.14.0 lambda-http 0.15.0 lambda-extesnion 0.12.0
Full Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/lambda-events-0.16.0...lambda-runtime-0.14.0
Nothing published for this version
Make child-spans work as expected when using the lambda-runtime by @TethysSvensson in https://github.com/awslabs/aws-lambda-rust-runtime/pull/896
Full Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/lambda-runtime-0.11.3...lambda-runtime-0.12.0
Nothing published for this version
Nothing published for this version
Always export the _X_AMZN_TRACE_ID env variable. by @calavera in https://github.com/awslabs/aws-lambda-rust-runtime/pull/850
Full Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/lambda-runtime-0.11.0...lambda-runtime-0.11.1
feat: Implement RFC for layering of runtime by @borchero in https://github.com/awslabs/aws-lambda-rust-runtime/pull/845
Full Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/lambda-runtime-0.10.0...lambda-runtime-0.11.0
Allow error response customization by @kikuomax in https://github.com/awslabs/aws-lambda-rust-runtime/pull/828
Full Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/lambda-runtime-0.9.1...lambda-runtime-0.10.0
Nothing published for this version
Nothing published for this version
Fix transitive dependency version of lambda_runtime. by @calavera in https://github.com/awslabs/aws-lambda-rust-runtime/pull/723
Full Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/lambda-runtime-0.8.3...lambda-runtime-0.9.0
Refactor Lambda response streaming. by @bnusunny in https://github.com/awslabs/aws-lambda-rust-runtime/pull/696
Full Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/lambda-http-0.8.2...lambda-runtime-0.8.3
Nothing published for this version
Provide context when deserialization fails. by @calavera in https://github.com/awslabs/aws-lambda-rust-runtime/pull/640
Full Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/v0.8.0...lambda-runtime-0.8.1
Fix logs processor example by @mattbajorek in https://github.com/awslabs/aws-lambda-rust-runtime/pull/588
http::request::Parts by @dcormier in https://github.com/awslabs/aws-lambda-rust-runtime/pull/607Full Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/v0.7.3...v0.8.0
Update DynamoDB example to use a shared client. by @calavera in https://github.com/awslabs/aws-lambda-rust-runtime/pull/582
Context::deadline(&self) -> SystemTime by @dcormier in https://github.com/awslabs/aws-lambda-rust-runtime/pull/583Full Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/v0.7.2...v0.7.3
Added IntoResponse implementation for (StatusCode, IntoResponse) by @mustafasegf in https://github.com/awslabs/aws-lambda-rust-runtime/pull/573
Full Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/v0.7.1-runtime...v0.7.2
Nothing published for this version
Check that lambda_https inner service is ready before calling it by @dcormier in https://github.com/awslabs/aws-lambda-rust-runtime/pull/538
lambda_https inner service is ready before calling it by @dcormier in https://github.com/awslabs/aws-lambda-rust-runtime/pull/538aws_lambda_events dependency by @dcormier in https://github.com/awslabs/aws-lambda-rust-runtime/pull/541Adapter to be .boxed() by @dcormier in https://github.com/awslabs/aws-lambda-rust-runtime/pull/540Full Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/v0.6.1...v0.7.0
Fix paths with spaces in HTTP requests. by @calavera in https://github.com/awslabs/aws-lambda-rust-runtime/pull/516
with_request_context to RequestExt by @sgasse in https://github.com/awslabs/aws-lambda-rust-runtime/pull/523Future it returns by @fermanjj in https://github.com/awslabs/aws-lambda-rust-runtime/pull/521Full Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/v0.6.0...v0.6.1
Update Rust edition to 2021 in all crates: The minimum supported Rust version is 1.58.1
Full Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/v0.5.1...v0.6.0
Fix issue parsing WebSocket requests. by @calavera in https://github.com/awslabs/aws-lambda-rust-runtime/pull/433
Full Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/v0.5.0...v0.5.1
build: BREAKING CHANGE: upgrade tracing-[error|subscriber] by @seanpianka in https://github.com/awslabs/aws-lambda-rust-runtime/pull/358
README.md: invoke lambda function with raw-in-base64-out by @david-perez in https://github.com/awslabs/aws-lambda-rust-runtime/pull/385README.md: add newline to end of file by @david-perez in https://github.com/awslabs/aws-lambda-rust-runtime/pull/386Full Changelog: https://github.com/awslabs/aws-lambda-rust-runtime/compare/v0.4.1...v0.5.0
Set _X_AMZN_TRACE_ID environment variable for x-ray #341
New:
Nothing published for this version
Removal of the 'static lifetime bound requirements on both lambda-http and lambda-runtime to allow for shared resources that exist in between invocati
New:
'static lifetime bound requirements on both lambda-http and lambda-runtime to allow for shared resources that exist in between invocations that land on the same Lambda Sandbox. See: https://github.com/awslabs/aws-lambda-rust-runtime/pull/333 and https://github.com/awslabs/aws-lambda-rust-runtime/pull/319Heavy restructuring was done in order to simplify the runtime and to enable asynchronous handlers by default.
New: Almost everything!
Heavy restructuring was done in order to simplify the runtime and to enable asynchronous handlers by default.
The lambda crate has been renamed to lambda_runtime, and the original lambda_runtime has been removed from the project. lambda_http remains the same.
The lambda_http crate now supports API Gateway HTTP API Lambda triggers.
Both lambda_runtime and lambda_http have noteworthy, breaking API changes. The following is a rough approximation of what a transition to the new runtime API will be:
note: the runtime is based on
std::future::Futurebased and relies on Tokio via Hyper.
→ main.rs
-use lambda_runtime::{error::HandlerError, lambda, Context};
+use lambda_runtime::{handler_fn, Context};
use serde_json::Value;
+type Error = Box<dyn std::error::Error + Sync + Send + 'static>;
-fn main() {
- lambda!(handler)
+#[tokio::main]
+async fn main() -> Result<(), Error> {
+ lambda_runtime::run(handler_fn(handler)).await?;
+ Ok(())
}
-fn handler(
- event: Value,
- _: Context,
-) -> Result<Value, HandlerError> {
+async fn handler(
+ event: Value,
+ _:Context
+) -> Result<Value, Error> {
Ok(event)
}
Please refer to the examples in (lambda-runtime/examples; lambda-http/examples) for more detail.
Nothing published for this version
New: We created `lambda_runtime_core` crate that implements the runtime's main loop and supports handlers that accept and return Vec .
lambda_runtime_core crate that implements the runtime's main loop and supports handlers that accept and return Vec<u8>. (#53)lambda_runtime crate is a wrapper on top of the lambda_runtime_core handler (#53).lambda_http crate, which enables support for API Gateway or ALB requests, treating them as Request structs from the http crate (#18 by @softprops).lambda_runtime_errors crate introduces the LambdaErrorExt trait that enables the ability to specify custom errorType values for the Lambda Runtime API. The change also includes a companion derive crate that makes it easy to automatically generate LambdaErrorExt implementations for crate-local error types (#63).Nothing published for this version
One column per quarter.