Secret Management with Hashicorp´s Vault
summary
Explains concrete Vault setups and what actually works: multiple auth backends are used (tokens, LDAP, GitHub, AWS IAM, Kubernetes, AppRole), Vault issues dynamic database credentials (example: 1‑hour TTL, 240‑hour max TTL) and PKI short‑lived client certs (example: 18 hours), and supports SSH one‑time passwords and a kubernetes auth with init container that shares a token via a volume. Shows Vault creating and revoking DB users, issuing AWS STS creds and TLS certs, and a real project where developers get LDAP→AWS/DB access while apps authenticate via Kubernetes and it works in production.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:45Executive Summary for Vault
- 7:37Configure Vault
- 15:31Static Secrets
- 16:06Dynamic Secrets
- 17:35Developer Configures Vault
- 18:06Create a New Dynamic User
- 18:36How To Create a Dynamic Secret
- 19:49Aws
- 22:03Ssh
- 24:41Vault Policies
- 27:23Recap How Vault Works
related talks
44mSecret Management with Hashicorp's Vault
43mSecret Management with Hashicorp's Vault
40mA Better Way To Manage Secrets
38mKeeping Secrets - A Practical Approach to Managing Credentials
51mIntroduction to Vault
29mIntro to secrets management using Vault
30mEfficiently share and manage secrets across applications with HashiCorp Vault
31mVault and Secret Management in Kubernetes
