Expose AWS Lambda execution context for Vapor logging#196
Merged
taylorotwell merged 2 commits intolaravel:2.0from Dec 19, 2025
Merged
Expose AWS Lambda execution context for Vapor logging#196taylorotwell merged 2 commits intolaravel:2.0from
taylorotwell merged 2 commits intolaravel:2.0from
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
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.
Expose AWS Lambda execution context for Vapor logging
Overview
Debugging production issues in Vapor can be difficult when attempting to correlate application logs with their corresponding AWS CloudWatch entries.
This change introduces a small helper trait that exposes commonly needed AWS Lambda execution metadata directly from the environment, including the request ID, function name, function version, and CloudWatch log identifiers.
Motivation
Providing easy access to this context allows logs and exceptions to include Lambda-specific identifiers, making it significantly easier to locate the relevant log stream in CloudWatch and trace individual requests during debugging.
Details
The helper is lightweight, has no external dependencies, and can be used wherever logging or error reporting occurs. It does not modify existing behavior and introduces no breaking changes.
Benefits