feature: Support VPC Lattice integration as frontend service

未關閉
#639 1 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 1 天內回覆

@mbfreder 已經在處理了。

開始於 2024年3月19日。

評估

這個 Issue 還沒有評估資料。

描述

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 to AwsProxyRequest, AwsProxyResponse, request POJO, response POJO, request reader, response writer, security context, and more

Expected 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.

主要語言
Java
星號
1.6k
分支
575
平均合併
1 天 15 小時
30 天內合併 PR
12

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

aws/serverless-java-container 的其他 Issue

查看 aws/serverless-java-container 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。