Adobe’s journey of delivering HashiCorp Vault at Adobe Scale
summary
Adobe describes rolling Vault into a three-region, production-ready service on AWS after consolidating 27 to 3 clusters, moving to integrated storage, and shifting some nodes to ARM for ~22% compute savings. Onboarding time for developers drops from 46 hours to sub-30 minutes through focused automation and a planned Vault easy button, audit evidence collection shrinks from weeks to about two days, and Vault handles ~2–3 billion HashiCorp-related transactions per month.
AI-written summary · about
chapters (7)
- 0:00Introduction and Adobe overview
- 3:34Vault adoption and early challenges
- 10:15Simplifying Vault architecture
- 16:56Lessons learned and mistakes
- 22:11Security gains and cross-team impact
- 25:43Operations model and ownership
- 28:38Future Vault wishlist
related talks
27mVault At Scale
41mAutomating Multi-Cloud, Multi-Region Vault for Teams and Landing Zones
29mDesigning High Availability for HashiCorp Vault in AWS
26mSecrets at scale: GitHub’s 9-year evolution with HashiCorp Vault
51mRun modern PKI workflows with HCP Vault on AWS
23mHashiCorp Vault and Getting Day 2 Operations Right
29mAdopting HashiCorp Vault: Deployment, Adoption, and Beyond
27mVault Futures: The Roadmap Ahead for Vault
