↓ Skip to main content
DevOps

Hashicorp vault

·1 min
Diagram from the HashiCorp documentation showing the layers of Vault

HashiCorp Vault overview: clients use the Vault API, which provides identity-based authentication, encryption and secrets management

“HashiCorp Vault is an identity-based secrets and encryption management system.”

— Hashicorp


In this blog I am attempting to use the vault for a custom kafka-keystore implementation. Points form the official documentation that you need to remember

  1. Vault encryption layer is referred to as barrier and is responsible for encrypt & decrypt vault data.
  2. Vault writes data to the configured storage in encrypted format.
  3. Vault starts in sealed state & before any operation can be performed it needs to be unsealed.
  4. By default Vault uses Shamir’s secret sharing to split the unseal key (configurable).
  5. Secret engines are components which store, generate or encrypt data.
  6. Secret engines are enabled at a path in Vault.
  7. Once a secret engine is enabled, once can interact with it directly at its path according to its own API.
Author
Samarthya
Engineer, learner, tinkerer. This is my trophy shelf of everyday work and leisure.

Related

Static IP’s in QEMU VM’s

·2 mins
Continuing from where I left in the blog before. If you are using looking to configure a static IP for your machines (may be your use case is similar to mine) this blog might be useful for you.

Running QEMu based VM’s on OSX M1

·5 mins
A popular choice in the OSS QEMu is an open source machine emulator (system emulation/usermode emulation) and virtualizer. Since I recently moved to Apple M1 silicone, I had not option of sticking to VirtualBox and was forced to relook at my options.

Vagrant-OSX

·1 min
In the previous blog, I was left with the error that had little information for me to debug. I realized since I migrated most of the files from my previous laptop it might be causing an issue.