Concord 2.44

Launch the Concord 2.44 on Ubuntu 24.04 LTS image by SecureAnyCloud from the Azure Marketplace on a Standard_B2s (or larger) VM. Open inbound ports 22 (SSH), 80 (HTTP) and 443 (HTTPS) in the Network Security Group. The 30 GiB data disk that carries the Concord database is provisioned automatically from the image.

When the VM is running, connect over SSH as azureuser with the SSH key you selected at launch:

ssh azureuser@<public-ip>

The database, server, agent and nginx start automatically on boot. Confirm that all four are active:

systemctl is-active postgresql concord-server concord-agent nginx

Each service should print active. For the full status view, run:

systemctl --no-pager status concord-server concord-agent nginx | grep -E 'concord-server|concord-agent|nginx.service|Active:' | head

Concord authenticates the Console and REST API with an administrator API token. The token is unique to your VM and is generated on first boot. Read it from the credentials file:

sudo cat /var/lib/sac/secrets/sac-credentials.txt

The CONCORD_ADMIN_TOKEN value is your administrator credential. Keep it secret, because it grants full administrative access to Concord.

Browse to https://<public-ip>/ and accept the per-VM self-signed certificate. Concord shows its login card.

Choose Login with API Key, paste the CONCORD_ADMIN_TOKEN from the previous step, and sign in as the admin user. You can also open the API-key login directly at https://<public-ip>/#/login?useApiKey=true.

Call the server ping endpoint, which is unauthenticated and confirms that the API is live. Then call the whoami endpoint, which returns the identity behind your token. It should report the admin user:

TOKEN=$(sudo grep '^CONCORD_ADMIN_TOKEN=' /var/lib/sac/secrets/sac-credentials.txt | cut -d= -f2-)
curl -ks https://127.0.0.1/api/v1/server/ping echo
curl -ks -H "Authorization: ${TOKEN}" https://127.0.0.1/api/service/console/whoami

An unauthenticated request to whoami, or one with a wrong token, is rejected with HTTP 401. The image ships no default credential.

Submit a minimal flow as an ad-hoc process and watch the agent execute it:

TOKEN=$(sudo grep '^CONCORD_ADMIN_TOKEN=' /var/lib/sac/secrets/sac-credentials.txt | cut -d= -f2-)
cat > /tmp/concord.yml <<'YML' flows: default: - log: "Hello from the sac Concord appliance" - log: "Workflow executed by concord-agent" YML
RESP=$(curl -ks -H "Authorization: ${TOKEN}" -F concord.yml=@/tmp/concord.yml https://127.0.0.1/api/v1/process)
IID=$(echo "$RESP" | sed -n 's/.*"instanceId"[: ]*"\([^"]*\)".*/\1/p')
echo "Started process ${IID}" for i in $(seq 1 40); do
ST=$(curl -ks -H "Authorization: ${TOKEN}" "https://127.0.0.1/api/v1/process/${IID}" | sed -n 's/.*"status"[: ]*"\([^"]*\)".*/\1/p')
echo "status=${ST}" case "$ST" in FINISHED|FAILED|CANCELLED|TIMED_OUT) break ;; esac sleep 3 done curl -ks -H "Authorization: ${TOKEN}" "https://127.0.0.1/api/v1/process/${IID}/log"

The process moves through NEW -> STARTING -> FINISHED. The log shows the agent acquiring the process, resolving its runtime dependencies and printing the flow's own log lines, ending with Process finished with: 0.

The same run is visible in the Console. Open the process from the dashboard and select the Logs tab.

Open the Console Activity page. It lists your most recent processes with their status, so you can see workflow runs at a glance.

Concord groups projects, repositories, secrets and teams under organisations. The image ships with the built-in Default organisation, ready for you to add projects and Git-backed flow repositories.

All Concord state is held in PostgreSQL. That state covers processes, projects, organisations, the secret store and the audit log. The PostgreSQL cluster is relocated onto the dedicated Azure data disk mounted at /var/lib/concord. Confirm that the running cluster is on the data disk:

mountpoint /var/lib/concord
sudo -u postgres psql -tAqc 'SHOW data_directory'

The data directory is /var/lib/concord/pgdata. Your automation state therefore survives independently of the OS disk, and you can resize the volume on its own.