Skip to main content
Microsoft
separator
https://catalogartifact.azureedge.net/publicartifacts/lynxroute.kestra-dd099df6-b629-4518-8fb4-56011530296c/image0_Azureready.png

Kestra - Hardened Self-Hosted Workflow Orchestration Platform

by Lynxroute

Kestra 1.3.37 - CIS Level 1 hardened workflow orchestration on Ubuntu 24.04 LTS with SBOM + CIS

What is Kestra

Kestra is an open-source, event-driven workflow orchestration and scheduling platform built on the Java Virtual Machine (Eclipse Temurin 21) with a JDBC-backed PostgreSQL state store. Workflows are authored as declarative YAML "flows" with a 600+ plugin catalog covering Postgres, MySQL, Kafka, Redis, dbt, Airbyte, Kubernetes, Slack, GitHub, HTTP, shell, Python, and dozens of other integrations. Core features include scheduled and event-driven triggers, dynamic tasks, namespaces with isolated secrets, a visual flow editor with execution graph and Gantt views, runtime expressions via the Pebble template engine, retries with backoff, conditional and parallel branching, and a REST API for headless control. Flow definitions, execution history, queue state, and blob metadata persist in PostgreSQL. Apache-2.0 license, no vendor lock-in.

Why self-host Kestra

Self-hosting keeps every workflow definition, execution payload, secret, and pipeline state inside your own tenant - no per-seat SaaS fees, no third-party visibility into what your pipelines move or transform. Suits teams with data residency requirements and organisations under HIPAA, GDPR, or ISO 27001.

What this VM image adds

Security hardening:

  • Per-instance Kestra admin credential - random username and password generated at first boot, written to /root/kestra-credentials.txt, never baked into the image. Single-tenant by design - the Docker socket is mounted into the Kestra container for the docker-task plugin
  • Kestra REST API and UI bound to 127.0.0.1:8080 - reachable only through the Nginx reverse proxy with TLS
  • PostgreSQL 16 on the Docker bridge network - no host port published, database password rotated per instance; the upstream demo password never ships in this image
  • Nginx reverse proxy with TLS termination - HTTP to HTTPS redirect, hardened cipher suite, WebSocket support for live execution log streaming, security headers (X-Frame-Options, X-Content-Type-Options, Referrer-Policy)
  • Loading splash on cold start - Nginx serves a branded "starting up" page while the JVM warms up and Postgres migrations finish, so the first browser hit never sees an upstream 502
  • UFW firewall - only TCP 22, 80, and 443 are open
  • fail2ban - SSH brute-force protection
  • AppArmor - mandatory access control
  • CVE scan - every image is scanned with Trivy before release
  • Certbot pre-installed - one command issues a Let's Encrypt certificate after you point a domain at the VM

OS hardening (CIS Level 1):

  • CIS Ubuntu 24.04 LTS Level 1 Benchmark via ansible-lockdown
  • auditd for system call auditing of critical paths
  • SSH hardening - PasswordAuthentication disabled, key-only access
  • Kernel hardening - SYN cookies, ASLR, rp_filter, TCP BBR
  • /tmp as tmpfs with nosuid, nodev, noexec
  • Azure IMDS endpoints - egress rules pre-configured (169.254.169.254, 168.63.129.16)

Compliance artifacts (inside the VM):

  • SBOM - CycloneDX 1.6 at /etc/lynxroute/sbom.json
  • CIS Conformance Report at /etc/lynxroute/cis-report.html
  • Tailored CIS profile at /usr/share/doc/lynxroute/CIS_TAILORED_PROFILE.md
  • Server credentials file - /root/kestra-credentials.txt with the web UI URL, the per-instance admin username and password, and the per-instance PostgreSQL password

Quick Start

  1. Deploy VM from Azure Marketplace (Standard_D2s_v3 or larger recommended)
  2. Open NSG: TCP 443 from your client networks, TCP 22 from your management IPs only
  3. SSH: ssh -i key.pem azureuser@<PUBLIC_IP>, then sudo cat /root/kestra-credentials.txt for the web UI URL, admin username, and admin password
  4. Open https://<PUBLIC_IP>, accept the self-signed certificate, and log in with the username and password from the credentials file. First boot takes 60-120 seconds while the JVM warms up; until ready the URL returns a Lynxroute loading splash that auto-refreshes
  5. In the Kestra UI click Settings -> Users and change both the email and the password to values you own - the bootstrap email is a per-instance .local placeholder
  6. Issue a public TLS certificate before sharing the VM: sudo certbot --nginx -d your.domain.com
English (United States)
Your Privacy Choices Opt-Out Icon Your Privacy Choices
Consumer Health Privacy Sitemap Contact Us Privacy & Cookies Terms of Use About our ads Manage cookies