
Why Cloud? Why AWS? The Beginning of My DevOps Journey.
Every journey starts with curiosity. Mine started with a simple question: What happens behind the applications and services we use every day? That curiosity led me to Cloud Computing, and eventually to AWS. In this article, I’ll share why I chose Cloud, why AWS became my starting point, and how it is shaping the beginning of my DevOps journey. This is not the story of an expert—just the beginning of my journey, the things I’m learning, the challenges I’m facing, and where I hope to go next.
Why Cloud?
Why AWS?
The Beginning of My DevOps Journey.
Every technology journey starts somewhere.
For me, it started with curiosity.
I often found myself wondering about something that most of us use every day without thinking much about it:
Where does an application actually run?
When I open a website, use an application, upload a file, or access a service from my phone, there is a lot happening behind the scenes. Servers, networks, storage, security, databases, monitoring, and many other components work together to make that experience possible.
The more I learned about technology, the more I wanted to understand what was happening behind the screen.
That curiosity eventually introduced me to Cloud Computing.
And from there came another question:
Why AWS?
This article is about how I started answering those two questions and why Cloud and AWS became the starting point of my DevOps journey.
Why Did I Choose Cloud?
Before getting into AWS, I wanted to understand why Cloud Computing was so important.
Traditionally, if a company wanted to run an application, it needed physical servers, networking equipment, storage, data centers, and people to manage all of it.
Cloud changed the way we think about infrastructure.
Instead of thinking only about physical machines, we can think about infrastructure as something that can be created, configured, scaled, monitored, and managed through software.
That idea really interested me.
I started seeing Cloud as more than just "someone else's servers."
For me, Cloud represents the ability to build, experiment, automate, and learn without needing to own a complete physical infrastructure.
I can create a server, deploy an application, test something, monitor it, make a mistake, troubleshoot it, and try again.
That hands-on aspect is what attracted me the most.
Cloud Made Me Curious About What Happens Behind an Application
One thing I quickly realized is that learning Cloud is not just about learning Cloud services.
It connects many different areas of technology.
To understand how an application works in the Cloud, I need to understand things like:
- Linux
- Networking
- Servers
- Storage
- Security
- Containers
- Automation
- Monitoring
- Deployment
- Infrastructure
And this is where my interest in DevOps started becoming stronger.
I began to understand that DevOps is not simply about knowing a few tools.
It is about understanding how code moves from development to a reliable running application—and how we can make that process faster, safer, and more automated.
Cloud became the environment where I could start putting these concepts together.
So, Why AWS?
Once I decided to explore Cloud, I had another decision to make:
Which Cloud platform should I start with?
There are several major Cloud providers, and each has its own ecosystem.
I chose AWS as my starting point because I wanted to learn through practical experimentation.
AWS has a huge range of services covering compute, storage, networking, databases, security, monitoring, containers, serverless computing, and much more.
But for me, the important part wasn't the number of services.
It was the opportunity to understand the fundamentals behind them.
For example, when I started looking at services such as EC2, S3, VPC, IAM, and CloudWatch, I didn't just see service names.
I started connecting them with concepts:
EC2 → Compute
S3 → Storage
VPC → Networking
IAM → Identity and Access Management
CloudWatch → Monitoring
Suddenly, Cloud Computing started becoming easier to understand because I could connect theory with something I could actually experiment with.
AWS Became My Learning Playground
One of the things I like about learning AWS is the ability to experiment.
I can start with a simple idea and gradually make it more complex.
For example, I can begin with:
Launch a server → Connect to Linux → Deploy an application
Then I can ask:
How do I make this application accessible securely?
That leads me toward networking and security.
Then:
How can I package the application?
That leads me toward Docker and containers.
Then:
How can I automatically deploy changes?
That leads me toward CI/CD.
Then:
How do I know whether my application is healthy?
That leads me toward monitoring and observability.
And suddenly, one simple application has introduced me to a large part of the DevOps ecosystem.
That is what makes Cloud interesting to me.
One question leads to another.
The Connection Between AWS and DevOps
As I continued exploring, I started seeing AWS and DevOps as closely connected parts of the same learning journey.
DevOps focuses heavily on automation, collaboration, reliability, and continuous improvement.
Cloud provides an environment where many of these ideas can be implemented practically.
I can work with infrastructure, deploy applications, use containers, automate tasks, monitor systems, and troubleshoot real problems.
This is why I don't see AWS as my final destination.
AWS is my playground for learning DevOps.
I want to understand not just which command to run, but why I am running it and what is happening behind it.
It Hasn't Always Been Easy
Learning Cloud can feel overwhelming in the beginning.
There are hundreds of services, new terminology, networking concepts, security settings, Linux commands, configuration files, and tools to understand.
At first, even something that looks simple can raise many questions.
You launch an EC2 instance.
Then you see a security group.
Then you need to understand ports.
Then SSH.
Then keys.
Then Linux.
Then permissions.
And suddenly, launching a "simple server" doesn't feel so simple anymore.
But I think this is actually an important part of learning.
Getting confused is not the opposite of learning. Sometimes, it is the beginning of learning.
Every error gives me another question to investigate.
Every problem gives me an opportunity to understand something more deeply.
Instead of trying to avoid every mistake, I want to learn how to troubleshoot them.
From Learning Services to Understanding Systems
One thing I want to change in my approach is the way I learn.
I don't want to simply memorize:
"EC2 does this."
or
"S3 does that."
I want to understand how different components work together.
For example, imagine a simple application:
User → Internet → AWS Networking → Application → Container → Database
Now there are many questions:
- How does the request reach the application?
- How is the application secured?
- Where is the application running?
- How is the data stored?
- How do we deploy a new version?
- How do we monitor the application?
- What happens if something fails?
- How can we scale it?
These questions are much more interesting to me than simply memorizing service definitions.
They are also the questions that are pushing me deeper into DevOps.
Where AWS Fits Into My Journey
My goal isn't to learn AWS just for the sake of adding another technology to my resume.
I want to use AWS as a foundation for understanding modern infrastructure and DevOps practices.
My learning path is gradually moving through areas such as:
Linux → Networking → Cloud → Docker → CI/CD → Monitoring → Observability → DevOps
I know there is still a lot to learn.
And that's okay.
I'm not trying to complete the journey in a few weeks.
I'm trying to build a strong foundation one concept at a time.
What I Have Learned So Far
One of the biggest things I am realizing is that technology becomes much easier to understand when I stop treating it as a collection of tools.
Instead, I try to understand the problem first.
Why do we need containers?
Why do we need automation?
Why do we need monitoring?
Why do we need scalable infrastructure?
Why do we need proper access control?
Once I understand the problem, the technology starts making more sense.
That mindset is something I want to carry throughout my DevOps journey.
What's Next?
This article is not the conclusion of my Cloud journey.
It is the beginning.
There are still many AWS services I want to explore, many Linux and networking concepts I want to strengthen, and many DevOps tools and practices I want to understand.
I also want to document what I build, the mistakes I make, the problems I face, and the solutions I discover.
Because I believe learning becomes more meaningful when we share the process—not just the final result.
Final Thoughts
So, Why Cloud?
Because I wanted to understand what happens behind the applications we use every day and learn how modern infrastructure works.
And Why AWS?
Because AWS gave me a practical environment where I can experiment with those concepts and gradually connect them together.
I don't consider myself an expert in Cloud or DevOps.
I'm still learning.
But I've realized something important:
You don't need to know everything before starting. You just need enough curiosity to ask the next question.
For me, AWS is where those questions are starting to turn into hands-on learning.
And this is just the beginning of my DevOps journey.
Learning. Building. Automating. One step at a time.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article