AWS Builder Center

My AWS & DevOps Journey: From Learning the Basics to Building Real Projects

I’m documenting my journey of learning AWS and DevOps, from Linux, Git, and Docker to CI/CD, Terraform, Kubernetes, and cloud deployment. This article shares what I’ve learned, the challenges I’ve faced, and the projects I’m building along the way.

My AWS & DevOps Journey

I started learning AWS and DevOps because I wanted to understand what happens behind the scenes when an application goes from code on a laptop to a real application running in the cloud.
At first, concepts like EC2, Docker, Jenkins, VPC, Terraform, and Kubernetes felt completely different from each other. But as I started working with them, I realized that they are all connected.

Where I Started

My journey started with the basics:
  • Linux and Ubuntu
  • Git and GitHub
  • Networking fundamentals
  • Python
  • Basic cloud concepts
Learning Linux was especially important because most DevOps tools and cloud servers rely heavily on Linux.

Moving Into AWS

After understanding the basics, I started exploring AWS.
I began with services such as:
  • Amazon EC2
  • IAM
  • Amazon S3
  • VPC
  • Security Groups
  • Amazon RDS
  • CloudWatch
One of the things I found interesting about AWS was understanding how different services work together.
For example, an application can run on an EC2 instance, store files in S3, use RDS for its database, and use CloudWatch for monitoring.

Learning Docker

Docker was another important step in my journey.
Instead of installing all application dependencies directly on my machine, I learned how to package an application and its dependencies inside a container.
I also started working with Docker Compose to run multiple services together, such as a frontend, backend, and database.
This helped me understand the idea of containerized applications much better.

CI/CD with Jenkins

Next, I started learning CI/CD.
I worked with Jenkins and learned how a pipeline can automate tasks such as:
Code → Build → Test → Deploy
I also learned about GitHub integration, Jenkins pipelines, build triggers, and Jenkinsfiles.
Working with Jenkins taught me that automation can save a lot of repetitive work.

Infrastructure as Code

After that, I started exploring Terraform.
Instead of manually creating cloud infrastructure through the AWS console, Terraform allows infrastructure to be defined as code.
This made me interested in the concept of Infrastructure as Code (IaC) and how infrastructure can be version-controlled just like application code.

What I'm Learning Next

There is still a lot I want to learn.
My current roadmap is:
Linux → Git → AWS → Docker → Jenkins → Ansible → Terraform → Kubernetes → Monitoring → DevSecOps
I also want to improve my knowledge of:
  • Kubernetes
  • Helm
  • Prometheus
  • Grafana
  • AWS networking
  • Cloud security
  • Python automation
  • DevSecOps

Building Real Projects

For me, the most important part of learning DevOps is not just watching tutorials.
I want to build projects where I can actually use these technologies together.
My goal is to build an end-to-end project like:
GitHub → Jenkins/GitHub Actions → Docker → AWS → Terraform → Kubernetes → Monitoring
Projects like these help me understand how the individual tools fit together into a complete DevOps workflow.

Lessons So Far

One thing I've learned is that DevOps is not about knowing every tool.
It's more about understanding the problem you're solving and choosing the right tools to automate, deploy, monitor, and maintain applications.
I've also learned that troubleshooting is a big part of the journey. Things don't always work on the first attempt, but debugging those problems has probably taught me more than simply following a tutorial.

What's Next......?

I'm still at the beginning of my AWS and DevOps journey, but I'm enjoying the process of learning by building.
My long-term goal is to become a DevOps Engineer with strong knowledge of AWS, automation, CI/CD, containers, and Infrastructure as Code.
I'll continue documenting what I learn and the projects I build along the way.
One step, one project, and one deployment at a time. ☁️🐳🚀
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article