Software Engineer at Bayer transitioning into Cloud and DevOps engineering, with 8+ years of software development experience across mobile and web. Currently working hands-on with AWS infrastructure, Terraform, and Kubernetes in a production environment. ⚙️ Technical Foundation AWS Certified Solutions Architect Associate and Cloud Practitioner, currently pursuing HashiCorp Terraform Associate, with hands-on focus on: - Infrastructure as Code (Terraform, Helm) - CI/CD pipelines (GitHub Actions, OIDC-based AWS authentication) - Container orchestration (AWS EKS, Kubernetes) - Serverless architecture (Lambda, S3, SNS, SQS, API Gateway) At Bayer I work alongside senior infrastructure engineers on production AWS EKS deployments, writing Terraform for real infrastructure, and building automated pipelines. Open to connecting with cloud professionals and exploring Cloud Engineer, DevOps Engineer, and Platform Engineer opportunities in Ottawa and remote. 🤝
Markdown supported · ⌘↵ to post
Atul Vishwakarma
Really enjoyed this post. Terraform starts off feeling simple when everything is in one file, but once the infrastructure grows, that approach becomes hard to maintain very quickly. I like how you showed the practical path from a single-file setup to a module-based structure instead of just talking about theory.
What stood out to me most was the readability and reusability angle. Modules do add a little upfront structure, but in the long run they make the codebase much easier to understand, scale, and hand over to another engineer without confusion.
This is the kind of refactoring that doesn’t always feel urgent at first, but once you’ve lived with a messy Terraform codebase, you immediately see the value. Solid write-up.