Certifications mattered to me because they got me out of theory and into the tools.

Before I had any AWS certifications, cloud felt abstract. I could read articles and watch videos, but I did not yet have instinct for where things lived in the console, how permissions failed, or what logs looked like when something broke. Studying for certifications gave me a reason to sit down and work through that gap instead of staying in the shallow end.

What the certifications actually did

During my AWS Cloud Support internship, I finished two certifications in a twelve-week window: AWS Certified AI Practitioner and AWS Certified Solutions Architect Associate. Both were done by week seven.

That did not make me an expert. It did mean I was spending every day inside AWS. I was exposed to EC2, S3, RDS, IAM, Lambda, DynamoDB, CloudWatch, networking, permissions, logs, and runbooks. The exams were layered on top of the work I was already doing.

Outside work hours, I used Stephen Maarek’s Udemy courses to structure prep. I ran practice exams, looked up explanations for missed questions, and found YouTube breakdowns when I needed a different voice. The question pools change, so I made sure I was looking at updated material. The loop was simple: test, find gaps, review, test again.

I will be direct: I memorized the practice exams. I ran the test banks until I was scoring consistently in the 90–100% range. By the time I sat the real exams, the format felt familiar.

The certifications came from daily AWS exposure during the internship, structured prep at night, repetition, and filling gaps as I found them. That is it.

Career progression checkpoint illustration for this section.

What the process gave me

The exam was just the checkpoint. The real value was spending weeks moving between AWS consoles, docs, guided labs, Udemy quizzes, YouTube explanations, and my own notes.

I was not just looking at architecture diagrams. I was wiring services together in lab environments, watching them fail, fixing them, and reinforcing the same concepts through practice questions. That cycle built familiarity and confidence inside AWS.

It also changed how I approach problems in general. When something does not work, I go to logs, permissions, configurations, and data flow instead of guessing. That habit came from living inside AWS daily and reinforcing it through exam prep.

What certifications did not do

They did not make me a senior engineer. They did not give me production ownership experience. They did not replace real project work. They did not teach deep algorithms or low-level systems design.

What they did give me was comfort navigating AWS. I can open a new AWS account, find services without hunting through menus, understand where permissions live, and trace basic failures. That is the real outcome I walked away with.

Professional growth checkpoint illustration for this section.

Closing

I do not treat certifications as status symbols. For me, they were a structured way to get comfortable inside real cloud systems.

The badges are proof I went through the process. The real value was the experience I gained along the way.