Makefile 2.3 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162
  1. # Set up terraform variables in a separate environment file, or inline here
  2. # This region should support EFS
  3. TF_VAR_region ?= us-gov-east-1
  4. # Cluster name is a unique cluster name to use, should be unique and not contain spaces or other special characters
  5. TF_VAR_cluster_name ?= teleporttest
  6. # AWS SSH key name to provision in installed instances, should be available in the region
  7. TF_VAR_key_name ?= duane.waddle
  8. # Full absolute path to the license file for Teleport Enterprise or Pro.
  9. # This license will be copied into SSM and then pulled down on the auth nodes to enable Enterprise/Pro functionality
  10. TF_VAR_license_path ?= ~/Downloads/license.pem
  11. # AMI name contains the version of Teleport to install, and whether to use OSS or Enterprise version
  12. # These AMIs are published by Gravitational and shared as public whenever a new version of Teleport is released
  13. # To list available AMIs:
  14. # OSS: aws ec2 describe-images --filters 'Name=name,Values=gravitational-teleport-ami-oss*'
  15. # Enterprise: aws ec2 describe-images --filters 'Name=name,Values=gravitational-teleport-ami-ent*'
  16. TF_VAR_ami_name ?= teleport-fips
  17. # Route 53 zone to use, should be the zone registered in AWS, e.g. example.com
  18. TF_VAR_route53_zone ?= xdrtest.accenturefederalcyber.com
  19. # Subdomain to set up in the zone above, e.g. cluster.example.com
  20. # This will be used for internet access for users connecting to teleport proxy
  21. TF_VAR_route53_domain ?= teleporttest
  22. # Bucket name to store encrypted letsencrypt certificates.
  23. TF_VAR_s3_bucket_name ?= xdr-teleporttest
  24. # Email of your support org, used for Letsencrypt cert registration process.
  25. TF_VAR_email ?= xdr.eng@accenturefederal.com
  26. # Set to true to use LetsEncrypt to provision certificates
  27. TF_VAR_use_letsencrypt ?=true
  28. # Set to true to use ACM (Amazon Certificate Manager) to provision certificates
  29. # If you wish to use a pre-existing ACM certificate rather than having Terraform generate one for you, you can import it:
  30. # terraform import aws_acm_certificate.cert <certificate_arn>
  31. TF_VAR_use_acm ?=false
  32. export
  33. # Plan launches terraform plan
  34. .PHONY: plan
  35. plan:
  36. terraform init
  37. terraform plan
  38. # Apply launches terraform apply
  39. .PHONY: apply
  40. apply:
  41. terraform init
  42. terraform apply
  43. # Destroy deletes the provisioned resources
  44. .PHONY: destroy
  45. destroy:
  46. terraform init
  47. terraform destroy