Day 1 of My 90-Day DevOps Journey: Getting Started with Terraform and AWS

Hey everyone, I'm excited to share my 90-day DevOps journey! Each day, I'm diving into different projects, learning, and documenting every step. Whether you're starting out or curious about Terraform and AWS, join me on this adventure!

Getting Started with Terraform and AWS

So, I kicked off by exploring Terraform—an awesome tool for automating infrastructure across cloud providers like AWS. Think of it as your magic wand for spinning up servers and managing cloud resources.

Challenges: Initially, I struggled with Terraform's .tf configuration files. Getting the syntax right and understanding how to define resources took a bit of trial and error.

Solutions: I found that diving into the Terraform documentation and online tutorials helped clarify things. Also, joining forums and communities like Stack Overflow was a lifesaver for quick answers and tips.

Deploying My First Web Server

My goal was to deploy a simple web server on AWS using Terraform—a real hands-on learning experience.

Challenges: After setting up the instance, I ran into a roadblock—my public IP wasn't loading in the browser. Frustrating, right?

Solutions: I double-checked my security group settings in AWS. Turns out, I needed to tweak the inbound rules to allow HTTP traffic on port 80 (0.0.0.0/0 for the win!). It was about finding the balance between security and accessibility.

Navigating Security Groups and Permissions

Configuring AWS security groups was a critical part of the process.

Challenges: Understanding CIDR notation (0.0.0.0/0) was a bit tricky at first. I wanted to allow traffic from any IP to access my web server securely.

Solutions: I made sure to review AWS VPC (Virtual Private Cloud) settings and network ACLs. This helped me refine the security group rules without compromising on safety.

Debugging and Learning

Throughout this journey, I embraced the ups and downs of debugging.

Challenges: Encounter errors like InvalidAMIID.NotFound and Unsupported block type? Been there, solved that!

Solutions: Googling error messages became my second nature. Plus, reaching out to mentors and peers for guidance was invaluable. It's all about learning from mistakes and growing stronger in DevOps.

Sharing My Experience

I'm excited to share my progress with you all. It's not just about the technical stuff—it's about the journey, the challenges, and the wins. If you're starting your DevOps journey or diving into cloud engineering, I hope my story encourages you to keep pushing forward.