Update lambda to v1.1.1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
lambda_http	dependencies	minor	1.0.2 → 1.1.1
lambda_runtime	dependencies	minor	1.0.2 → 1.1.1

---

Release Notes

aws/aws-lambda-rust-runtime (lambda_http)

v1.1.1: v1.1.1

Compare Source

Thank you to all the contributors who helped make this release possible. We appreciate your time, effort, and passion for the Rust Lambda community. ❤️

Lambda Managed Instances

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)

Added

• (lambda-managed-instances) log non-2xx Lambda Runtime API responses with status and body (#​1109)
• tenant ID propagation for multi-tenant Lambda use cases. The 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)
• Add builder pattern support for event response types (#​1090)

Fixed

• (test) fix test_concurrent_structured_logging_isolation (#​1121)

Changed

• MSRV updated from 1.82.0 to 1.84.0, enabled MSRV-aware resolver (#​1078)
• X-Ray trace ID now sourced from Context instead of environment variables (#​1067)

Other

• (lambda-managed-instances) add tokio_unstable to known cfgs to avoid linter warns (#​1095)
• (lambda-managed-instances) verify request-ID isolation in concurrent exec (#​1086)
• (lambda-managed-instances) warn on run() with AWS_LAMBDA_MAX_CONCURRENCY, rename feature experimental-concurrency to concurrency-tokio (#​1095)
• Introducing Harness Testing (#​1103)

1.1.0-rc1 - 2026-02-04

Added

• (lambda-managed-instances) Lambda Managed Instances support via concurrency-tokio feature flag (#​1067)
• (lambda-managed-instances) tenant ID propagation for multi-tenant Lambda use cases (#​1082)

Changed

• MSRV updated from 1.82.0 to 1.84.0, enabled MSRV-aware resolver (#​1078)
• X-Ray trace ID now sourced from Context instead of environment variables (#​1067)

---

lambda_http - 1.1.1

Added

• (lambda-managed-instances) Lambda Managed Instances support via concurrency-tokio feature flag with run_concurrent() and BoxCloneService for concurrent streaming responses (#​1067)
• Add builder pattern support for event response types (#​1090)

Changed

• MSRV updated from 1.82.0 to 1.84.0, enabled MSRV-aware resolver (#​1078)

Other

• (lambda-managed-instances) add tokio_unstable to known cfgs to avoid linter warns (#​1095)
• (lambda-managed-instances) warn on run() with AWS_LAMBDA_MAX_CONCURRENCY, rename feature experimental-concurrency to concurrency-tokio (#​1095)
• (lambda-managed-instances) verify request-ID isolation in concurrent exec (#​1086)
• Introducing Harness Testing (#​1103)
• disable default features of lambda-runtime (#​1093)
• (deps) update axum-extra requirement from 0.10.2 to 0.12.5 (#​1079)

1.1.0-rc1 - 2026-02-04

Added

• (lambda-managed-instances) Lambda Managed Instances support via concurrency-tokio feature flag with run_concurrent() and BoxCloneService for concurrent streaming responses (#​1067)

Changed

• MSRV updated from 1.82.0 to 1.84.0, enabled MSRV-aware resolver (#​1078)

---

lambda_runtime_api_client - 1.0.2

Added

• (lambda-managed-instances) API client connection pooling for concurrent requests (#​1067)

Changed

• MSRV updated from 1.82.0 to 1.84.0, enabled MSRV-aware resolver (#​1078)

---

lambda-extension - 1.0.3

Added

• Make Telemetry API log record type generic (#​1098)

1.0.2 - 2026-01-06

Changed

• MSRV updated from 1.82.0 to 1.84.0, enabled MSRV-aware resolver (#​1078)

---

aws_lambda_events - 1.1.1

Added

• (lambda-events) support X509 custom authorizer in IoT events (#​1114)
• (lambda-events) add Control Tower lifecycle events module (#​1107)
• (lambda-events) add VPC Lattice event structures (#​1036)
• Add builder pattern support for event response types (#​1090)

Fixed

• (sns) support SubscriptionConfirmation and UnsubscribeConfirmation message types (#​1102)
• (lambda-events) claims_to_add_or_override type in CognitoEventUserPoolsPreTokenGenV2 (#​1100)

Other

• (lambda-events) deprecate authorizer-specific fields in ApiGatewayV2httpRequest (#​1089)

1.0.3 - 2026-01-06

Changed

• MSRV updated from 1.82.0 to 1.84.0, enabled MSRV-aware resolver (#​1078)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.