Hello,
I’ve deployed the Camunda 8 core components to our AWS shared VPC as ECS Fargate services. I’m using Terraform to script our deployment.
The installation is working fine (Desktop modeler with Operate and Tasklist).
I’m trying now to implement a Spring Boot Zeebe client using the Bernd’s example customer-onboarding-camunda-8-springboot.
My issue is that the Camunda 8 services are running behind an AWS Application Load Balancer. The listener is exposing the 26500 port with https with a target group with gRPC as protocol version. I can deploy without problems my BPMNs from the desktop modeler with a cluster endpoint https…
But when I’m trying to access the broker from my spring boot application, I’m getting the error:
…
Caused by: java.util.concurrent.ExecutionException: io.grpc.StatusRuntimeException: UNAVAILABLE: Network closed for unknown reason
at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:396) ~[na:na]
at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2073) ~[na:na]
at io.camunda.zeebe.client.impl.ZeebeClientFutureImpl.join(ZeebeClientFutureImpl.java:52) ~[zeebe-client-java-8.4.1.jar:8.4.1]
… 34 common frames omitted
Caused by: io.grpc.StatusRuntimeException: UNAVAILABLE: Network closed for unknown reason
…
When providing the Zeebe AWS task IP private address (by-passing the ALB) for the zeebe.client.broker.gateway-address property, everything is working fine.
Is there a way on the client side to enable/disable TLS for the connections to the Zeebe broker?
BR
Pascal