feat(cloudfront): add NodejsEdgeFunction construct #36045
Draft
+1,585
−144
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
Adds NodejsEdgeFunction construct that combines EdgeFunction's cross-region deployment capabilities with NodejsFunction's TypeScript bundling via esbuild. This addresses the feature request in issue #12671 by providing a convenient way to deploy TypeScript Lambda@Edge functions without manual bundling. Key features: - Extends EdgeFunction for automatic us-east-1 deployment - Reuses NodejsFunction's prepareBundling utility for esbuild integration - Validates runtime is Node.js family only - Supports all NodejsFunction bundling options (minify, sourceMap, etc.) - Includes integration test with AWS API assertions Closes #12671
github-actions
bot
added
effort/medium
aws-cdk-automation
requested changes
Nov 13, 2025
Collaborator
There was a problem hiding this comment.
The pull request linter fails with the following errors:
❌ Features must contain a change to a README file.
If you believe this pull request should receive an exemption, please comment and provide a justification. A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed, add Clarification Request to a comment.
abidhasan-aws
force-pushed
the
add-nodejs-and-python-function-for-edge-lambda
branch
2 times, most recently
from
a1c0bb9 to
ba8fc32
Compare
Autofix incorrectly removed the helper functions (getRuntime, findLockFile, findEntry, findDefiningFile) and broke imports. Restored all functions and fixed import paths.
…ng logic The prepareBundling function and all helper functions already exist in aws-lambda-nodejs/lib/bundling-preparation. Use them directly instead of duplicating the code.
This was referenced Nov 15, 2025
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.
Issue # (if applicable)
Closes #12671
Reason for this change
Currently, there is no construct that automatically bundles TypeScript code for
Lambda@Edgefunctions.EdgeFunctionhandles cross-region deployment but requires pre-bundled JavaScript.This forces users manually bundle core before using EdgeFunction.
Description of changes
Introduces
NodejsEdgeFunctionconstruct that bundles TypeScript code forEdgeFunction, enabling automatic TypeScript compilation for Lambda@Edge deployments.Extracted bundling utility functions from
NodejsFunctioninto a shared module (function-helpers.ts) that bothNodejsFunctionandNodejsEdgeFunctionuse, eliminating code duplication while maintaining consistent bundling behavior.Before
After
Description of how you validated changes
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license