Support for Lambda Function URLs

[deki]

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

[msailes]

In AwsProxyHttpServletRequestReader

https://github.com/awslabs/aws-serverless-java-container/blob/6d88f503c02988cc947743bad78d965d8aa0b5a2/aws-serverless-java-container-core/src/main/java/com/amazonaws/serverless/proxy/internal/servlet/AwsProxyHttpServletRequestReader.java#L47-L49

The condition fails because when a request from a function url is mapped to a AwsProxyRequest type getHttpMethod() returns null.

[deki]

HttpApiV2ProxyHandler along with HttpApiV2ProxyRequest needs to be used, than it works fine. Will change docs and samples.

[msailes]

If I use the example request from the developer guide

{
// removed for brevity
  "requestContext": {
    "accountId": "123456789012",
    "apiId": "<urlid>",
    "authentication": null,
    "authorizer": {
        "iam": {
                "accessKey": "AKIA...",
                "accountId": "111122223333",
                "callerId": "AIDA...",
                "cognitoIdentity": null,
                "principalOrgId": null,
                "userArn": "arn:aws:iam::111122223333:user/example-user",
                "userId": "AIDA..."
        }
    },
    "domainName": "<url-id>.lambda-url.us-west-2.on.aws",
    "domainPrefix": "<url-id>",
    "http": {
      "method": "POST",
      "path": "/my/path",
      "protocol": "HTTP/1.1",
      "sourceIp": "123.123.123.123",
      "userAgent": "agent"
    },
// removed for brevity
}

Then I get the following error and a 502 http response.

com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "authentication" (class com.amazonaws.serverless.proxy.model.HttpApiV2ProxyRequestContext), not marked as ignorable (11 known properties: "apiId", "domainPrefix", "accountId", "authorizer", "requestId", "timeEpoch", "time", "stage", "domainName", "routeKey", "http"])
 at [Source: (ByteArrayInputStream); line: 21, column: 27] (through reference chain: com.amazonaws.serverless.proxy.model.HttpApiV2ProxyRequest["requestContext"]->com.amazonaws.serverless.proxy.model.HttpApiV2ProxyRequestContext["authentication"])

This is because HttpApiV2ProxyRequestContext is not ignoring fields that it doesn't recognise, in this case authentication.

To fix this we could add @JsonIgnoreProperties(ignoreUnknown = true) to the class so that Jackson ignores fields it doesn't recognise.

[VPatrny]

The fix mentioned above works for me. Thx!

public class StreamLambdaHandler implements RequestStreamHandler {
//    private static SpringBootLambdaContainerHandler<AwsProxyRequest, AwsProxyResponse> handler;
    private static SpringBootLambdaContainerHandler<HttpApiV2ProxyRequest, AwsProxyResponse> handler;

    static {
        try {
//            handler = SpringBootLambdaContainerHandler.getAwsProxyHandler(Application.class);
            handler = SpringBootLambdaContainerHandler.getHttpApiV2ProxyHandler(Application.class);

[astsiatsko]

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?

[deki]

@astsiatsko which framework are you using?

For Spring Boot 3 you have the possibility to use the new SpringDelegatingLambdaContainerHandler as described in https://github.com/aws/serverless-java-container/tree/main/samples/springboot3/alt-pet-store. This one supports both payload versions. More docs on this coming soon...

[astsiatsko]

@deki thanks! I am using spring boot 3.1.x. Thank you, I will give it a try and let you know asap.

[astsiatsko]

@deki One question - may I do sth like that?
SpringDelegatingLambdaContainerHandler.getContainerConfig().setInitializationTimeout(timeout);

[deki]

This is currently not implemented for this handler type. Please open a new issue describing your requirement and someone will look into it.

[astsiatsko]

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

mvc.service(httpServletRequest, httpServletResponse);

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?

[astsiatsko]

My endpoint signature:

@RequestMapping(path = "/w6/test/{uuid}/refresh", method = RequestMethod.GET, produces = MediaType.APPLICATION_JSON_VALUE)
    public ResponseEntity<TMaxmindResponse> refresh(
            @Parameter(description = "UUID of the order") @PathVariable("uuid") String uuid,
            @Parameter(description = "ID of the order(primary key)") @RequestParam("order_id") Long orderId,
            @Parameter(description = "tab") @RequestParam("tab") String tab
    )