This code provides some example usage of the Fleet Terraform module, including how some addons can be used to extend functionality. Prior to applying, edit the locals in main.tf to match the settings you want for your Fleet instance including:

domain name
route53 zone name (may match the domain name)
license key (if premium)
any extra settings to be passed to Fleet via ENV var.

To deploy:

terraform apply

If using a new route53 zone:

From the output, obtain the NS records created for the zone and add them to the parent DNS zone

Requirements

Name	Version
terraform	>= 1.12.0
aws	>= 6.37.0

Providers

Name	Version
aws	6.49.0
random	3.9.0
tls	4.3.0

Modules

Name	Source	Version
acm	terraform-aws-modules/acm/aws	4.3.1
fleet	github.com/fleetdm/fleet-terraform?depth=1&ref=tf-mod-root-v1.30.0	n/a
mdm	github.com/fleetdm/fleet-terraform/addons/mdm?depth=1&ref=tf-mod-addon-mdm-v2.2.0	n/a
migrations	github.com/fleetdm/fleet-terraform/addons/migrations?depth=1&ref=tf-mod-addon-migrations-v2.3.0	n/a

Resources

Name	Type
aws_route53_record.main	resource
aws_route53_zone.main	resource
aws_secretsmanager_secret_version.scep	resource
random_password.challenge	resource
tls_private_key.scep_key	resource
tls_self_signed_cert.scep_cert	resource

Inputs

No inputs.

Outputs

Name	Description
route53_name_servers	Ensure that these records are added to the parent DNS zone Delete this output if you switched the route53 zone above to a data source.