I have an AWS ECS cluster from which I'd like to expose a GRPC service to the world. That has.... not been easy.
I worked around the challenge of having GPRC join a target group by running dropwizard on one port for the healthcheck and GRPC on a different port. That only got me to the net roadblock though which was that while ALB does accept HTTP2 it forwards it out as HTTP1 and thus I get "Unexpected HTTP/1.x request" from grpc-java. I think the next option would be something like https://medium.com/applied-engineering-reporting-from-the-front/http-load-balancing-on-grpc-services-e3d702db05d7 which makes a custom multiplexer? I thought I was stymied, but then I realized that perhaps http://docs.aws.amazon.com/elasticloadbalancing/latest/network/introduction.html would be the right move. A layer 4 load balancer should get the HTTP2 traffic right to my GRPC server ya? I'd be responsible for SSL termination and all that but still... Giving that a shot though I've gotten stuck on getting an NLBs TCP healthcheck to come back as healthy from GRPC. It's darn hard to debug so I'm wondering whether anybody else has given this a shot / can let me know whether I'm on a reasonable track here. I mostly deal with layer 4 & 7 wrt cakes. Thanks. -Jeff -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To post to this group, send email to grpc-io@googlegroups.com. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/6a6f40cc-c30c-4d87-ae0b-17302fa9890c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
