-
Notifications
You must be signed in to change notification settings - Fork 560
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
Support for Lambda Function URLs #460
Comments
In The condition fails because when a request from a function url is mapped to a |
HttpApiV2ProxyHandler along with HttpApiV2ProxyRequest needs to be used, than it works fine. Will change docs and samples. |
If I use the example request from the developer guide
Then I get the following error and a 502 http response.
This is because To fix this we could add |
The fix mentioned above works for me. Thx!
|
…id UnrecognizedPropertyException for Lambda Function URLs with IAM auth (#460)
Hey guys, thanks for this change. But is it possible to have ONE handler for all types of events? ALB, API_GW, functional url and so on? So far I see the ways how handlers are initialized are way different and it seems that I have to keep 2X resources in lambda to keep 2 types of handlers in memory - one for ALB, API_GW and another for FURL. Is there a way to share a single handler for all types of events? |
@astsiatsko which framework are you using? For Spring Boot 3 you have the possibility to use the new |
@deki thanks! I am using spring boot 3.1.x. Thank you, I will give it a try and let you know asap. |
@deki One question - may I do sth like that? |
This is currently not implemented for this handler type. Please open a new issue describing your requirement and someone will look into it. |
Hey guys. Sorry for asking but are you sure your approach works for complex urls with query and path parameters? I use SpringDelegatingLambdaContainerHandler in complex enterprise lambda function and on
I constantly get error 400 and /error context path. I copied SpringDelegatingLambdaContainerHandler to the same package in my app and added logs. In my query I have two query params and path param. In aws logs I see it starts spring boot but I always get 400 and /error in logs instead of my url. I use ALB event, but it doesn't work for others either. Can you help please? |
My endpoint signature:
|
Hey guys. I think you have a problem with query parameters procession - I changed all my parameters to path params and it worked just fine. |
Here is the stack trace I have. May be it helps
|
@astsiatsko good catch, would you mind opening a new issue for it? This is unrelated to Lambda Function URLs. We'll include a fix in the next release. |
@deki you can assign it to me |
Recently Lambda Function URLs were released: https://aws.amazon.com/blogs/aws/announcing-aws-lambda-function-urls-built-in-https-endpoints-for-single-function-microservices/
Those requests fail with:
com.amazonaws.serverless.exceptions.InvalidRequestEventException: The incoming event is not a valid request from Amazon API Gateway or an Application Load Balancer
The text was updated successfully, but these errors were encountered: