Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #2535. #2549

Merged
merged 1 commit into from
Jul 16, 2017
Merged

Fixes #2535. #2549

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 14 additions & 6 deletions docs/terraform.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,16 +14,24 @@ Ps: Steps below assume a recent version of Terraform. There's a workaround for a

#### Set up remote state

You could keep your Terraform state locally, but we **strongly recommend** saving it on S3 with versioning turned on on that bucket. Configure a remote S3 store like so:
You could keep your Terraform state locally, but we **strongly recommend** saving it on S3 with versioning turned on on that bucket. Configure a remote S3 store with a setting like below:

```
$ terraform remote config \
-backend=s3 \
-backend-config="bucket=mycompany.terraform>" \
-backend-config="key=infrastructure.tfstate" \
-backend-config="region=us-east-1"
terraform {
backend "s3" {
bucket = "mybucket"
key = "path/to/my/key"
region = "us-east-1"
}
}
```

Then run:

```
$ terraform init
```
to set up s3 backend.
Learn more [about Terraform state here](https://www.terraform.io/docs/state/remote.html).

#### Initialize/create a cluster
Expand Down