HashiCorp Vault and Getting Day 2 Operations Right
summary
Deploys must be Packer images built into CI/CD and provisioned with Terraform; policies, secrets engines and upgrades are codified so day‑2 changes are automated. Use Helm charts on Kubernetes, namespaces for multi‑tenancy, and integrated storage or Consul with HA; enable auto-unseal via cloud KMS. Schedule raft snapshots, test DR and backups, and feed Vault metrics to Prometheus/Grafana. Harden nodes (non‑root service account, disable core dumps), publish runbooks and an onboarding framework, and run a Vault community of excellence.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker background
- 1:27Day 2 operations goals and pillars
- 2:10Automate platform deployment and upgrades
- 5:00Ensure Vault reliability patterns
- 9:09Backups and disaster recovery
- 12:21Monitoring and observability
- 14:09Security hardening best practices
- 18:20Streamlining processes and onboarding
- 20:23Building a culture of excellence
related talks
29mAdopting HashiCorp Vault: Deployment, Adoption, and Beyond
29mAutomating Vault deployments: Patterns, pitfalls, and practical lessons
27mVault At Scale
23mUsing Hashicorp Vault in Kubernetes Clusters
23mManaging Vault with Terraform
46mVault configuration as code via HashiCorp Terraform - Stories from trenches
25mLessons learned from deploying Vault at scale
31mHashiCorp Vault Configuration as Code via HashiCorp Terraform: Stories From the Trenches