How the Dynamic Duo of Vault and Puppet Tame SSL Certificates
summary
Automates PKI using HashiCorp Vault and Puppet to issue, distribute and auto-rotate certificates and CA chains, with a Puppet module that requests certs from Vault, writes keys to Linux paths or the Windows certificate store, and reloads services on change. Deployed to 500 servers with a 30‑day TTL, renewals run via Puppet agent every 30 minutes and complete with no outages. Demonstrates HashiCorp Vault + Puppet producing centrally signed, auto‑rotating SSL that works on Linux and Windows.
AI-written summary · about
chapters (14)
- 0:00Introduction to SSL certificates
- 3:36Problems with manual certificate management
- 6:05Security and DevOps requirements
- 7:30Introducing Vault and Puppet
- 8:32PKI workflow with Vault and Puppet
- 11:45Puppet code for certificate management
- 12:47How Puppet works
- 14:11Windows certificate challenges
- 15:39Windows solution with server-side functions
- 16:21Windows certificate binding
- 18:26Machine certificate pattern
- 19:29Deploying CA certificates
- 22:00Results and benefits in production
- 23:25Future plans and closing
related talks
13mAutomating PKI: Paddy Power Betfair's Journey with Vault
51mRun modern PKI workflows with HCP Vault on AWS
29mKeys, Certs and Vault: From DevSecOps to Post-Quantum
45mSecure Together: Consul + Vault
27mAddressing the growing threat of non-human identities with PKI
20mVault Automation with the HashiCorp Stack in OneMount
29mHow to get dynamic with secrets management
29mAdopting HashiCorp Vault: Deployment, Adoption, and Beyond