Build a self-service access management solution with GitHub and Boundary
summary
A self-service flow uses GitHub issues as the front end, GitHub Actions to call Boundary, Terraform to provision targets and update issue templates, and Vault to hold credentials; a developer files an issue, Actions provisions Boundary access, Boundary injects Vault credentials into the session, the client runs boundary connect and the session works, then closing the issue revokes access. Sensitive targets require admin approval via GitHub environments, Boundary workers sit in each network, and scheduled or ephemeral Terraform workspaces handle automatic revocation. GitHub issues drive automation
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:47Cognitive overload
- 4:34Access management
- 8:45GitHub workflow
- 16:11Key points
- 17:35GitHub and Boundary
- 19:20Module design
- 20:05Cleaning up expired access
- 22:24Summary
- 23:47QR code
related talks
37mSecure Remote Access With Boundary and Azure AD
40mEvent Driven Access Controls
29mZero Trust Security and Identity Management with Boundary
39mExplore HashiCorp Boundary
32mSplicing the Identity Based Access Gene into your Infrastructure DNA with HashiCorp Boundary
34mHashiCorp Boundary: Then & Now
44mAttacking & Defending Supply Chains. How we got Admin in your Cloud,...
56mHow to use GitHub Actions with Security in mind