chore: AWS Lambda Adapter: CloudFront, S3 & Function URL

[ptz0n]

Overview

What is it?

• [x] Feature / enhancement
• [ ] Bug
• [x] Docs / tests / types / typos

Description

A more performant and robust AWS Lambda adapter, using S3 and Lambda Function URL origins behind CloudFront.

Use cases and why

• Simple and flexible stack for deploying Qwik to AWS.
• Less overhead, removing API Gateway.
• Serving static files from S3.

Checklist:

• [ ] My code follows the developer guidelines of this project
• [ ] I have performed a self-review of my own code
• [ ] I have made corresponding changes to the documentation
• [ ] Added new tests to cover the fix / functionality

[netlify[bot]]

👷 Deploy request for qwik-insights pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	65a55baf58f4f9f54f4b843fb99922609a098fb6

[gioboa]

@ptz0n is it still valid or is it abandoned?

[ptz0n]

Still valid 👍🏼 Have a few improvements in store.

[PatrickJS]

@ptz0n let me know when it's good

[PatrickJS]

@ptz0n lets pair on this

[gioboa]

@PatrickJS @ptz0n Are you still working on this or is it abandoned?

[netlify[bot]]

‼️ Deploy request for qwik-insights rejected.

Name	Link
🔨 Latest commit	a57d35841d9a25b211f0b97fd4e9ed173ced204d

[PatrickJS]

abandoned. still planned when I have time. we deployed a qwik app a few different ways on aws I just need to document it

[gioboa]

Ok, no worries. I close this PR and you can start from scratch with a new PR. I mean, you can always look at this PR to copy paste things in the new one. 😉