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
fwiw it looks like this is going to work just fine.
I had to run a separate process to accept HTTP1 to pass the healthcheck,
this meant running static ports rather than the standard ECS dynamic ports.
That's a bit sad, but functional.
Other big PITA is of course that I now need to do SSL
Howdy,
I'm trying to build some configuration distribution with gRPC for
prefab.cloud. All is working, but I could use a second opinion on whether
I'm implementing error handling correctly.
My clients would like to setup a connection and then listen forever. So far
I have found that they
I successfully got GRPC working in AWS with the (fairly new)
NetworkLoadBalancer for http://prefab.cloud
2 main things to know:
1) NLB can’t terminate SSL so you’ll have to do that yourself instead of nice
simple AWS very management.
2) you need to run something next to your GRPC server that
I’m not seeing that exactly, but i’m Having issues on deployments. Seems like
connections don’t reconnect and i’m struggling to feel good about my error
handling and connection resetting code. I’m going ruby client to have server.
You?
--
You received this message because you are subscribed
I put the credentials in an EFS that is attached to all the instances in my ECS
cluster.
Then all apps just look in /efs/certs/
Only other note: be sure not to be silly like I was and try to use LetsEncrypt.
Most other languages (java) do not have LetsEncrypt in their CA.
--
You received
