rm hrs

dagster-io · Dec 25, 2024 · f197378 · f197378
1 parent bb2c56f
commit f197378
Show file tree

Hide file tree

Showing 4 changed files with 0 additions and 34 deletions.
diff --git a/...r-plus/deployment/deployment-types/hybrid/amazon-ecs/configuration-reference.md b/...r-plus/deployment/deployment-types/hybrid/amazon-ecs/configuration-reference.md
@@ -9,8 +9,6 @@ This guide is applicable to Dagster+.
 
 This reference describes the various configuration options Dagster+ currently supports for [Amazon ECS agents](/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs).
 
----
-
 ## Per-location configuration
 
 When [adding a code location](/dagster-plus/deployment/code-locations) to Dagster+ with an Amazon ECS agent, you can use the `container_context` key on the location configuration to add additional ECS-specific configuration that will be applied to any ECS tasks associated with that code location.
@@ -113,8 +111,6 @@ Refer to the following guides for more info about environment variables:
 - [Dagster+ environment variables and secrets](/dagster-plus/deployment/management/environment-variables/)
 - [Using environment variables and secrets in Dagster code](/guides/deploy/secrets)
 
----
-
 ## Per-job configuration: Resource limits
 
 You can use job tags to customize the CPU and memory of every run for that job:
@@ -140,8 +136,6 @@ def my_job():
 
 If the `ecs/cpu` or `ecs/memory` tags are set, they will override any defaults set on the code location or the deployment.
 
----
-
 ## Per-deployment configuration
 
 This section describes the properties of the `dagster.yaml` configuration file used by Amazon ECS agents. Typically, this file is created by the CloudFormation template that deploys the agent and can be found within the agent task definition's command.

diff --git a/...docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/existing-vpc.md b/...docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/existing-vpc.md
@@ -13,8 +13,6 @@ Our CloudFormation template allows you to quickly spin up the ECS agent stack in
 
 **For info about deploying an ECS agent in a new VPC**, check out the [ECS agents in new VPCs guide](/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/new-vpc).
 
----
-
 ## Prerequisites
 
 To complete the steps in this guide, you'll need:
@@ -30,8 +28,6 @@ To complete the steps in this guide, you'll need:
     - **Enabled `enableDnsHostnames` and `enableDnsSupport` DNS attributes**. Refer to the [AWS DNS attributes documentation](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-dns.html#vpc-dns-support) for more info.
   - **Optional**: An existing ECS cluster with a [Fargate or EC2 capacity provider](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cluster-capacity-providers.html). The CloudFormation template will create a cluster for you if one isn't specified.
 
----
-
 ## Step 1: Generate a Dagster+ agent token
 
 In this step, you'll generate a token for the Dagster+ agent. The Dagster+ agent will use this to authenticate to the agent API.
@@ -43,7 +39,6 @@ In this step, you'll generate a token for the Dagster+ agent. The Dagster+ agent
 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
 
@@ -53,8 +48,6 @@ Click the **Launch Stack** button to install the CloudFormation stack in your AW
 
 **Note**: Creating the CloudFormation stack may take a few minutes. Refresh the [AWS console **Stacks** page](https://console.aws.amazon.com/cloudformation/home#/stacks) 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:
@@ -76,8 +69,6 @@ After you've finished configuring the stack in AWS, you can view the agent in Da
 
 ![Instance Status](/images/dagster-cloud/agents/dagster-cloud-instance-status.png)
 
----
-
 ## Next steps
 
 Now that you've got your agent running, what's next?

diff --git a/.../dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/manual-provision.md b/.../dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/manual-provision.md
@@ -11,8 +11,6 @@ In this guide, you'll manually set up and deploy an Amazon Elastic Container Ser
 
 This method of setting up an Amazon ECS agent is a good option if you're comfortable with infrastructure management and want to fully define your agent.
 
----
-
 ## Prerequisites
 
 To complete the steps in this guide, you'll need:
@@ -29,8 +27,6 @@ To complete the steps in this guide, you'll need:
 
 - **Familiarity with infrastructure management and tooling.**
 
----
-
 ## Step 1: Generate a Dagster+ agent token
 
 In this step, you'll generate a token for the Dagster+ agent. The Dagster+ agent will use this to authenticate to the agent API.
@@ -43,8 +39,6 @@ In this step, you'll generate a token for the Dagster+ agent. The Dagster+ agent
 
 Keep the token somewhere handy - you'll need it to complete the setup.
 
----
-
 ## Step 2: Create ECS IAM roles
 
 To successfully run your ECS agent, you'll need to have the following IAM roles in your AWS account:
@@ -119,8 +113,6 @@ To successfully run your ECS agent, you'll need to have the following IAM roles
 }
 ```
 
----
-
 ## Step 3: Create an ECS service
 
 1. Create an ECS service to run the agent. You can do this [in the Amazon ECS console](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-service-console-v2.html) or [via the CreateService API](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html).
@@ -134,8 +126,6 @@ To successfully run your ECS agent, you'll need to have the following IAM roles
 
    Refer to the [ECS configuration reference](/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/configuration-reference#per-deployment-configuration) for more info about the required fields.
 
----
-
 ## Next steps
 
 Now that you've got your agent running, what's next?

diff --git a/...beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/new-vpc.md b/...beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/new-vpc.md
@@ -13,8 +13,6 @@ Our CloudFormation template allows you to quickly spin up the ECS agent stack. T
 
 **For info about deploying an ECS agent in an existing VPC**, check out the [ECS agents in existing VPCs guide](/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/existing-vpc).
 
----
-
 ## Prerequisites
 
 To complete the steps in this guide, you'll need:
@@ -37,8 +35,6 @@ To complete the steps in this guide, you'll need:
     - Create one using the [first run wizard](https://console.aws.amazon.com/ecs/home#/firstRun), or
     - Create the IAM role using the [AWS CLI](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html#create-service-linked-role)
 
----
-
 ## Step 1: Generate a Dagster+ agent token
 
 In this step, you'll generate a token for the Dagster+ agent. The Dagster+ agent will use this to authenticate to the agent API.
@@ -50,7 +46,6 @@ In this step, you'll generate a token for the Dagster+ agent. The Dagster+ agent
 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
 
@@ -62,8 +57,6 @@ Click the **Launch Stack** button to install the CloudFormation stack in your AW
 
 If the installation fails, verify that your AWS account [meets the requirements listed above](#prerequisites).
 
----
-
 ## 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:
@@ -81,8 +74,6 @@ After you've finished configuring the stack in AWS, you can view the agent in Da
 
 ![Instance Status](/images/dagster-cloud/agents/dagster-cloud-instance-status.png)
 
----
-
 ## Next steps
 
 Now that you've got your agent running, what's next?