Certified Terraform associate !

One goal I set for myself this year for all my development projects: managing infrastructure provisioning from the beginning using Infrastructure as Code (IAC).
Why?
👉 It forces me to define the architecture of my application from the start:
- Is it a service running on a provisioned EC2 instance 24/7?
- Is it an ECS task triggered by EventBridge?
- Are there Lambdas behind an API Gateway?
💡 By the way, I clarify my project requirements better: Do I need high availability? Do I have a certain tolerance for errors? Latency considerations? Resource constraints to consider?
👉 By provisioning with Terraform, I have a clear view of the cloud services I'm using. When I need to have an overview of my infrastructure resources, I just need to inspect my state file.
✅ Much clearer than any cloud provider's interface or CLI.
👉 AND MOST IMPORTANTLY, the day I come back to my project after a 3-month break, I can have the infrastructure up and running in 2 minutes.
✅ Implementing IAC is also the difference between a deployed project that will live on and dead code in a private repository.


