Multi-Cloud Provisioning — AWS + Alternative — Terraform & Infrastructure as Code

Vendor lock-in is one of the most strategically dangerous positions a technology organisation can occupy. When every workload is tied to a single cloud provider's proprietary services, switching costs — rewriting infrastructure configurations, retraining engineers, migrating data — become prohibitive even if the provider raises prices, degrades reliability, or discontinues services. Multi-cloud provisioning is the practice of deliberately distributing workloads across two or more cloud providers, using each for what it does best while retaining the ability to shift workloads when needed. Terraform is the industry's preferred tool for multi-cloud infrastructure precisely because its provider model abstracts the differences between cloud APIs behind a consistent HCL configuration language. A Terraform configuration can provision AWS VPCs and GCP GKE clusters in the same `terraform apply`, with the same state file tracking all resources across both clouds. This lesson covers the mechanics of multi-provider Terraform configurations, provider aliasing, and practical multi-cloud architecture patterns.

Analogy🏏Cricket

🏏 Think of it like cricket: Before standardised cricket rulebooks existed, every ground played by its own local customs — different LBW interpretations, different wide-ball rules, inconsistent DRS protocols. A touring team playing in a new city had to learn an entirely different set of rules. The standardised ICC rulebook is IaC: a version-controlled document that specifies exactly how cricket is played anywhere in the world. When any ground host asks 'how should this match be set up?', they apply the rulebook — not their memory, not local tradition, not a wiki page from 2019. Every ground becomes reproducible because they're all applying the same version-controlled specification. The insight is that codifying rules enables consistency at scale — you can run a thousand simultaneous cricket matches and every one follows the same rules because they all reference the same canonical document.