Skip to content

Commit

Permalink
Fix Readme
Browse files Browse the repository at this point in the history
  • Loading branch information
achetronic committed Oct 25, 2021
1 parent 988050e commit a550013
Showing 1 changed file with 7 additions and 4 deletions.
11 changes: 7 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ export TF_VAR_SSH_PRIVATE_KEY_PATH="~/.ssh/id_ed25519"
> By the moment, only recent Ubuntu versions are supported.
> Feel free to extend the OS support pushing your code to this repository.
```bash
terraform apply --target module.init
terraform init && terraform apply --target module.init
```


Expand All @@ -30,17 +30,20 @@ terraform apply --target module.init

4. Create your VMs.
```bash
terraform apply
terraform apply --target module.workload
```

## Security considerations
For security reasons, a random password and an SSH key-pair are auto-generated per instance.
This means that each instance has a different password and a different authorized SSH key.
They are stored in the `tfstate` so execute a `terraform state list` and then show the resource you need
by using `terraform state show ···`

When the `terraform apply` is complete, all the SSH private key files are exported in order
to allow you to access or manage them.

There is a special folder called `external-ssh-keys` which was created for the special case that several
well-known SSH keys must be authorized in all the instances at the same time.
There is a special directory located in `modules/workload/external-ssh-keys`.
This was created for the special case that several well-known SSH keys must be authorized
in all the instances at the same time.
This can be risky and must be used under your own responsibility. If you need it, place some `.pub` key files
inside, and they will be directly configured and authorized in all the instances.

0 comments on commit a550013

Please sign in to comment.