-
Notifications
You must be signed in to change notification settings - Fork 120
Use Lambda URL as CloudFront origin #368
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.
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
base: master
Are you sure you want to change the base?
Conversation
|
Uploaded some changes @mnapoli I didn't managed to pass ts-lint checks on |
|
@mnapoli Can you review last changes? |
|
Hello @kevincerro, there is any update on this? This change will for sure reduce costs. |
Hello, no changes since last comment. I've a forked version of lift package with this PR changes => |
|
@mnapoli Sorry for reviving an old PR, but what is pending for this to get to upstream? |
|
Hey! No problem with the ping, I'm actually tracking this initiative in brefphp/bref#1625 (comment) and I've posted a new update. TL/DR: that wouldn't work when using a VPC 😢 Also I've asked around and got no signal from AWS teams that they're considering adding support for VPCs. |

Closes brefphp/bref#1625
This PR is a draft for using Lambda URL as CloudFront origin domain
Please review and write your opinion about how we must handle logic about this
https://mywebsite.com/?SampleArg=Ky4gdyRYLiA0JSAMOWx9Iw==
X-Amzn-Errortype = InvalidQueryStringExceptionPending:
Configuration changes
Before
After
Example Symfony project using CloudFront + Lambda URL
https://docs.block2code.com/components
Screenshots