Feature Request - Support for Application Load Balancer

[vijaychd]

• Framework version: XX
• Implementations: Jersey / Spring / Spring Boot / Spark
  Spring boot

Scenario

Calling Lambda Function thru Application Load Balancer

Expected behavior

Application load balancer is recently added as trigger for lambda function. it would be nice to support that for java container in lambda.

Actual behavior

Steps to reproduce

Full log output

[sapessi]

Thanks for the feedback @vijaychd - we'll definitely look at this for the next release

[sapessi]

@vijaychd I have committed ALB support in the 1.3-SNAPSHOT version in the core branch of this repository. Could you run a few tests with it? Please note that it only supports the multi-value headers feature

[vijaychd]

Thanks @sapessi
Initial test looks good to invoke the rest controller. I added /lambda-demo-api/rs/* to the controller and configured ALB for /lambda-demo-api/*. Call to api methods worked. .

[vijaychd]

need to figure out how /health and /swagger-ui.html would work. @sapessi Can that be supported?

[sapessi]

Technically it should work @vijaychd, although I have never tried. What framework are you testing with?

[vijaychd]

Spring boot. /health worked after i changed the endpoint. /v2/api-docs doesn't.

[sapessi]

Any chance you have a github repo I can use to try and replicate quickly?

[vijaychd]

Nope.
For spring boot app, usually the context path is set as
server.servlet.context-path=/lambda-demo-api

I think with ApiGateway proxy it was always getting set as /. Is it something you can add to override the context path for container.

So i will use same context on the ALB, then all endpoints should work

[sapessi]

Resolving in preparation for 1.3 release

[vijaychd]

By setting below, /health and /v2/api-docs worked fine.
handler = SpringBootLambdaContainerHandler.getAwsProxyHandler(Application.class, profiles);
handler.getContainerConfig().setServiceBasePath("/lambda-demo-api");
handler.getContainerConfig().setStripBasePath(true);