This documentation is for an older version (1.4.7) of Dagster. You can view the version of this page from our latest release below.
For Hybrid deployments, Dagster Cloud uses an agent that is responsible for executing your code. The agent streams metadata about code execution over HTTPS to Dagster Cloud’s Agent API.
Dagster Cloud currently supports agents running on the following backends:
| Name | How it works |
|---|---|
| Amazon Elastic Container Service (ECS) | The Amazon Elastic Container Service (ECS) agent executes Dagster jobs as Amazon Web Services (AWS) ECS tasks. This agent is appropriate for scaled production deployments; ECS is a good choice for teams who have already standardized on ECS or who don't plan to run their own container orchestration infrastructure. |
| Docker | The Docker agent executes Dagster jobs in Docker containers on your computer. |
| Kubernetes | The Kubernetes agent executes Dagster jobs on a Kubernetes cluster. This agent is appropriate for scaled production deployments and is a good choice for teams who have already standardized on Kubernetes. |
| Local | The local agent executes Dagster jobs as processes on your computer. |