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.
In this guide, we'll cover:
Dagster Cloud currently supports agents running on the following backends:
The Amazon Elastic Container Service (ECS) agent executes Dagster jobs as Amazon Web Services (AWS) Fargate 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.
There are three ways you can create an Amazon ECS agent:
Already used our CloudFormation template? Refer to the Upgrading CloudFormation for Amazon ECS guide for info about upgrading your ECS agent's template.
The Docker agent executes Dagster jobs in Docker containers on your computer. Refer to the setup guide for more info.
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. Refer to the setup guide for more info.
Already set up a Kubernetes agent? Refer to the Kubernetes agent configuration reference for info about configuration options.
The local agent executes Dagster jobs as processes on your computer. Refer to the setup guide for more info.