aws-serverless-java-container | Java wrapper to run Spring | REST library

I have a spring boot app that I am trying to boot as a Lambda with the aws-serverless-java-container-spring library, and upon startup I get the error:

I am new to aws lambda and I am moving my spring boot 2.x based project to lambda.But I am struggling with lambda cold-start and warm-up. I tried a few things mentioned in this link:https://github.com/awslabs/aws-serverless-java-container/wiki/Quick-start---Spring-Boot, but still the application takes around 45 secs to start.

Things I tried:

1. Async initialization from the above link. It did help a bit but not enough.

2. Skip the Init phase of the lambda. It helped reduce almost 8 secs.

3. Provisioned concurrency but as far as I could see, it is not helping either. When I saw the logs, the spring context is getting initialized every time, if any request comes after an interval of 15-20 mins.

The response time of my lambda in different scenarios is:

I'm using aws-serverless-java-container to wrap a Jersey service in a AWS Lambda. I decided to use function alias to have a "test" and "prod" stage that eventually points to different versions of the lambda function.

I need to select some properties in a .properties file based on that alias, basically because I need to talk to a "test" or "prod" DB or use a different endpoint to invoke an external web service.

For such purpose I need to invoke the method getInvokedFunctionArn of the Context object. Unfortunately the Jersey resource is not aware of such context by default.

Below a sample resource:

I want to configure aws lambda in my existing Spring boot project. In my project i am using lombok, kafka consumer, and microservice. I follow steps at:

https://github.com/awslabs/aws-serverless-java-container/wiki/Quick-start---Spring-Boot

I added dependency:

I just tried to run a Spring Boot application on AWS Lambda using the following article: https://github.com/awslabs/aws-serverless-java-container/wiki/Quick-start---Spring-Boot

Basic requests are just working fine, but sending files seems to cause problems. Running the application locally works fine:

I want to develop a new java webservice to be deployed on AWS Lambda, but I also want to be able to easily test it.

My idea is to code my webservice using Jersey and be able to compile it into a war file, so I can test it localy and also be able to compile it into a jar for the Serverless Java container from AWS.

My first thought was to create 2 modules on IntelliJ IDEA 2017.3 Ultimate, one for the warand one for the jar, all using Maven, with the 2 modules sharing the same code base for the Jersey REST Resources (the webservice classes). But unfortunately I am too new to IntelliJ IDEA and I can't put this to work.

Is there a way to achieve this?

I am using the AWS labs' serverless container (https://github.com/awslabs/aws-serverless-java-container) to handle the lambda entrypoint and response for a lambda that returns HTML. It appears that it calls the lambda and returns the HTML just fine from the lambda. However, API Gateway then throws a fit processing the response. I am using the API Gateway as a proxy, not configuring individual endpoints.

Wed Jun 21 20:53:29 UTC 2017 : Endpoint response body before transformations: --- statusCode: 200 headers: Content-Type: "text/html" body: "\r\n\r\nhttp://www.w3.org/1999/xhtml\"\r\n \ \ lang=\"en\">\r\n \r\n \r\n \ \ Page Title\r\n \r\n \r\n \ \ \r\n \r\n\ \ \r\n \r\n ... [TRUNCATED] Wed Jun 21 20:53:29 UTC 2017 : Endpoint response headers: {x-amzn-Remapped-Content-Length=0, x-amzn-RequestId=adb2b101-56c3-11e7-afc6-8383d836980f, Connection=keep-alive, Content-Length=17551, Date=Wed, 21 Jun 2017 20:53:29 GMT, X-Amzn-Trace-Id=root=1-594adcc9-6987c6ed102696c505538b02;sampled=0, Content-Type=application/octet-stream} Wed Jun 21 20:53:29 UTC 2017 : Execution failed due to configuration error: Malformed Lambda proxy response Wed Jun 21 20:53:29 UTC 2017 : Method completed with status: 502

As you can see from the logs, the AWS own Java object, AwsProxyResponse, properly wraps the HTML content how AWS coded it. You see it returning the proper body and text/html headers. It seems API Gateway then blows up handling a response from AWS's own response.

How do I get AWS Gateway to properly handle the response when the response form the lambda is Content-Type: test/html?