fix: add lambda:InvokeFunction permission for CloudFront OAC #83
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
CDK's NatInstanceProviderV2 uses the `route` command in its default user data, which requires the net-tools package. However, Amazon Linux 2023 (the default AMI for NatInstanceProviderV2) doesn't have net-tools pre-installed, causing NAT instances to fail silently. This change provides custom user data that uses `ip route` instead of `route` to determine the default network interface, ensuring NAT functionality works correctly on AL2023. Reference: https://github.com/aws/aws-cdk/blob/main/packages/aws-cdk-lib/aws-ec2/lib/nat.ts
Starting October 2025, new Lambda function URLs require both lambda:InvokeFunctionUrl and lambda:InvokeFunction permissions when using CloudFront Origin Access Control (OAC). CDK's FunctionUrlOrigin.withOriginAccessControl only adds lambda:InvokeFunctionUrl, so new deployments would fail with 403 errors. Reference: https://docs.aws.amazon.com/lambda/latest/dg/urls-auth.html
konokenj
force-pushed
the
fix/cloudfront-oac-invoke-permission-v2
branch
from
2e3b8a8 to
eb5a5b1
Compare
Contributor
Author
|
Root cause on aws-cdk aws/aws-cdk#35872 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Starting October 2025, new Lambda function URLs require both
lambda:InvokeFunctionUrlandlambda:InvokeFunctionpermissions when using CloudFront Origin Access Control (OAC).Problem
CDK's
FunctionUrlOrigin.withOriginAccessControlonly addslambda:InvokeFunctionUrlpermission. New deployments after October 2025 would fail with 403 errors because thelambda:InvokeFunctionpermission is missing.Solution
Explicitly add
lambda:InvokeFunctionpermission usingCfnPermission.Reference
Dependencies
Please merge #81 first. This PR is based on that branch and will have no conflicts once #81 is merged.