diff --git a/articles/deploying-fleet-on-aws-with-terraform.md b/articles/deploying-fleet-on-aws-with-terraform.md index 2596513f9d..ec68553cb1 100644 --- a/articles/deploying-fleet-on-aws-with-terraform.md +++ b/articles/deploying-fleet-on-aws-with-terraform.md @@ -83,7 +83,7 @@ in order to create the database from a previous snapshot. ## Deployment -Next, we’ll update the terraform setup in the `/aws` directory's [main.tf](https://github.com/fleetdm/fleet/tree/main/infrastructure/dogfood/terraform/aws/main.tf) to use the S3 Bucket and DynamoDB created above: +Next, we’ll update the terraform setup in the `/aws` directory's [main.tf](https://github.com/fleetdm/fleet/tree/main/infrastructure/dogfood/terraform/aws/main.tf) to use the S3 Bucket and DynamoDB referenced above: ``` terraform { @@ -178,10 +178,10 @@ We'll need some of these values in the next step. Now all we need to do is prepare the database for use. We'll run an AWS ECS Task that will migrate the database and prepare it for use. ``` -aws ecs run-task --cluster fleet-backend --task-definition fleet-migrate: --launch-type FARGATE --network-configuration "awsvpcConfiguration={subnets=[],securityGroups=[]}" +aws ecs run-task --cluster --task-definition fleet-migrate: --launch-type FARGATE --network-configuration "awsvpcConfiguration={subnets=[],securityGroups=[]}" ``` -Where `` is `fleet-migration-task-revision`, `` is one of the private subnets, and `` is the security group from the previous output. +Replace ``, ``, and `` with the corresponding values from the previous output. Replace `` with one of the private subnets from the previous output. For the example output from `terraform apply` in the previous step, the command would look like this: