That’s great news. Does anybody know if they support ALPN to announce h2 as the http2 protocol? They don’t do this for ELBs, I would hope for NLBs. If they d

That’s great news. Does anybody know if they support ALPN to announce h2 as the http2 protocol? They don’t do this for ELBs, I would hope for NLBs. If they do this, this would finally be the sane solution how to use NLBs + ACM to expose gRPC services at the edge. Other solution might maybe be (as popping up here in the threads): Use NLB + ACM and let it do MITM and then forward the traffic to a service with a self signed certificate. The hope here would be that the NLB would pick up the ALPN header from your backend service and communicate it transparently to the outside world. Don’t know if this architecture makes sense. Anyways, I just would love gRPC capable secure workloads on the NLB with ACM. Doing Self signed certificates or LetsEncrypt works already - the Gamechanger is to use ACM + ALPN and by that also having upstream http2 traffic behind the NLB (compared to the ALB, which only supports upstream http1)