Simplifying remote access in dynamic environments with Boundary
summary
Boundary automates discovery and access control for AWS EC2 and Azure VMs using tag-based Dynamic host catalog, shown importing 10 newly launched EC2 instances into the catalog automatically. Identity integrates via OIDC/LDAP (Azure Entra ID, Okta), groups map to RBAC roles, and Privileged Identity Management (PIM) enables time‑limited elevation. Credentials are fetched from Vault or stored in Boundary and applied via credential injection for SSH, RDP, and HTTPS. A client-side transparent sessions beta makes access invisible and VPN-like while enforcing least‑privilege.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:41Remote access challenges
- 4:11Boundary user experience
- 7:42Admin automation benefits
- 10:32Dynamic host catalog demo
- 13:20User identity integration
- 15:29Azure Entra ID setup
- 18:38RBAC role assignment
- 20:02Self-service access requests
- 21:52Privileged Identity Management
- 24:41End user workflow simplification
- 26:04Transparent session demo
- 30:19Security and automation summary
- 31:01Resources and next steps
related talks
37mSecure Remote Access With Boundary and Azure AD
29mZero Trust Security and Identity Management with Boundary
32mSplicing the Identity Based Access Gene into your Infrastructure DNA with HashiCorp Boundary
34mHashiCorp Boundary: Then & Now
15mBoundary: Then and Now [Abridged]
24mSecure and Scale Access to Your Multi-Cloud Resources Using HashiCorp Boundary
39mExplore HashiCorp Boundary
21mSecure Remote Access with HCP Boundary