title: Unable to Establish Insecure gRPC connection on the New AWS gRPC ELB
body: <p>AWS ALB has the new support for gRPC load balancing as per this <a href="https://aws.amazon.com/blogs/aws/new-application-load-balancer-support-for-end-to-end-http-2-and-grpc/" rel="nofollow noreferrer">Link</a></p>
  <p>All the explanation indicates using an ssl connection between the client &amp; the server. Now, this might be required if client is browser, but in the case of Internal ALB &amp; Intra service communication, I would not like to have secure connection.</p>
  <p>Is this possible/ Has anyone got more info on how to load balance without ssl?</p>
  <p><strong>What I understand:</strong>
  Pick your domain name, generate a certificate. Add Alias for this in Route 53 (same domain name) &amp; use the certificates in client &amp; server for intra-servie communication in Internal ELB.</p>
  <p>Is this the only way possible? I have to also manage this certificate.</p>