Skip to content

Commit e6cecfb

Browse files
authored
added the copy of the example tfvars file
1 parent 55d7e63 commit e6cecfb

File tree

1 file changed

+1
-10
lines changed

1 file changed

+1
-10
lines changed

aws/README.md

Lines changed: 1 addition & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,7 @@ Run this command below to have Terraform initialized from this repository. There
2727

2828
```
2929
terraform init -from-module github.com/dcos/terraform-dcos/aws
30+
cp desired_cluster_profile.tfvars.example desired_cluster_profile.tfvars
3031
```
3132

3233
## Configure AWS SSH Keys
@@ -71,16 +72,6 @@ aws_secret_access_key = /R8SHF+SHFJaerSKE83awf4ASyrF83sa471DHSEXAMPLE
7172

7273
## Deploy DC/OS
7374

74-
### Deploying with Default Configuration
75-
76-
We've provided sensible defaults if you would want to play around with Mesosphere DC/OS. The default variables are tracked in [variables.tf](/aws/variables.tf).
77-
78-
Just run this command to deploy a multi-master setup in the cloud. **3 agents will be deployed** for you; 2 private agents, 1 public agent.
79-
80-
```bash
81-
terraform apply
82-
```
83-
8475
### Deploying with Custom Configuration
8576

8677
The default variables are tracked in the [variables.tf](/aws/variables.tf) file. Since this file can be overwritten during updates when you may run `terraform get --update` when you fetch new releases of DC/OS to upgrade to, it's best to use the [desired_cluster_profile.tfvars](/aws/desired_cluster_profile.tfvars.example) and set your custom Terraform and DC/OS flags there. This way you can keep track of a single file that you can use manage the lifecycle of your cluster.

0 commit comments

Comments
 (0)