Scaling Vault Enterprise with a cell architecture
summary
Adobe runs two billion transactions per month through Vault and scales by sizing up Graviton EC2s and preferring 5-node clusters with added non‑voting nodes for load spreading. Writes are routed to the Raft leader via AWS ALB to cut write latency; Vault Benchmark is used for lab comparisons. Operational controls include rate limits, OIDC group limits (~200 per token), namespace-based delegation backed by opinionated Terraform modules and migration tooling to reorganize secrets and move hot workloads to additional clusters.
AI-written summary · about
chapters (9)
- 0:00Introduction and Adobe Vault
- 3:13Capacity management challenges
- 9:01Vault Benchmark tool insights
- 11:36Rate limiting and quotas
- 11:57Terraform-based Vault configuration
- 17:36Current Vault deployment model
- 20:07Secret migration tooling
- 22:13Scaling with cell architecture
- 26:25Q&A and closing
related talks
26mVault in BBVA, Secrets in a Hybrid Architecture
41mAutomating Multi-Cloud, Multi-Region Vault for Teams and Landing Zones
27mVault At Scale
25mLessons learned from deploying Vault at scale
26mSecrets at scale: GitHub’s 9-year evolution with HashiCorp Vault
51mIntroduction to Vault
28mVault Roadmap
27mVault Futures: The Roadmap Ahead for Vault