AI
Manual Ops and the Configuration Drift Problem
World Bank ran infrastructure across multiple Azure subscriptions and AWS accounts with no automation. Every team got a handcrafted platform. Configuration drift followed: dev environments bore no resemblance to production, and compliance tracking was manual. When the new CIO commissioned a developer experience study, the internal white paper documented what engineers already knew. Click-ops at scale compounds into thousands of unique platforms no team can govern consistently, and the cognitive load lands on developers and platform engineers equally.
The Module-to-Golden-Path Framework
The framework sits in three layers. At the base, hardened Terraform modules encode years of security controls for individual cloud services and publish to a private registry in HCP. Above that, templates stitch modules into consumable products. An Azure Kubernetes cluster template, for example, bundles the cluster with an ingress controller, App Gateway, and a Key Vault CSI driver. At the top, three golden-path products cover application, data, and AI workloads. Developers order them through an internal developer portal, which World Bank treats as the storefront for the whole platform.
Security Gates Inside the Provisioning Pipeline
A developer requests a golden-path product in the IDP. The request triggers a pipeline that creates Terraform Cloud workspaces, pre-fills variables, and connects a Git repository. When Terraform runs the plan, a RunTask integration routes the plan output to a security scanner before any resource deploys. Policy-as-code enforcement runs at the same gate. Only if both checks pass does infrastructure land in the hybrid environment, which spans Azure, AWS, GCP, and on-prem. Monitoring, logging, key management, and managed identity ship with every deployment, not as options, but as defaults baked into every template.
Results and Lessons from Shipping at Scale
Provisioning time dropped from 5 days to 30 minutes. World Bank deployed 27,000 cloud resources and now supports 700 applications on the platform. Standard adoption increased 70% as developers gravitated toward the golden paths instead of building bespoke stacks. Three lessons drove that outcome: automate one bottleneck end-to-end before touching the next; keep modules just flexible enough to work, not so configurable they become maintenance burdens; and make the golden path the easiest option available.
“Start small, standardize and automate” — Suneer Pallitharammal Mukkolakal
Notable Quotes
Start small, standardize and automate Suneer Pallitharammal Mukkolakal · ▶ 19:42
Your developers creative work truly Suneer Pallitharammal Mukkolakal · ▶ 21:12
this is not an option. Think of it as if Suneer Pallitharammal Mukkolakal · ▶ 15:22
Key Takeaways
- Hardened Terraform modules baked with security controls cut World Bank provisioning from 5 days to 30 minutes.
- Policy-as-code enforcement runs inside every Terraform plan, not after deployment, keeping 27,000 resources compliant.
- Toggle-based golden paths let developers add cache, object storage, or LLM APIs without calling platform engineers.