| 25 May 2022 |
 Mic92 | Not sure what the best channel for this question is, but do you have some automation/recommndation on how to bootstrap vault access on new machines? | 10:41:04 |
| 27 May 2022 |
 @grahamc:nixos.org | hardware? | 13:23:17 |
| @grahamc:nixos.org | * bare metal hardware that you own? | 13:23:23 |
| @grahamc:nixos.org | Mic92: ^ | 13:23:49 |
| @grahamc:nixos.org | for people I push them through logging in with google apps, for bare metal hardware I was working on this but didn't end up needing it: https://github.com/grahamc/vault-credential-yubikey | 13:24:45 |
| @grahamc:nixos.org | (but it completely works) | 13:24:56 |
| Mic92 | In reply to @grahamc:nixos.org
Mic92: ^ Let's say something cloud-vendor neutral. I need to be able to migrate if possible. | 13:25:26 |
| @grahamc:nixos.org | I'd use whatever auto auth method you can built-in to vault, trying to remain vendor neutral on that is (imho) missing out on a lot of really good security engineering | 13:26:34 |
| @grahamc:nixos.org | ie: AWS, Azure, GCP, etc. all have built-in automatic authentication mechanisms that I'd take advantage of | 13:27:13 |
| Mic92 | Do you usually deploy vault enterprise? | 13:27:24 |
| @grahamc:nixos.org | no | 13:27:36 |
| @grahamc:nixos.org | I don't have that kind of budget 😓 | 13:27:53 |
| Mic92 | Ok. How do you manage TLS? I just bootstrapped something with cfssl for now | 13:29:11 |
| Mic92 | And also how do you unseal? | 13:29:18 |
| @grahamc:nixos.org | letsencrypt | 13:29:20 |
| @grahamc:nixos.org | https://learn.hashicorp.com/tutorials/vault/autounseal-aws-kms | 13:29:50 |
| @grahamc:nixos.org | this is how we generally integrate vault with our services: https://github.com/DeterminateSystems/nixos-vault-service | 13:30:04 |
| Mic92 | Ah, I thought aws kms unseal is only available in the enterprise edition | 13:30:35 |
| @grahamc:nixos.org | nope | 13:30:40 |
| Mic92 | Which is why I did not use it | 13:30:43 |
| @grahamc:nixos.org | kms unseal + dynamodb as the backend | 13:31:03 |
| @grahamc:nixos.org | makes it relatively easy to deploy using AMIs and not permit SSH access to the vault hosts | 13:31:25 |
| @grahamc:nixos.org | (which is considered best practice for vault servers) | 13:31:58 |
| Mic92 | So to update your fault server, you have to upload a new AMI? | 13:33:50 |
| Mic92 | *vault | 13:33:54 |
| @grahamc:nixos.org | that is the recommended best-practice for managing Vault servers, yeah | 13:34:05 |
| @grahamc:nixos.org | https://learn.hashicorp.com/tutorials/vault/production-hardening | 13:34:41 |
| @grahamc:nixos.org | "Disable ssh" and "immutable upgrades" | 13:35:39 |
| Mic92 | I see. Also one can run multiple vault servers on the same dynamo backend, right? https://www.vaultproject.io/docs/configuration/storage/dynamodb | 13:36:46 |
| @grahamc:nixos.org | as long as you setup clustering | 13:36:56 |
