Automating Multi-Cloud, Multi-Region Vault for Teams and Landing Zones
summary
Deploys Vault Enterprise across AWS and Azure in an active‑active, multi‑region topology (about 16 clusters total, five‑node clusters and Console replicas), built from Packer‑built images and provisioned with Terraform and Terraform Cloud. Automates namespace self‑service: Terraform modules create namespaces, GitHub repos, TFC workspaces, and AppRole credentials (credentials are stored in an admin namespace and injected into workspaces). Handles Azure AD OIDC, JWT/GitHub runners, database engines (Snowflake), Datadog telemetry; main failures are TLS cert formatting and audit‑log permission replication breaks.
AI-written summary · about
chapters (7)
- 0:00Introduction and use cases
- 2:22Deployment strategy
- 7:30Technical architecture
- 13:48Lessons in deployment
- 17:36Automating namespaces
- 26:53Self-service modules
- 34:13Process and migration
related talks
55mBest practices
27mVault At Scale
29mAutomating Vault deployments: Patterns, pitfalls, and practical lessons
21mA secure automation platform: Terraform Enterprise, Ansible Automation Platform, & Vault Enterprise
15mA Diary of Change in the Dusty Financial Sector
23mHashiCorp Vault and Getting Day 2 Operations Right
27mScaling Vault Enterprise with a cell architecture
23mManaging Vault with Terraform