Creating an Amazon Elastic Container Service agent in an existing VPC#

In this guide, you'll set up and deploy an Amazon Elastic Container Service (ECS) agent in an existing VPC using CloudFormation. Amazon ECS agents are used to launch user code in ECS tasks.

Our CloudFormation template allows you to quickly spin up the ECS agent stack in an existing VPC. It also supports using a new or existing ECS cluster. The template code can be found here. Refer to the CloudFormation docs for more info about CloudFormation.

For info about deploying an ECS agent in a new VPC, check out the ECS agents in new VPCs guide.

Prerequisites#

To complete the steps in this guide, you'll need:

• In Dagster Cloud:

  • Your organization and deployment names.
  • Permissions in Dagster Cloud that allow you to manage agent tokens. Refer to the User permissions documentation for more info.

• In Amazon Web Services (AWS):

  • An existing VPC with the following:
    • Subnets with access to the public internet. Refer to the AWS Work with VPCs guide for more info.
    • Enabled enableDnsHostnames and enableDnsSupport DNS attributes. Refer to the AWS DNS attributes documentation for more info.
  • Optional: An existing ECS cluster with a Fargate or EC2 capacity provider. The CloudFormation template will create a cluster for you if one isn't specified.

Step 1: Generate a Dagster Cloud agent token#

In this step, you'll generate a token for the Dagster Cloud agent. The Dagster Cloud agent will use this to authenticate to the agent API.

1. Sign in to your Dagster Cloud instance.
2. Click the user menu (your icon) > Cloud settings.
3. In the Cloud settings page, click the Tokens tab.
4. Click the + Create agent token button.
5. After the token has been created, click Reveal token.

Keep the token somewhere handy - you'll need it to complete the setup.

Step 2: Install the CloudFormation stack in AWS#

Press the "Launch Stack" button below to install the CloudFormation stack in your AWS account.

Note: Creating the CloudFormation stack may take a few minutes. Refresh the AWS console Stacks page to check the status.

Step 3: Configure the agent#

After the stack is installed, you'll be prompted to configure it. In the ECS wizard, fill in the following fields:

• Dagster Cloud Organization: Enter the name of your Dagster Cloud organization.
• Dagster Cloud Deployment: Enter the name of the Dagster Cloud deployment you want to use. Leave this field empty if the agent will only serve Branch deployments.
• Enable Branch Deployments: Whether to have this agent serve your ephemeral Branch deployments. Only a single agent should have this setting enabled.
• Agent Token: Paste the agent token you generated in Step 1.
• Deploy VPC: The existing VPC to deploy the agent into.
• Deploy VPC Subnet: A public subnet of the existing VPC to deploy the agent into.
• Existing ECS Cluster: Optionally, the name of an existing ECS cluster to deploy the agent in. Leave blank to create a new cluster
• Task Launch Type: Optionally, the launch type to use for new tasks created by the agent (FARGATE or EC2). Defaults to FARGATE.

The page should look similar to the following image. In this example, our organization name is hooli and our deployment is prod:

After you've finished configuring the stack in AWS, you can view the agent in Dagster Cloud. To do so, navigate to the Status page and click the Agents tab. You should see the agent running in the Agent statuses section:

Next steps#

Now that you've got your agent running, what's next?

• If you're getting Dagster Cloud set up, the next step is to add a code location using the agent.

• If you're ready to load your Dagster code, refer to the Adding Code to Dagster Cloud guide for more info.

If you need to upgrade your ECS agent's CloudFormation template, refer to the upgrade guide for more info.