Secure Your Multi-Cloud Delivery Pipeline with HashiCorp Vault
summary
Shows a concrete pipeline replacement for static high‑privilege credentials using HashiCorp Vault as an identity broker across private cloud plus multiple AWS accounts. Implements AppRole and AWS auth, Vault policies that enforce least privilege, and Secret Backends (KV, AWS, SSH) to issue dynamic secrets instead of baked‑in keys. Demonstrates automated rotation and short leases (examples mention 5‑minute tokens and daily rotation), centralized audit logs for every Vault request, and a working deploy pipeline that removes long‑lived credentials.
AI-written summary · about
chapters (8)
- 0:00Introduction to multi-cloud security
- 2:36Challenges in multi-cloud pipelines
- 6:21Centralizing secrets management with Vault
- 12:39Dynamic secrets and rotation policies
- 19:15Demo: Configuring Vault for deployment
- 24:11Identity-based access control
- 27:05Audit logs and compliance tracking
- 30:45Summary and Q&A
related talks
22mSecuring AWS Accounts With HashiCorp Vault
38mKeeping Secrets - A Practical Approach to Managing Credentials
38mDon’t Break Your Pasta! Good Practices for Securing Your Pipelines
30mEfficiently share and manage secrets across applications with HashiCorp Vault
30mSimplifying Secrets Management in the Public Cloud
30mHashiCorp Vault and Jenkins - Leveraging AWS IAM to Empower a Hybrid Scenario
28mSecret Management with Hashicorp´s Vault
44mSecret Management with Hashicorp's Vault