How To Secure Your MicroServices
summary
Uses Consul and Vault to replace copy‑pasted connection strings with dynamic Postgres credentials that Vault creates and later revokes, demonstrated from a .NET app using Vault’s database plugin and AppRole + SecretID workflow. Demo shows credentials issued with 10-minute leases, automatic renewal, and Vault audit logs; deployment integrates with Octopus/Terraform or a scheduler (Nomad) that injects secrets as env vars so the solution is automated, auditable, and actually works.
AI-written summary · about
chapters (14)
- 0:00Intro
- 7:05Project Goals
- 9:35Live Demo
- 17:27Authentication
- 18:31App Roles
- 19:04Pipeline
- 21:00Updating
- 21:28Octopus
- 23:50Demo
- 27:23Tradeoff
- 29:45Nomad Configuration
- 31:02Nomad Demo
- 35:50Why shortlived credentials
- 37:06Audits
related talks
31mModern Security with Microservices and the Cloud
27mStop the (Password) Insanity! - Managing Credentials with HashiCorp Vault
42mDynamic credentials for Kubernetes workloads with Vault and VSO
41mModern Security with Microservices and the Cloud
31mModern Security With Microservices And The Cloud
53mDynamic Database Credentials
51mIntroduction to Vault
47mThe Secret to Handling Dynamic Secrets