Remove S3 backend requirement.

This was useful when these scripts were run from centralized
infrastructure.  However the copy in this repo has never been used that
way, and should instead be tailored towards individuals bootstrapping
a small number of environments.  No need to involve a second cloud for
that use case.

env/.gitignore

@@ -0,0 +1,2 @@
+*.tfstate
+*.tfstate.backup

env/Makefile

@@ -8,7 +8,6 @@ NODES ?= 3
 CREDS ?=
 
 # binaries to use
-AWS ?= aws
 TELE ?= tele
 TF ?= terraform
 
@@ -21,11 +20,6 @@ TF_DIR ?= terraform
 # path to the public SSH key file to put on GCE instances
 SSH_KEY_PATH ?=
 
-# parameters for AWS S3 terraform backend
-AWS_S3_REGION ?= us-east-1
-AWS_S3_BUCKET ?= training.gravitational.io
-AWS_S3_OPTS := --region $(AWS_S3_REGION) --acl public-read
-
 # exported terraform variables
 TF_VAR_node_tag := $(ENV)
 TF_VAR_purpose := $(PURPOSE)
@@ -79,9 +73,8 @@ refresh: check-env init
 .PHONY: init
 init: check-env
 	cd ${TF_DIR} && ${TF} init -reconfigure \
-	    -backend-config="region=$(AWS_S3_REGION)" \
-	    -backend-config="bucket=$(AWS_S3_BUCKET)" \
-	    -backend-config="key=terraform/$(ENV)/terraform.tfstate"
+		-backend-config="path=../$(ENV).tfstate"
+
 
 #
 # check-env makes sure ENV environment variable is set.

env/README.md

@@ -4,12 +4,6 @@ for Gravity workshops.
 Each environment consists of 3 clean Ubuntu nodes suitable for installing
 Gravity cluster. The nodes are provisioned on GCE using terraform >= v0.12.
 
-Note, the terraform scripts use S3 backend to store terraform state, so valid
-AWS credentials should be available in the environment.
-
-To use the local backend instead, comment out the terraform backend section in
-the [config.tf](./terraform/config.tf) file.
-
 ### Usage Examples
 
 #### Provision Environment

env/terraform/config.tf

@@ -64,5 +64,5 @@ provider "google" {
 }
 
 terraform {
-  backend "s3" {}
+  backend "local" {}
 }