Learn Lab: SSH Credential Injection with HCP Boundary and Private Vault
summary
Demonstrates configuring HCP Boundary to inject SSH keys from a private Vault: run Vault Dev locally, store an SSH private key, deploy a self‑managed HCP worker (binary) with the cluster ID, register the worker, create Vault policies and a Vault-backed Boundary credential store and library, create a host/catalog/target (port 2222) and attach the library, then run boundary connect SSH to have the SSH credential injection happen so the client never sees the secret. Emphasizes private Vault access and that the worker on same network is required for injection to work.
AI-written summary · about
chapters (9)
- 0:00Introduction and setup
- 2:41Secrets brokering overview
- 6:27Prerequisites and planning
- 9:55Deploying the SSH target
- 12:22Worker and Vault setup
- 24:11Registering the worker
- 30:48Configuring Vault and Boundary
- 37:15Creating the SSH target
- 41:13Demonstration and Q&A
related talks
24mEmpowering credential injection at scale using Boundary
39mExplore HashiCorp Boundary
34mHashiCorp Boundary: Then & Now
42mHCP Vault Learn Lab: Operations with Terraform
15mBoundary: Then and Now [Abridged]
01h 06mRecord session activity with Boundary
32mSplicing the Identity Based Access Gene into your Infrastructure DNA with HashiCorp Boundary
32mThe End of Shared Passwords with Vault and Boundary