-
Notifications
You must be signed in to change notification settings - Fork 549
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
feature: Support VPC Lattice integration as frontend service #639
Comments
Thanks for raising this. As we are about to integrate the Lambda events lib, I created aws/aws-lambda-java-libs#443. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To help us debug your issue fill in the basic information below using the options provided
This is a feature request to support VPC Lattice integration similar to API GW and ALB.
Serverless Java Container version:
eg. 1.5
For both v1 (Spring Boot 2) and v2 (Spring Boot 3.x). Ideally, v2 should be good if v1 is not prioritized.
Implementations:
Jersey / Spring / Spring Boot / Spring Boot 2 / Spark
SpringBoot
Framework version:
eg SpringBoot 2.2.6.RELEASE
Spring Boot 3.x (if feasible, Spring Boot 2)
Frontend service:
REST API / HTTP API / ALB
VPC Lattice
Deployment method:
eg SAM, Serverless Framework, Console
N/A
Scenario
Describe what you are trying to accomplish
Support VPC Lattice as the frontend service. The incoming payload for VPC Lattice is different than API GW. This addition will be a new
RequestSource
, therefore needing a variety of changes related toAwsProxyRequest
,AwsProxyResponse
, request POJO, response POJO, request reader, response writer, security context, and moreExpected behavior
Describe how you would expect the application to behave
A Spring Boot application running on a Lambda function should work with VPC Lattice as a request source.
Actual behavior
Describe what you are seeing instead
Currently, VPC Lattice is not supported.
The text was updated successfully, but these errors were encountered: