|
5 years ago | |
---|---|---|
.. | ||
README.md | 5 years ago | |
s3.terraform-state.tf | 5 years ago |
This creates some resources that I don't usually want to get rid of. Naturally, these will incur charges if you do not destroy them at some point. But they should be pretty cheap.
This creates:
alias/terraform
for S3 encryption.s3.terraform-state.tf
a. Set the region and profile of your aws credentials
a. Replace bucket = "fcm-terraform-state"
with whatever you want your S3 bucket called. (Remember that the gbucket name must be globally unique)terraform init
terraform apply
You now have an S3 bucket to store terraform state. That lets you and your collaborators work together without have to be on a shared server.
You'll need to update backend.tf
in other directories to use it appropriately.
If you're on a large or very active team, you may want to lookup how to use dynamodb to provide proper locking, as well.