Keeping Secrets - A Practical Approach to Managing Credentials
summary
Uses HashiCorp Vault as Vault as system of record with Consul HA storage, per-user tokens, and audited TLS access; CI (Rake + s_build gem) retrieves secrets into memory, builds environment‑agnostic Docker images, then Terraform deploys to AWS ECS/ECR and injects secrets as environment variables at start time — never writing them to disk. Workflows create ephemeral PR deployments for validation then destroy them, support AWS backend dynamic credentials, and enforce a weekly restore drill and inject secrets at runtime.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:28The Problem
- 5:23What is Vault
- 7:08Storage backends
- 13:40Procedures
- 17:05Basal
- 21:35Prepare
- 25:30Deploy
- 31:07Questions
related talks
40mA Better Way To Manage Secrets
28mSecret Management with Hashicorp´s Vault
43mSecret Management with Hashicorp's Vault
28mHow to Store Secrets—and When Do You Need Them—in HashiCorp Vault
41mHiding secrets in a Vault
50mDevOps: Shhhh! It's a secret! - HashiCorp Vault
29mBehind Closed Doors: Managing Passwords in a Dangerous World
30mEfficiently share and manage secrets across applications with HashiCorp Vault
