Configuration as Code
summary
Using HashiCorp Terraform to manage HashiCorp Vault configuration as code: practical stories from HelloHippo about fully describing Vault via Terraform. Covers what worked and what didn’t, pitfalls to expect, and operational security topics such as secret and access-key rotation, plus how HelloHippo applies a Configuration-as-Code methodology.
AI-written summary · about
chapters (24)
- 0:00Welcome
- 1:06About me and Vault
- 4:18HashiCorp Vault overview
- 6:02Vault deployment planning
- 8:52Deployment architecture
- 10:19Vault migration with Terraform
- 12:31Secret config problems
- 14:00Vault security and resilience
- 16:48Terraform split for install and config
- 17:53Vault config start and tokens
- 18:34Vault token issuance
- 21:26Vault auth methods
- 23:09LDAP backend and policies
- 25:00Vault policies configuration
- 26:48Terraform state security
- 27:30App auth in Kubernetes and AWS
- 29:37KV secrets engine
- 31:00Temporary credentials benefits
- 33:07AWS console temporary access
- 34:16DB temporary access challenges
- 35:20Secret rotation and static accounts
- 36:44Terraform-Vault integration issues
- 39:10Dynamic secrets mistakes
- 40:13Conclusion and Q&A
related talks
31mHashiCorp Vault Configuration as Code via HashiCorp Terraform: Stories From the Trenches
46mVault configuration as code via HashiCorp Terraform - Stories from trenches
42mHCP Vault Learn Lab: Operations with Terraform
36mInfrastructure as Code with Terraform
23mManaging Vault with Terraform
42mManage Vault programmatically with Terraform
23mHashiCorp Vault and Getting Day 2 Operations Right
18mCodify Your JWT-OIDC Vault Auth Method with Terraform