Self-service infrastructure is no longer a dream
summary
Platform teams show a working pattern that combines Terraform Cloud, dynamic provider credentials via OIDC and a serverless Terraform reference engine to let developers self-provision without static IAM keys. The demo provisions S3 websites through AWS Service Catalog, Terraform Cloud no-code workspaces, and HCP Waypoint templates; runs enforce Sentinel/OPA policies and run module tests using Terraform 1.6’s test framework. HashiCorp cites 92% reliance on platform teams, and the demos complete plan/apply and upgrades successfully.
AI-written summary · about
chapters (25)
- 0:00Introduction and agenda
- 1:02Collaboration and agenda
- 1:40AWS and HashiCorp partnership
- 2:37The need for self-service
- 3:46Platform team challenges
- 5:21Self-service challenges
- 7:27Guiding principles
- 9:08Path to self-service
- 10:29Cloud maturity journey
- 12:13Terraform Cloud overview
- 13:30TFC features for scaling
- 14:47Dynamic credentials
- 16:39Policy and run tasks
- 17:47Module management
- 19:37Testing framework evolution
- 22:00Terraform test framework
- 24:35Registry testing and AI
- 26:23No-code provisioning
- 28:18No-code upgrade pipeline
- 29:06HCP Waypoint overview
- 30:44Service Catalog integration
- 32:48Demo: Service Catalog
- 38:51Demo: No-code provisioning
- 47:28Demo: HCP Waypoint
- 52:16Conclusion and resources
related talks
27mAdvanced Multipurpose Infrastructure: A Self-Managed Cloud Environment with HashiCorp Terraform
35mTerraform-Powered Platform-as-a-Service
31mCommodified IaC using Terraform Cloud
55mBest practices
21mAccelerating cloud transformation with Terraform: A World Bank success story
33mBuilding applications with infrastructure as code
29mInfinity and beyond: Scaling Terraform for the global enterprise
36mInfrastructure as Code with Terraform