-
Notifications
You must be signed in to change notification settings - Fork 33
Add support for bare Lambda function URLs #21
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
Merged
Merged
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
[Lambdas can be called with an auto-generated URL](https://docs.aws.amazon.com/lambda/latest/dg/urls-invocation.html), which has a specific format similar but not identical to API Gateway.
Based on real-world testing.
Based on real-world testing.
Can one of the admins verify this patch? |
5 similar comments
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
@swift-server-bot test this please |
@tomerd I've added some test cases to this - any thoughts on getting this merged? |
@swift-server-bot test this please |
tomerd
approved these changes
Nov 1, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add request and response object models for invoking Lambda function URLs.
Motivation:
Instead of having to spin up (and pay for) API Gateway endpoints, Lambdas can spin up bare URLs for public access.
There are no existing request or response objects for these requests like there are for other event types.
Modifications:
FunctionURLRequest
object matching the request payload formatFunctionURLResponse
object matching the response payload formatThese payloads are very similar (but not identical to) API Gateway V1 requests, so this is mostly just forked from that and tested until it works with simple requests.
Note that I have only tested completely public endpoints, and cannot speak for the accuracy of the
Authorizer
sub-type.Result:
After this change, users will be able to write:
and then be able to simply invoke their Lambdas without API Gateway: