feat: add multi-tenancy support via tenant ID propagation#631
Merged
Conversation
Extract tenant_id from the Lambda runtime context and forward it as the X-Amz-Tenant-Id header to the downstream web application. The header is only added when tenant_id is present in the context. Includes unit and integration tests for both present and absent tenant_id scenarios.
📊 Benchmark ComparisonBenchmark Details
|
tobixlea
approved these changes
Feb 16, 2026
licjun
approved these changes
Feb 16, 2026
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
3 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.
Summary
Adds multi-tenancy support to Lambda Web Adapter by propagating the
tenant_idfrom the Lambda runtime context as anX-Amz-Tenant-IdHTTP header to the downstream web application.Changes
tenant_idfrom the LambdaContext(populated from thelambda-runtime-aws-tenant-idruntime header)X-Amz-Tenant-Idheader when present; omit when absentHow it works
When the Lambda runtime includes a
tenant_idin the invocation context, the adapter automatically adds it as anX-Amz-Tenant-Idheader on the forwarded request. No configuration is needed — if the tenant ID is present, it's propagated; if not, the header is simply omitted.