vault-init
Automate the initialization and unsealing of HashiCorp Vault on Google Cloud Platform.
by kelseyhightowerGo
Commit activity
Last 12 weeks · 0 commits
Community health
2 of 6 standards met
42
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · 1 in progress · Last activity 7y ago
See all on GitHub →
Please refer to this issue for more details: https://github.com/sethvargo/vault-on-gke/issues/70
Hi Kelsey, Hope you are doing well!!! I have been following your youtube videos, blogs to know the practices to be followed on different aspects specifically on container world. Recently i was evaluating the vault auto unseal feature where i have consul as its storage backend and AWS KMS for auto unseal integration, both consul and vault are running as container workload on k8s platform. I was able to evaluate auto unseal correctly. Post this i was looking about the vault auto init, as i was performing it manually during initial setup. After some googling i landed up on your github repo, i read about it but didn't get it completely. It would be very helpful for me if you can spare some time and share your expert guidance to me in same. 1. process of vault auto init 2. how to retrieve the master and recovery keys Pointing to the relevant available document is also helpful. Thanks in advance Sandeep
This pull request adds support for Vault deployments in AWS. It follows the same idea as the Google Cloud Platform implementation, utilizing AWS KMS for encrypting/decrypting the unseal keys, and storing the encrypted files in S3. Added env variable to append a prefix to the encrypted files when storing/reading from storage. Note: Vault dose support using AWS KMS as a seal wrapper, however this is currently only available in Vault Enterprise.
Recent fixes
These seemed to be needed when I was setting up vault based on https://github.com/sethvargo/vault-on-gke, with an upgraded Vault container: . I tried it out with as well, and it worked. Not sure if you want to merge this or if handling newer vault versions is even a priority, but this seemed like the easiest way to put it on your radar. Thanks!
vault-init is not closing the connection to the vault-server:
Structured data for AI agents
Repository: kelseyhightower/vault-init. Description: Automate the initialization and unsealing of HashiCorp Vault on Google Cloud Platform. Stars: 148, Forks: 59. Primary language: Go. Languages: Go (97.5%), Dockerfile (2.5%). License: Apache-2.0. Open PRs: 1, open issues: 2. Last activity: 7y ago. Community health: 42%. Top contributors: sethvargo, kelseyhightower.