Zero Trust security with HashiCorp Vault and AWS (PRT239)
summary
Claims a Zero Trust posture where every request is authenticated, every action is authorized, and data is always protected. Demonstrations center on Vault (machine credentials, AWS Secrets Engine for one-time IAM credentials, Vault+KMS/HSM key rotation), Consul (multi‑cloud service mesh, automated TLS service‑to‑service connections and network stitching), and Boundary (human-to-machine access with workers, hidden target IPs, no copy/paste credentials). Vault reports ~16M downloads/year and “trillions of secrets served”; HCP managed options remove most operational toil.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 0:40What is HashiCorp
- 3:37Simple
- 4:47Modern infrastructure
- 6:30Security challenges
- 7:46The City of Doors
- 10:05The Four Components
- 11:48HashiCorp Vault
- 15:17Vault in Kubernetes
- 17:11Different security workflows
- 17:48Using HashiCorp Vault
- 18:13Benefits of HashiCorp Vault
- 19:47House of Doors Model
- 20:13Service Networking
- 21:08Console
- 22:00Multicloud service mesh
- 22:58Network infrastructure automation
- 24:20Consoles focus
- 25:13Application focus
- 26:11Console selfmanaged
- 26:42Zero Trust
- 27:16Boundaries
- 27:47Challenges
- 28:40Identitybased access control
- 29:04Boundary on AWS
- 29:25Failure Zones
- 31:21Access
- 35:41Boundary
- 36:38HTTP Boundary
- 39:03AWS Vault
related talks
36mManaged Zero Trust Security With HashiCorp Cloud Platform
49mZero Trust Security
01h 02mIntroduction to Zero Trust Security
42mZero-Knowledge Architecture, or Leak-Free Secrets, with HC Vault
28mSecret Management with Hashicorp´s Vault
44mSecret Management with Hashicorp's Vault
31mSecure Your Multi-Cloud Delivery Pipeline with HashiCorp Vault
38mKeeping Secrets - A Practical Approach to Managing Credentials