Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature Request: Support OAC between CloudFront and Lambda #217

Open
davidw17 opened this issue Jul 10, 2024 · 3 comments
Open

Feature Request: Support OAC between CloudFront and Lambda #217

davidw17 opened this issue Jul 10, 2024 · 3 comments

Comments

@davidw17
Copy link

Our organisation are using cdk-nextjs and for our security requirements, it would be beneficial to have OAC implemented between Cloudfront and the Lambdas vs the current edge solution. Now that OAC is available, just raising a feature request item to get this implemented if possible.

See:

cdk-nextjs/src/NextjsDistribution.ts

Line 223 in 2d9c5a3

/**

@francoisdtm
Copy link

1; I would also prefer to have OAC instead of lambda@edge.
I can work on this change; do we want to keep the possibility to have lambda@edge, or move entirely to OAC ?

@davidw17
Copy link
Author

I think it would be handy to still be able to use lambda@edge as an option if possible.

@bestickley
Copy link
Collaborator

@francoisdtm, I don't think we can move to OAC because it does not support PUT or POST payloads. See the note below from the docs:

If you use PUT or POST methods with your Lambda function URL, your users must include the payload hash value in the x-amz-content-sha256 header when sending the request to CloudFront. Lambda doesn't support unsigned payloads.

If CloudFront allowed selecting different origins per method, then maybe we could for GETs but I don't think that's possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@francoisdtm @bestickley @davidw17