Starting university in computer science, I quickly realized that learning to code is only one part of becoming a good engineer.
Today, applications rely on much more than code: computing resources, networking, storage, databases, security, monitoring, and increasingly artificial intelligence.
This is what made me interested in cloud computing and AWS.
Why I decided to learn AWS
As an engineering student specializing in systems and networks, I wanted to better understand what happens behind the applications we use every day.
How does an application handle thousands of users?
How is data stored securely?
How do different services communicate?
How can a system remain available when something goes wrong?
Cloud computing provides a practical way to explore these questions.
Instead of thinking only about writing a program, I started thinking about the entire system surrounding it.
Learning by building
One thing I have learned is that watching courses is not enough.
The real understanding starts when you try to build something yourself.
A simple project can already introduce important concepts:
User → Application → API → Database → Cloud Infrastructure
Each component raises new questions about architecture, networking, authentication, scalability, security and cost.
This is why I want to progressively move from basic AWS concepts toward hands-on projects.
AWS and cybersecurity
Another area I am particularly interested in is cybersecurity.
Modern security is increasingly connected to cloud infrastructure. Understanding how networks, identities, permissions and resources are managed in the cloud is becoming an important skill for future engineers.
For me, learning AWS is therefore not only about becoming a cloud engineer.
It is also a way to build a stronger foundation for cloud security and DevSecOps.
My learning roadmap
I am following a simple approach:
Learn → Practice → Build → Share → Improve
My next steps are:
- Strengthen my AWS fundamentals.
- Practice with hands-on environments.
- Build small cloud projects.
- Explore AWS security concepts.
- Document what I learn.
- Progress toward an AWS certification.
I believe that documenting the journey is almost as important as completing the courses.
Writing about a problem forces you to understand it clearly.
Why the AWS Builder community matters
One of the things I find interesting about AWS Builder Center is the community aspect.
Learning alone can sometimes feel like a collection of disconnected courses.
Reading how other students approach cloud, cybersecurity, AI or software engineering gives a different perspective.
It also creates an opportunity to share mistakes, solutions and project ideas.
As a student, I think this is particularly valuable because you don't need to already be an expert to contribute.
You can simply share what you learned today.
My goal
I don't want to collect certificates just for the sake of collecting certificates.
I want to be able to look back at the end of my studies and see a portfolio of real things I built and understood.
AWS is one of the technologies I want to explore along that journey.
For me, the objective is simple:
Don't just learn the cloud. Build something with it.
And this is only the beginning. 🚀☁️
#AWS #CloudComputing #AWSBuilderCenter #Students #Cybersecurity #DevOps #Learning
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article