empayre/fleet
14
0
Fork 0
mirror of https://github.com/empayre/fleet.git synced 2024-11-06 08:55:24 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update deploying-fleet-on-aws-with-terraform.md (#8748)

Browse Source 
Changed some wording under "Deployments" to remove confusion, and
updated instructions for "Prepare the database" to better reflect the
previous outputs from the terraform apply.

Co-authored-by: Katheryn Satterlee <me@ksatter.com>
This commit is contained in:
creedjax 2023-01-06 15:40:24 -06:00 committed by GitHub
parent 656e5bfc70
commit b204647c49
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
articles/deploying-fleet-on-aws-with-terraform.md
View File

@ -83,7 +83,7 @@ in order to create the database from a previous snapshot.
## Deployment ## 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 { 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. 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:<latest_migration_version> --launch-type FARGATE --network-configuration "awsvpcConfiguration={subnets=[<private_subnet_id>],securityGroups=[<desired_security_group>]}" aws ecs run-task --cluster <ecs_cluster_name> --task-definition fleet-migrate:<fleet-migration-task-revision> --launch-type FARGATE --network-configuration "awsvpcConfiguration={subnets=[<private_subnet_id>],securityGroups=[<backend_security_group_id>]}"
``` ```
Where `<migration_version>` is `fleet-migration-task-revision`, `<private_subnet_id>` is one of the private subnets, and `<desired_security_group>` is the security group from the previous output. Replace `<backend_security_group_id>`, `<ecs_cluster_name>`, and `<fleet-migration-task-revision>` with the corresponding values from the previous output. Replace `<private_subnet_id>` 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: For the example output from `terraform apply` in the previous step, the command would look like this: