# 🔍 Terraform Modular EKS + Istio — The Part Nobody Explains

When I first modularized my Terraform for EKS, everything looked clean… Until it didn’t work. Modules were correct. Code was clean. Folder structure looked “perfect”. But Terraform was behaving in ways I didn’t expect. Resources were creating in weird order. Dependencies felt invisible. And debugging became painful. That’s when I realized: 👉 Understanding Terraform syntax is easy 👉 Understanding how Terraform thinks is the real game This blog is about that shift. 🧠 The Biggest Misconception Initially, I thought Terraform runs like a script: Step 1 → Step 2 → Step 3 But that assumption is completely wrong. Terraform doesn’t execute line by line. 👉 It builds a dependency graph first , and only then decides what to create and in what order. Once this clicked, everything started making sense. 🧩 My Project Structure (Real Setup) Here’s how I organized everything: modularized/ ├── eks/ # Root module (entry point) │ ├── main.tf │ ├── variables.tf │ ├── providers.tf │ └── backend.tf ├── module