How To Manage Keycloak Securely by Using Terraform on Google Cloud
summary
Manages Keycloak configuration with Terraform and runs apply from a Cloud Build private pool so runs originate from a single global IP; a VPC peering plus a NAT VM routes build egress to that IP to satisfy IP allowlists. Secrets live in Google Secret Manager and Terraform reads them via a data block, removed from code; IAM and VPC Service Controls restrict access. Pipeline has two environments (dev → prod), Slack mentions on failures, and the system is deployed and operational.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:03Keycloak use cases
- 3:09TerraformによるKeycloak構成管理
- 4:57Security challenges
- 6:20Google Cloud Build
- 7:49Private IP controls
- 9:12Secret manager
- 10:16CD pipeline summary
- 11:23Q&A
related talks
23mFully SaaS-Based DevOps with Terraform Cloud and GitLab
32mGotchas Using Terraform in a Secure Delivery Pipeline
11mCommon Pitfalls When Using Terraform and How to Avoid Them
01h 00mGotchas using Terraform in a secure delivery pipeline
13mMaking cloud security more human
34mZero trust CI/CD pipeline
42mSpinGo: Terraforming Your Way to Spinnaker In Google Cloud
23mManaging Vault with Terraform