Dustin
0ec109b088
Upstream changed the naming convention for Fedora AMIs. It also seems they've stopped publishing "release" artifacts; all the AMIs are now date-stamped. We should probably consider running `terraform apply` periodically to keep up-to-date. |
||
|---|---|---|
| .. | ||
| .gitattributes | ||
| .gitignore | ||
| .terraform.lock.hcl | ||
| README.md | ||
| asg.tf | ||
| eventbridge.tf | ||
| iam-policy.json | ||
| main.tf | ||
| sns.tf | ||
| terraform.tfstate | ||
| userdata.yml | ||
| variables.tf | ||
README.md
Configuring AWS Using Terraform
Prerequisites
The IAM user or role that runs Terraform must have the appropriate permissions.
The iam-policy.json file defines a policy that will allow the Terraform to
manage all of the necessary resources. Before running Terraform, create an IAM
policy and assign it to a user, group, or role. Be sure to replace the AWS
account ID in the various target resource names.
To use an IAM role, set the iam_role Terraform variable when executing
terraform plan/terraform apply.
Create Resources
Terraform will create all resources automatically:
terraform apply