AWS Builder Center

Starting My Cloud Engineering Journey: Lessons From the First Few Weeks

A beginner's honest reflection on starting Cloud Engineering — from rushing through Linux commands to slowing down and actually understanding permissions, SSH, and file systems through hands-on practice and real errors. Currently working through AWS Cloud Practitioner Essentials, pairing theory with hands-on EC2, S3, and IAM practice in my own AWS account. Goal: real understanding, not just a certificate.

I'm a Software Engineering student at FAST-NUCES, Pakistan, and a few weeks ago I started a self-paced Cloud Engineering learning path — beginning with Linux fundamentals and an AWS account.
Like most beginners, I moved fast at first. I set up my AWS account, learned basic Linux commands, and even posted about it on LinkedIn. But looking back, I realized I had memorized commands without really understanding what they did or why they mattered.
So I paused and went back to basics — this time hands-on. I opened a real terminal and deliberately practiced navigating folders, creating and moving files, and setting permissions with chmod. I made plenty of mistakes along the way: running "cd" into a file instead of a folder, trying to create files in restricted system directories, and misreading error messages like "Not a directory" or "Permission denied." Each error actually taught me more than any tutorial did, because I had to stop and figure out exactly what went wrong.
Along the way, I also locked myself out of my own AWS account after losing access to my MFA device — a stressful but valuable lesson in why backup codes and IAM best practices matter from day one.
Now I'm working through AWS Cloud Practitioner Essentials on Skill Builder, pairing each concept with hands-on practice in my own AWS account — launching EC2 instances, exploring S3, and getting comfortable with IAM.
My goal isn't just to pass a certification exam. I want to genuinely understand how cloud infrastructure works, build real projects (starting with deploying my own website on S3), and eventually use these skills for freelance work and, longer term, a career in cloud engineering.
If you're a beginner in the same boat — slow down and get your hands dirty with the basics. It's less impressive to post about, but it's what actually sticks.
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