Aws-app-mesh-roadmap: Feature Request: Enable configuring Proxy Protocol in Virtual Gateway
If you want to see App Mesh implement this idea, please upvote with a :+1:.
Tell us about your request
Proxy protocol helps an application to retrieve client information like source IP, port information etc. This could be used by the application within the mesh to take actions based on the client. Virtual Gateways currently do not support configuring proxy protocol. But Envoy supports configuring both V1 and V2 version of Proxy protocol. Check here for details.
We must enable AppMesh customers to allow configuring it at the Gateway.
Which integration(s) is this request for?
Applicable to all integrations: Fargate, ECS, EKS, EC2, Kubernetes.
Are you currently working around this issue?
No
rajal-amzn
>All comments
This needs to be added to Virtual Nodes as well.
We have a use case where we deploy NLB => VirtualNode (with Envoy and Nginx) instead of VirtualGateway, to make use of some features that Nginx has, and Virtual Gateway does not. We have Proxy Protocol V2 enabled on NLB, but Envoy responds with HTTP 400 Bad request to all requests from NLB.
mkielar
on 6 Oct 2020
Related issues
duttab49
路
4Comments
omerlh
路
6Comments
AKBarcenas
路
3Comments
bcelenza
路
3Comments
bcelenza
路
3Comments
Most helpful comment
This needs to be added to Virtual Nodes as well.
We have a use case where we deploy NLB => VirtualNode (with Envoy and Nginx) instead of VirtualGateway, to make use of some features that Nginx has, and Virtual Gateway does not. We have Proxy Protocol V2 enabled on NLB, but Envoy responds with HTTP 400 Bad request to all requests from NLB.