naman1-gupta opened a new issue, #12540: URL: https://github.com/apache/apisix/issues/12540
### Description I am running APISIX along with the APISIX ingress controller on EKS. Earlier I was terminating TLS on the gateway level and had certificates defined as secrets in Kubernetes, but now I want to be able to terminate TLS on the LB and send unencrypted traffic from there on. https://aws.amazon.com/blogs/aws/new-tls-termination-for-network-load-balancers/ To do this, I disabled TLS in the Helm chart. However, since the APISIX gateway isn't aware that TLS is being handled before traffic reaches it, it forwards the x-forwarded-proto header with the http scheme, which breaks some applications. One way to fix this is to use the proxy-rewrite plugin and set a custom value for this header. However, I'm looking for a way to instruct the gateway: 'You are running in TLS mode, but you don't have to handle termination.' Is this possible? ### Environment - APISIX version (run `apisix version`): 3.9.1 - Operating system (run `uname -a`): Linux - OpenResty / Nginx version (run `openresty -V` or `nginx -V`): nginx version: openresty/1.25.3.1 - etcd version, if relevant (run `curl http://127.0.0.1:9090/v1/server_info`): 3.5.7-debian-11-r14 - APISIX Dashboard version, if relevant: - Plugin runner version, for issues related to plugin runners: - LuaRocks version, for installation issues (run `luarocks --version`): -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
