Ansible is a great orchestration tool. The low barrier to entry and simplicity of Ansible are why so many people that start using it love it. But there is one feature in Ansible that probably should be used more often. That feature is Ansible Vault.
DevOps'ish is on hiatus and is not taking new subscribers at this time. Stay tuned to Chris Short's web site for details on future projects and when DevOps'ish will relaunch.Thank you to all subscribers for your years of support.
“Vault” is a feature of ansible that allows keeping sensitive data such as passwords or keys in encrypted files, rather than as plaintext in your playbooks or roles. These vault files can then be distributed or placed in source control.
This means you can store just about anything in Ansible files. SSH keys, MySQL user passwords, and secret API keys are all fair game in Ansible Vaults. Then you can safely check this data into your repo with a reasonable expectation that it is safe from Github crawlers and other prying eyes.
The best use case for Ansible Vaults are your variable files (group_vars and host_vars). I have a quite a few group_vars and not so many host_vars. It’s nice to be able to store secrets as reusable variables. Keeping them all in one place is even better. I also take it a step further by having a policy of, “If one variable file is an Ansible Vault they’re all Ansible Vaults.” Why? Allow me to explain…
Creating an Ansible Vault
ansible-vault create BARF.yml
- Enter Vault Password at Prompt
- Confirm Vault Password
- Input your data
- Save file
You can no longer use vim (or Emacs, nano, etc.) to edit Ansible Vault files… They’re encrypted!
Ansible Vault adds a layer of security so it’s inherently harder to use (but not much harder). Don’t make it harder by sporadically encrypting some variable files and not others. Waste the handful of kilobytes of disk and make all your variable files Ansible Vaults.
Previously, I’ve given a one-liner on how to Grep Multiple Ansible Vault Files that is based off this model as well.
Editing an Ansible Vault
ansible-vault edit ~/BARF.yml
- Enter Vault Password at Prompt
- Edit your data
- Save File
Ansible Vault files, at first blush, seem a little cumbersome to work with. But, the good folks at Ansible gave us
vault_password_file Configures the path to the Vault password file as an alternative to specifying –vault-password-file on the command line
vault_password_file is a file with your Ansible Vault password in it. For example:
~/.vault is a valid place for a vault_password_file. Your vault_password_file should be outside of any public repository and only readable/writable by you. You can specify vault_password_file as a command line argument:
ansible-vault edit --vault-password-file ~/.vault BARF.yml
You can define vault_password_file in your Ansible Configuration file and never have to use
--vault-password-file nor be prompted for the password on the CLI (you will see an error if the vault_password_file does not exist).
I have taken this a step further and created some helper scripts so the various Ansible Vault commands can be run quickly and easily. You can find the ansible-vault-helpers on Github or download them as a zip file.
The ansible-vault-helper scripts assume your Ansible Vault password is in a file (outside of any public repo and only readable/writable by you) in your home directory, specifically, ~/.vault.
Scripts are intended to be somewhere in your path for convenience. Adding this repo to your path is highly recommended.
More on Ansible Vault at http://docs.ansible.com/ansible/playbooks_vault.html
avcreate: Creates Ansible Vault files
avdecrypt: Removes the encryption from Ansible Vault files (converts file to plaintext)
avedit: Decrypts file for use in your text editor (vim for Ansible Vaults)
avencrypt: Encrypts file using Ansible Vault
avview: Read-only view of an Ansible Vault file (less for Ansible Vaults)