Managing Secrets in Your Cloud Environment
summary
Central recommendation: stop putting credentials in code and centralize. Hands-on solutions compared: HashiCorp Vault (dynamic creds, but operationally heavy because of Vault unseal keys), AWS KMS + SSM Parameter Store (used at scale with a homemade chamber CLI to fetch secrets and enforce per-service IAM), and the new AWS Secrets Manager for built-in rotation. Notes: Segment reports thousands of secrets and hits SSM rate limits on mass boot, GCP lacks a Parameter-Store equivalent so use Cloud KMS + storage and enable data-access audit logs.
AI-written summary · about
chapters (17)
- 0:00Start
- 2:54Why Management of Secrets Is So Important
- 5:09Centralized Secret Management
- 6:11What Not To Do Putting Secrets in Code
- 6:47Differential Protection
- 8:05Encryption
- 8:22Rotation
- 8:55Separation of Duties
- 10:46Vaults
- 11:51Authentication Method
- 14:33What's Next
- 14:52Secrets Manager Service
- 15:29Aws Kms Key Management Service
- 16:10Aws Kms
- 16:45Ssm Parameter Store
- 25:52Secret Management Options
- 27:30Root Secret
related talks
47mManaging your Secrets in a Cloud Environment
30mSimplifying Secrets Management in the Public Cloud
29mBehind Closed Doors: Managing Passwords in a Dangerous World
38mKeeping Secrets - A Practical Approach to Managing Credentials
41mModern Security with Microservices and the Cloud
55mHandling secrets in cloud-based applications
28mYour Secrets in Cloud-Based Key Management Services
26mSecret Management in Kubernetes: The GitOps Way - Benjamin Ritter
