𝐂𝐥𝐢𝐜𝐤𝐎𝐩𝐬 𝐰𝐨𝐫𝐤𝐬 𝐨𝐧𝐜𝐞. 𝐈𝐚𝐂 𝐰𝐨𝐫𝐤𝐬 𝐞𝐯𝐞𝐫𝐲 𝐭𝐢𝐦𝐞. 𝐈𝐭’𝐬 𝐪𝐮𝐢𝐜𝐤 𝐭𝐨 𝐬𝐩𝐢𝐧 𝐮𝐩 𝐫𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 𝐦𝐚𝐧𝐮𝐚𝐥𝐥𝐲: VPCs, subnets, security groups, roles, task definitions 𝐁𝐮𝐭 𝐡𝐞𝐫𝐞’𝐬 𝐭𝐡𝐞 𝐩𝐫𝐨𝐛𝐥𝐞𝐦: How do you track what changed? How do you repeat it consistently? How do you share it with someone else? What happens months later? 𝐓𝐡𝐚𝐭’𝐬 𝐰𝐡𝐞𝐫𝐞 𝐓𝐞𝐫𝐫𝐚𝐟𝐨𝐫𝐦 (𝐚𝐧𝐝 𝐈𝐚𝐂 𝐦𝐢𝐧𝐝𝐬𝐞𝐭) 𝐜𝐨𝐦𝐞𝐬 𝐢𝐧: Version control, repeatability, structure, no drift, single source of truth. The console is great for exploration, but when you’re aiming for production, clickOps becomes technical debt fast. IaC forces you to design your infrastructure, not just build it. #terraform #iac #devops
Vembarasan T
1mo
Saqib TariqI would say If I can’t "git diff" it, I won't trust it.
Abdulrahman Said
1mo
Great post bro👏
Totally agree, ClickOps feels fast until you have to debug what changed 3 weeks later 😅. Terraform forces you to think ahead instead of just clicking your way through fixes. Once I switched to IaC, I realized half my “infra issues” were really just missing documentation and drift. How are you handling your Terraform state these days, remote backend with DynamoDB locking or using Terraform Cloud?