Self-managed deployment using AWS ECS Fargate: error when starting connectors-bundle app

lugon · June 26, 2024, 12:36pm

Hello,

I’m doing some experimentation with a self-managed Camunda 8 configuration deployed to AWS ECS Fargate using Terraform. I’ve made a first try in February with 8.4 versions and everything was working fine.

With the upgrade to the version 8.5.2 for the platform and 8.5.3 for the connectors-bundle, I can see the following error in the connectors log:

2024-06-26T12:25:42.349Z ERROR 1 — [ scheduling-1] i.c.common.auth.SimpleAuthentication : Authenticating for OPERATE failed due to org.apache.hc.client5.http.ClientProtocolException

I’ve checked the different environment variables as listed in the camunda platform docker-compose.yml file without finding the right setup.

github.com

camunda/camunda-platform/blob/b216901aacb72ab06ef85b89a9c2146189daccd4/docker-compose.yaml

# While the Docker images themselves are supported for production usage,
# this docker-compose.yaml is designed to be used by developers to run
# an environment locally. It is not designed to be used in production.
# We recommend to use Kubernetes in production with our Helm Charts:
# https://docs.camunda.io/docs/self-managed/platform-deployment/kubernetes-helm/
# For local development, we recommend using KIND instead of `docker-compose`:
# https://docs.camunda.io/docs/self-managed/platform-deployment/helm-kubernetes/guides/local-kubernetes-cluster/

# This is a full configuration with Zeebe, Operate, Tasklist, Optimize, Identity, Keycloak, and Elasticsearch
# See docker-compose-core.yml for a lightweight configuration that does not include Optimize, Identity, and Keycloak.

services:

  zeebe: # https://docs.camunda.io/docs/self-managed/platform-deployment/docker/#zeebe
    image: camunda/zeebe:${CAMUNDA_PLATFORM_VERSION}
    container_name: zeebe
    ports:
      - "26500:26500"
      - "9600:9600"
      - "8088:8080"

This file has been truncated. show original

my experimental configuration is not using the identity app.

BR
Pascal

lugon · August 9, 2024, 6:24am

My latest experiments with the connectors-bundle:

When trying the 2.5.5 version, it fails connecting to the running operate service: still trying to connect to http://localhost:8081 whatever the properties I was trying to inject for the URL (also tried to find alternate properties names in the source code).
As desperate move I’ve tried the 8.6.0-alpha version and it finally worked!!!
So apparently the operate URL wasn’t correctly loaded in the 2.5.X versions of the connectors-bundle.
BR

system · November 7, 2024, 6:24am

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.