Workflow orchestration on AWS
Durable execution and orchestration for application workflows.
7 documented options on Amazon Web Services. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.
Read this page as JSON or Markdown.
| Listing | Documented clouds | Deployment and infrastructure | Licensing | Installation | Operations and limitations |
|---|---|---|---|---|---|
| Apache Airflow | AWS, DigitalOcean | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for upstream Airflow; dependencies, provider integrations and external services have their own terms. | Install the Python distribution or official container images; the Apache Airflow Helm chart deploys the platform to a customer-operated Kubernetes cluster. | Customer operates Airflow services, database, worker capacity, Dag code, credentials, authorization, logs, backups and version upgrades.Scope and evidenceThe Helm chart is a deployment mechanism, not a managed control plane. Providers and Dag tasks can call external databases, APIs, compute or model services. Review each integration and executor before treating a complete pipeline as contained in the account. Managed Airflow services are separate offerings. Airflow 3.4’s Dag Importer and language-SDK support is experimental; non-Python Dag authoring requires the applicable language runtime and coordinator on Dag processors and workers.
Cloud evidence reviewed 2026-11-12 |
| Camunda 8 Self-Managed | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Enterprise license required for production; unlicensed use is limited to non-production conditions. | Official Helm charts on EKS, AKS or GKE | Customer manages Kubernetes, supported databases or search services, storage, ingress, identity, backups, scaling and upgrades.Scope and evidenceThis entry covers Camunda 8 Self-Managed, not Camunda SaaS. Match Helm and component versions, size persistent storage for the workload and review external database/search dependencies. A valid Enterprise license is required for production use. Camunda Notice 80 covers critical eMudhra trust-store issues, including CVE-2026-114820, across multiple 8.6–8.10 components; fixed versions differ by component, and Keycloak requires a sufficiently recent rebuilt image. Notices 81 and 82 also patch Web Modeler HTTP parser and custom HTTP/2 denial-of-service paths. Follow the component matrix instead of treating one Helm version as a universal fix. Camunda Optimize 8.6.30 and 8.7.32 mitigate CVE-2026-114938 by disabling the affected AVX-512 Base64 intrinsic. Apply the branch-specific Optimize update, or move to a fixed JDK when supplied, and do not treat a single Helm version as a universal Camunda fix.
Cloud evidence reviewed 2026-11-14 |
| Dagster OSS | AWS | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for upstream Dagster; Dagster commercial services are separate. | Deploy the documented OSS Docker Compose stack with webserver, daemon, code locations and PostgreSQL run storage. | Customer manages orchestration services, code images, run storage, execution capacity, access boundaries and upgrades.Scope and evidenceThis listing covers fully self-hosted OSS Dagster, not the commercial hybrid control plane. Integrations, run launchers and user code can use external services. Secure network access to the OSS management services.
Cloud evidence reviewed 2026-11-12 |
| HashiCorp Nomad Enterprise | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Nomad Enterprise license required for the selected edition; Community Edition uses separate source-available terms. | HashiCorp Validated Design Terraform modules where available or manual package and binary installation | Customer manages servers and clients, TLS, gossip encryption, ACLs, snapshots, networking, workload drivers, upgrades and availability.Scope and evidenceThis entry scopes Nomad Enterprise rather than the separately licensed Community Edition. HashiCorp's validated cloud design requires a production multi-node topology, enterprise license, TLS and gossip encryption, protected snapshots and provider-specific infrastructure. Confirm the current validated module release and supported operating systems before deployment. HCSEC-2026-51, 52, and 53 cover cross-namespace information disclosure plus symlink-based allocation-directory escape and host permission modification. Fixed Enterprise builds are 2.1.0, 1.11.12, and 1.10.18.
Cloud evidence reviewed 2026-11-17 |
| Kestra Self-Hosted | AWS, Azure, Google Cloud, DigitalOcean | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for the open-source Kestra platform; commercial Enterprise features and support are separate. | Docker on AWS EC2 or DigitalOcean Droplets, or Helm on AWS EKS, Google GKE or Azure AKS, with documented database and object storage services. | Customer manages server and worker capacity, PostgreSQL, object storage, plugins, credentials, network access, backups and upgrades.Scope and evidenceVendor guides cover AWS, Azure, Google Cloud and DigitalOcean deployments, including single-VM starting points and distributed Kubernetes installations. Customers operate the application, database and storage configuration; production ingress, authentication, credentials and high availability depend on the selected topology. Enterprise features and support are separately licensed. Kestra v2.0.11 updates dependencies for CVE-2026-45292 and other vulnerable libraries and adds CSRF tokens to Basic-auth browser requests. Recheck browser automation and authenticated API clients after upgrading.
Cloud evidence reviewed 2026-11-13 |
| Prefect Server | Northflank, AWS, Azure, Google Cloud | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for upstream Prefect. Prefect Cloud is a separate managed offering. | Install Prefect and start its server; use the documented PostgreSQL/Redis architecture when scaling multiple API and background-service instances. | Customer manages server services, database, queue/cache, worker pools, secrets, access controls and upgrades.Scope and evidenceConfigure clients and workers against the self-hosted API. Task code and worker integrations can still use external compute and services. Self-hosted control-plane capacity is separate from any serverless execution target. Prefect 3.9.4.dev6 is a prerelease that stops GitRepository from exposing URL-embedded credentials in DEBUG logs and repr output and adds same-origin validation for UI v2 post-login redirects. No stable fixed release was published at review time. Avoid credential-bearing repository URLs, restrict DEBUG logs, rotate exposed tokens and validate the eventual stable release before production rollout.
Cloud evidence reviewed 2026-11-12 |
| Temporal Self-Hosted | AWS | Customer-operated Servers / containers | Open Source / Open Core MIT-licensed Temporal Server; managed Cloud offering is separate | Production Docker/Kubernetes or manual server deployment with persistence and application workers | Customer configures service security, persistence, worker capacity, monitoring, upgrades and disaster recovery.Scope and evidenceThe local CLI development server is not a production installation. Self-hosted Temporal requires substantial operational ownership; the production guide notes that RBAC and audit logging are not provided out of the box. This entry excludes Temporal Cloud and does not describe a packaged end-user workflow application. Temporal v1.32.2 includes security fixes and changes ValidateWorkerDeploymentVersionComputeConfig to require namespace Write access; matching security patches are available as v1.31.5 and v1.30.9. Review namespace permissions before upgrading.
Cloud evidence reviewed 2026-11-12 |
Deployment evidence and category fit
Apache Airflow
Directed workflows with task dependencies, scheduling, execution and monitoring. Python remains the traditional authoring language; Airflow 3.4 adds experimental whole-Dag authoring in TypeScript, Java, Go and YAML. Executor and provider configuration determine where work runs.
The Helm chart is a deployment mechanism, not a managed control plane. Providers and Dag tasks can call external databases, APIs, compute or model services. Review each integration and executor before treating a complete pipeline as contained in the account. Managed Airflow services are separate offerings. Airflow 3.4’s Dag Importer and language-SDK support is experimental; non-Python Dag authoring requires the applicable language runtime and coordinator on Dag processors and workers.
- Airflow Helm deployment on EKS with IAM roles ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The current upstream Amazon provider guide explicitly configures Airflow Helm webserver/worker pods on EKS, including their service account, and links a self-managed Terraform deployment example. S3 logging is optional infrastructure configuration; this is not Amazon Managed Workflows for Apache Airflow. Restrict the example IAM permissions for production.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
Camunda 8 Self-Managed
Coordinates durable process instances, service tasks and distributed workers using the Camunda orchestration cluster.
This entry covers Camunda 8 Self-Managed, not Camunda SaaS. Match Helm and component versions, size persistent storage for the workload and review external database/search dependencies. A valid Enterprise license is required for production use. Camunda Notice 80 covers critical eMudhra trust-store issues, including CVE-2026-114820, across multiple 8.6–8.10 components; fixed versions differ by component, and Keycloak requires a sufficiently recent rebuilt image. Notices 81 and 82 also patch Web Modeler HTTP parser and custom HTTP/2 denial-of-service paths. Follow the component matrix instead of treating one Helm version as a universal fix. Camunda Optimize 8.6.30 and 8.7.32 mitigate CVE-2026-114938 by disabling the affected AVX-512 Base64 intrinsic. Apply the branch-specific Optimize update, or move to a fixed JDK when supplied, and do not treat a single Helm version as a universal Camunda fix.
- Camunda 8 Self-Managed on Amazon EKS ↗
Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.
Camunda provides current EKS infrastructure and Helm installation guidance for a customer AWS account, including managed persistence dependencies.
Cloud evidence reviewed 2026-11-14. Full listing and qualifications
Dagster OSS
Orchestrates data assets and jobs with schedules, sensors, run tracking and separately configured execution code.
This listing covers fully self-hosted OSS Dagster, not the commercial hybrid control plane. Integrations, run launchers and user code can use external services. Secure network access to the OSS management services.
- Dagster OSS Docker Compose deployment on EC2 ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The project explicitly identifies an AWS EC2 host for its OSS Docker Compose deployment, including webserver, daemon and code-location containers. Review current images, persistence, secrets and production hardening; this is separate from Dagster Plus and its customer-cloud agent.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
HashiCorp Nomad Enterprise
Coordinates long-running services, batch jobs and parameterized workload execution through declarative job specifications.
This entry scopes Nomad Enterprise rather than the separately licensed Community Edition. HashiCorp's validated cloud design requires a production multi-node topology, enterprise license, TLS and gossip encryption, protected snapshots and provider-specific infrastructure. Confirm the current validated module release and supported operating systems before deployment. HCSEC-2026-51, 52, and 53 cover cross-namespace information disclosure plus symlink-based allocation-directory escape and host permission modification. Fixed Enterprise builds are 2.1.0, 1.11.12, and 1.10.18.
- Nomad Enterprise validated cloud deployment on AWS, Azure and Google Cloud ↗
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
HashiCorp's Validated Design documents production Nomad deployment on customer AWS, Azure and Google Cloud infrastructure. The operator supplies the Enterprise license and manages the resulting cluster.
Cloud evidence reviewed 2026-11-17. Full listing and qualifications
Kestra Self-Hosted
Orchestrates scheduled and event-driven data, infrastructure, business and AI workflows with customer-operated execution workers.
Vendor guides cover AWS, Azure, Google Cloud and DigitalOcean deployments, including single-VM starting points and distributed Kubernetes installations. Customers operate the application, database and storage configuration; production ingress, authentication, credentials and high availability depend on the selected topology. Enterprise features and support are separately licensed. Kestra v2.0.11 updates dependencies for CVE-2026-45292 and other vulnerable libraries and adds CSRF tokens to Basic-auth browser requests. Recheck browser automation and authenticated API clients after upgrading.
- Kestra on Amazon EC2 with RDS and S3 ↗
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor documents deploying Kestra on a customer EC2 instance and moving database and internal storage to customer RDS PostgreSQL and S3. Secure the application endpoint and replace example broad credentials with least-privilege IAM.
- Kestra on Amazon EKS with RDS and S3 ↗
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor documents a distributed Helm deployment on customer EKS with RDS PostgreSQL, S3 storage and an AWS load balancer. Review cluster sizing, ingress, workload identity, backups and high-availability configuration.
Cloud evidence reviewed 2026-11-13. Full listing and qualifications
Prefect Server
Python flow/task orchestration with retries, scheduling, state tracking and workers that execute deployments on configured infrastructure.
Configure clients and workers against the self-hosted API. Task code and worker integrations can still use external compute and services. Self-hosted control-plane capacity is separate from any serverless execution target. Prefect 3.9.4.dev6 is a prerelease that stops GitRepository from exposing URL-embedded credentials in DEBUG logs and repr output and adds same-origin validation for UI v2 post-login redirects. No stable fixed release was published at review time. Avoid credential-bearing repository URLs, restrict DEBUG logs, rotate exposed tokens and validate the eventual stable release before production rollout.
- Prefect deployment through Northflank BYOC ↗
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The provider guide installs the self-hosted Prefect server/API/UI, PostgreSQL and worker and explicitly offers AWS, Google Cloud or Azure through Northflank Bring Your Own Cloud. These hyperscaler badges require the BYOC deployment option and its commercial/access prerequisites; a default Northflank hosted project does not run in the customer hyperscaler account. This is a Northflank deployment recipe, not a claim of Prefect vendor-managed BYOC.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
Temporal Self-Hosted
Developer-oriented durable workflow execution and retry/state orchestration; application workers and code must be supplied.
The local CLI development server is not a production installation. Self-hosted Temporal requires substantial operational ownership; the production guide notes that RBAC and audit logging are not provided out of the box. This entry excludes Temporal Cloud and does not describe a packaged end-user workflow application. Temporal v1.32.2 includes security fixes and changes ValidateWorkerDeploymentVersionComputeConfig to require namespace Write access; matching security patches are available as v1.31.5 and v1.30.9. Review namespace permissions before upgrading.
- Temporal server Helm chart on Amazon EKS ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream Temporal server Helm chart explicitly identifies AWS EKS as a target cluster. The current V3 chart deploys server components and requires separately provisioned persistence; it no longer installs database sub-charts. Review schema management, credentials, access controls and production operations. This is separate from Temporal Cloud.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
Deployment and procurement checks
- Private offers
- AWS Marketplace private offers can contain negotiated pricing and terms for a buyer account. Confirm the product delivery model and your agreement; commitment credit is not established by a directory badge. Provider source ↗ · Reviewed 2026-11-14
- Private connectivity
- PrivateLink provides private endpoints to supported services and resources across VPC/account boundaries. Confirm that the selected product exposes a compatible endpoint service. Provider source ↗ · Reviewed 2026-11-14
- Cross-account operations
- Use an IAM role with scoped permissions and a third-party external ID where applicable. Review the trust principal, support access and revocation separately from installation access. Provider source ↗ · Reviewed 2026-11-14
- Government environments
- AWS GovCloud (US) is a distinct isolated-region environment. A commercial-region product deployment does not establish availability or certification there. Provider source ↗ · Reviewed 2026-11-14
For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.
Plan this deployment
Account boundary: AWS account. Access: IAM roles and policies. Network: VPC.
Provider documentation ↗ · Guidance reviewed 2026-11-10. Confirm the application edition, region, support access, backup locations and operating responsibilities before choosing.
Compare this category across clouds · Search these listings · Compare 2–4 listings