Once the process completes, your Fleet instance is ready to use! Check out the documentation for more details on using Fleet.
Osquery_status_s3_bucket = "-fleet-prod-osquery-status-archive" Osquery_results_s3_bucket = "-fleet-prod-osquery-results-archive"
#Osquery fleet manager update#
In the ars file, update fleet_min_capacity and fleet_max_capacity: prefix = "-fleet-prod"įleet_backend_mem = 4096 //software inventory requires 4GB Now that Fleet has everything it needs, we're ready to start the service.įirst, we'll need to edit our production variables to increase Fleet's capacity and allow the service to start. Running this command will kick off the migration task, and Fleet will be ready to go.Īt this point, you can go to your Fleet domain and start using Fleet. Next, we’ll update the terraform setup in the /aws directory's main.tf to use the S3 Bucket and DynamoDB created above: terraform " Now that the remote state is configured, we can move on to setting up the infrastructure for Fleet. You may see a warning during this process. Keep these handy because we’ll need them in the following steps. Terraform will perform the actions described above.Īfter typing yes you should have a new S3 bucket named -fleet-terraform-remote-state And the table -fleet-terraform-state-lock. You should be able to see all the resources that Terraform will create - the S3 bucket and the dynamodb table: Plan: 3 to add, 0 to change, 0 to destroy.ĭo you want to perform these actions in workspace "dev"? terraform apply -var prefix="-fleet" -var region="".terraform workspace new -fleet-remote-state.We'll override the prefix terraform variable to get unique resources and the region variable to use the same region set in the AWS CLI (you can run aws configure get region to see what region is set). To bootstrap our remote state resources, we’ll create a S3 bucket and DynamoDB table using the values defined in remote-state/main.tf.
0 kommentar(er)
