Infrastructure as Code insights, tutorials & news. Terraform, AWS, Ansible, CloudFormation & more. New articles weekly on Medium. By engineers, for engineers.
Arizona
Joined February 2026
- Tweets19
- Following17
- Followers5
- Likes9
IaC Weekly retweeted
#263 (sponsored by @dnsimple) - Gemini CLI Review Agents, Reliable Databricks Deployments, S3 Lifecycle Automation, HCP Terraform AI Guardrails
weekly.tf/p/issue-263-gemini…
IaC Weekly retweeted
Convert existing #Azure resources to #Terraform within one minute using the new #Microsoft #Terraform #VSCode Extension. Check it out here: marketplace.visualstudio.com…
IaC Weekly retweeted
• AWS supports Terraform.
• GCP supports Terraform.
• Azure supports Terraform.
• OCI supports Terraform.
• Alibaba Cloud supports Terraform.
• DO supports Terraform.
• Cloudflare supports Terraform.
• K8s clusters supports Terraform.
• Startups rely on Terraform.
• Enterprises standardize on Terraform.
Multi-cloud runs on Infrastructure as Code.
If the industry runs on Terraform…
What’s stopping you from learning it? 🚀
IaC Weekly retweeted
Terraform Folder Structure & How Real-World Teams Manage Cloud Infrastructure
In production, Terraform must be scalable, reusable, secure, and maintainable.
📁 environments/
Isolates infra per environment so dev changes never impact prod.
📂 dev/ (same for staging & prod)
• main.tf → Entry point. Calls reusable modules (network, compute, data).
• variables.tf → Input variables (region, CIDR, instance size, tags).
• provider.tf → Provider config, backend, version constraints, remote state.
• outputs.tf → Exposes LB DNS, VPC ID, instance IPs.
• dev.tfvars → Environment-specific values.
📁 modules/ → Heart of reusability (self-contained components)
📂 network/ (VPC Layer)
• VPC, subnets, IGW, NAT, route tables, SGs
📂 compute/ (App Layer)
• EC2, ASG, Launch Templates, EKS nodes
📂 data/ (Storage Layer)
• S3, RDS, DynamoDB
Why this matters in production:
✔ Prevents cross-environment mistakes
✔ Version-controlled infrastructure
✔ CI/CD friendly
✔ Team collaboration ready
✔ DRY & reusable
This is how real DevOps teams structure Terraform.
💬 Comment your team Terraform structure below👇
IaC Weekly retweeted
Use infrastructure as code even for small projects. The habit matters more than the time savings. I can’t remember the last time I did my projects through the manual console. Terraform everyday.
IaC Weekly retweeted
Terraform Core Commands Simplified 🚀
You don’t need 100 commands.
Master these.
Control most real-world infrastructure.
1️⃣ terraform init
→ Initialize project
→ Download providers
→ Configure backend
2️⃣ terraform validate
→ Check syntax
→ Catch config errors early
3️⃣ terraform fmt
→ Format code
→ Keep team consistent
4️⃣ terraform plan
→ Preview changes safely
5️⃣ terraform apply
→ Create / update infrastructure
6️⃣ terraform destroy
→ Delete infrastructure ⚠️
7️⃣ terraform state list
→ See tracked resources
8️⃣ terraform state show <resource>
→ Inspect resource details
9️⃣ terraform output
→ Display output values
🔟 terraform refresh
→ Sync state with real infrastructure
Master the basics once.
Everything else becomes predictable.
