Securing Secrets at Scale: Integrating Ansible Automation with Conjur
summary
Concrete demo of Ansible + Conjur Open Source shows a simple home‑lab stack (Docker Conjur app, Postgres backend, TLS proxy) and a working flow: create YAML policies, use the host factory to mint short‑lived invite tokens, install the Ansible collection and lookup plugin, and have the control node obtain a machine identity without storing static SSH credentials. Notes include needing three roles of machines (workstation, controller, targets), TLS CA pitfalls, and full code on GitHub.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:46Secret management history
- 8:07Why Conjur
- 10:14Conjur home lab setup
- 12:01Conjur CLI basics
- 15:56Host factories for credentials
- 18:27Ansible integration setup
- 21:02Ansible with Conjur secrets
- 23:07Benefits of approach
- 24:53Extending to other systems
- 26:38Lessons learned troubleshooting
- 29:45Q&A
related talks
57mBest Practices for Securing Containerized Applications
29mGood Practices and Security for your Ansible Automation Platform 2
01h 34mAnsible 101
35mContainer security automation with Ansible
23mAutomation with Scalable & Secure SSH
26mWhere Does the Ansible Code You’re Running Come From?
36mGentle Introduction to Ansible
38mKeeping Secrets - A Practical Approach to Managing Credentials