AlinsRan commented on issue #1252: URL: https://github.com/apache/apisix-ingress-controller/issues/1252#issuecomment-1328716546
Hi @ochuko3d ! I tried terminating ssl in ELB and it seems to be working fine. I think you should configure LB forwarding to the tls port, I think you can change it to the http port. Please refer to it: https://aws.amazon.com/premiumsupport/knowledge-center/associate-acm-certificate-alb-nlb/?nc1=h_ls Here is my config: ```yaml apiVersion: v1 kind: Service metadata: annotations: meta.helm.sh/release-name: apisix meta.helm.sh/release-namespace: apisix creationTimestamp: "2022-11-28T07:07:59Z" finalizers: - service.kubernetes.io/load-balancer-cleanup labels: app.kubernetes.io/instance: apisix app.kubernetes.io/managed-by: Helm app.kubernetes.io/name: apisix app.kubernetes.io/service: apisix-gateway app.kubernetes.io/version: 2.15.1 helm.sh/chart: apisix-0.11.3 name: apisix-gateway namespace: apisix resourceVersion: "16654" uid: 21cee675-006a-4234-b76d-cc0ae7987d4a spec: allocateLoadBalancerNodePorts: true clusterIP: 10.100.231.173 clusterIPs: - 10.100.231.173 externalTrafficPolicy: Cluster internalTrafficPolicy: Cluster ipFamilies: - IPv4 ipFamilyPolicy: SingleStack ports: - name: apisix-gateway nodePort: 31180 port: 80 protocol: TCP targetPort: 9080 - name: apisix-gateway-tls nodePort: 31065 port: 443 protocol: TCP targetPort: 9443 selector: app.kubernetes.io/instance: apisix app.kubernetes.io/name: apisix sessionAffinity: None type: LoadBalancer ```   -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
