From a5500132e39d68aac6573b0a6384a2975da7f633 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alby=20Hern=C3=A1ndez?= Date: Mon, 25 Oct 2021 23:39:44 +0100 Subject: [PATCH] Fix Readme --- README.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index f43cd55..c84287c 100644 --- a/README.md +++ b/README.md @@ -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 ``` @@ -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. \ No newline at end of file