Splicing the Identity Based Access Gene into your Infrastructure DNA with HashiCorp Boundary
summary
Claims that infrastructure can auto-provision access by treating access as code and shows a working stack: Boundary 0.7 for identity-based TCP brokering, dynamic host discovery plugins (AWS/Azure), the Vault OIDC bridge for non-OIDC identity sources, and Terraform to create resources and identity entries. Demo actually creates 2 VMs and a new user auto-connected — Boundary discovers hosts, evaluates managed-group filters, and brokers ephemeral Vault credentials so access is granted without manual Boundary edits.
AI-written summary · about
chapters (10)
- 0:00Introduction to Boundary
- 2:54What is HashiCorp Boundary
- 4:39Boundary Core Features
- 7:33Boundary Architecture Basics
- 10:22Dynamic Access Management
- 14:14Self-Managing Access Components
- 16:39Automation with Terraform
- 19:06Live Demo Setup
- 27:15Automated Access Workflow
- 29:45Resources and Community
related talks
39mExplore HashiCorp Boundary
34mHashiCorp Boundary: Then & Now
32mSimplifying remote access in dynamic environments with Boundary
15mBoundary: Then and Now [Abridged]
24mSecure and Scale Access to Your Multi-Cloud Resources Using HashiCorp Boundary
37mSecure Remote Access With Boundary and Azure AD
24mEmpowering credential injection at scale using Boundary
36mManaged Zero Trust Security With HashiCorp Cloud Platform