Live data from Hacker News

HashiCorp and Google: easing secret and infrastructure management

cloudplatform.googleblog.com

21–30 of 78 posts

Re: HashiCorp and Google: easing secret and infrastructure management

#21

What do people here use to store and source-control secrets/almost-secrets and make them available to (pick n) terraform/ansible/salt/chef/...? I've heard a lot of good things of Hashicorp Vault ( https://www.vaultproject.io ) but been hesitant to go with it.

We use StackExchange's blackbox [1] to check in GPG encrypted secrets into our monorepo (contains both ansible deployment playbooks and the code itself). This way, we can introduce secrets and the code that uses it in a single commit!

[1] https://github.com/StackExchange/blackbox

Re: HashiCorp and Google: easing secret and infrastructure management

#22

What do people here use to store and source-control secrets/almost-secrets and make them available to (pick n) terraform/ansible/salt/chef/...? I've heard a lot of good things of Hashicorp Vault ( https://www.vaultproject.io ) but been hesitant to go with it.

Here's a great blog post about how we use it here at Fleetsmith (disclosure - I work there)

http://blog.fleetsmith.com/authenticating-to-hashicorp-vault...

Re: HashiCorp and Google: easing secret and infrastructure management

#23
post #21

What do people here use to store and source-control secrets/almost-secrets and make them available to (pick n) terraform/ansible/salt/chef/...? I've heard a lot of good things of Hashicorp Vault ( https://www.vaultproject.io ) but been hesitant to go with it.

We use StackExchange's blackbox [1] to check in GPG encrypted secrets into our monorepo (contains both ansible deployment playbooks and the code itself). This way, we can introduce secrets and the code that uses it in a single commit! [1] https://github.com/StackExchange/blackbox

+1 for blackbox. Very nicely done!

Re: HashiCorp and Google: easing secret and infrastructure management

#24
post #21

Earlier quoted context omitted.

We use StackExchange's blackbox [1] to check in GPG encrypted secrets into our monorepo (contains both ansible deployment playbooks and the code itself). This way, we can introduce secrets and the code that uses it in a single commit! [1] https://github.com/StackExchange/blackbox

+1 for blackbox. Very nicely done!

Originally part of Puppet - those guys are masterful

Re: HashiCorp and Google: easing secret and infrastructure management

#25

What do people here use to store and source-control secrets/almost-secrets and make them available to (pick n) terraform/ansible/salt/chef/...? I've heard a lot of good things of Hashicorp Vault ( https://www.vaultproject.io ) but been hesitant to go with it.

I'm currently taking advantages of SaltStack's GPG renderer to store secrets in our version-controlled Salt code (see https://docs.saltstack.com/en/latest/ref/renderers/all/salt....).

Re: HashiCorp and Google: easing secret and infrastructure management

#26

I worry a lot about how these megacorps will treat "collaborators" vs "non collaborators" in the coming years. Obviously you can't just outright buy everyone, but they seem to be increasingly abusive towards technologies and teams that aren't on board with their interests and ideology. Actually I'm more worried about how Facebook and Amazon treat non compliance, but Google sure seems to be getting shadier every day.…

And the Googlers arrive right on cue, hahahaha

Could you please not do this?

https://news.ycombinator.com/newsguidelines.html

Re: HashiCorp and Google: easing secret and infrastructure management

#27
post #16

What do people here use to store and source-control secrets/almost-secrets and make them available to (pick n) terraform/ansible/salt/chef/...? I've heard a lot of good things of Hashicorp Vault ( https://www.vaultproject.io ) but been hesitant to go with it.

I almost never heard anything negative about vault until I did a presentation on all the troubles I had with it. Here are the slides about the issues I had: https://docs.google.com/presentation/d/1ipP2eB9pW5j3WDvzCGz9... At the end of the day, Vault gives you secret keys to manage which makes automating the unsealing process not fun if you want full automation. Talking with Armon from Hashicorp they planned to work o…

I unseal using ansible (with the unseal keys in ansible-vault) and automate the configuration fully through ansible. For example you can use the ansible expect module:

  - name: unseal 1
    expect:
      command: '/usr/bin/vault unseal'
      responses:
        'Key \(will be hidden\): ': "{{vault_seal_key_1}}"
      echo: yes
    when: vault_sealed_result.rc == 2 and vault_seal_key_1 is defined
    tags:
      unseal

Re: HashiCorp and Google: easing secret and infrastructure management

#28

What do people here use to store and source-control secrets/almost-secrets and make them available to (pick n) terraform/ansible/salt/chef/...? I've heard a lot of good things of Hashicorp Vault ( https://www.vaultproject.io ) but been hesitant to go with it.

Vault is a pretty good thing. For some time, we used chef attributes and environments, but by now we have migrate most stuff into vault. The migration was easy, because chef-attributes form a big JSON object, so you can translate that into a secret tree in vault in a straightforward way.

The worst part about vault is managing access in a secure way and granting access to the right parts imo. We leverage the pki backend (or rather, three dozen pki backends) to map nodes to their respective policies and that required quite a bit of tooling to make work. But now it does, it's secure, and if need comes, it should be easy to revoke secret access for a cluster.

Re: HashiCorp and Google: easing secret and infrastructure management

#29

What do people here use to store and source-control secrets/almost-secrets and make them available to (pick n) terraform/ansible/salt/chef/...? I've heard a lot of good things of Hashicorp Vault ( https://www.vaultproject.io ) but been hesitant to go with it.

We're on AWS so we use SSM Parameter Store. Works nicely with KMS and IAM.

Re: HashiCorp and Google: easing secret and infrastructure management

#30
post #10

What do people here use to store and source-control secrets/almost-secrets and make them available to (pick n) terraform/ansible/salt/chef/...? I've heard a lot of good things of Hashicorp Vault ( https://www.vaultproject.io ) but been hesitant to go with it.

Can't recommend Vault enough. By far the easiest and most capable solution to work with. The only downside I can point out is that the multi-cluster/region HA requires expensive enterprise licensing, but that is something most user cases don't require.

Did you use it with Kubernetes by any chance?
Post reply on HN