week 5:CloudFormation vs ClickOps: Why the Struggle Was Worth It

If you’re about to start Week 5, or you’re currently staring at a CloudFormation error wondering whether you’re making any progress, this post is for you.

One of the most interesting parts of Week 5 is that you build the same infrastructure twice.

First, you deploy it manually through the AWS Management Console. You create the VPC, subnets, route tables, Internet Gateway, Security Groups, and EC2 instances yourself. This ClickOps approach helps you understand what each service does and how everything fits together.

Then comes CloudFormation.

At first, I thought I was simply rebuilding what I had already created.

I quickly learned that I was doing something very different.

With ClickOps, AWS guides you through the process. You can visually see your resources being created, and it feels intuitive.

With CloudFormation, every resource must be described in code. Every dependency, every reference, and every relationship between resources has to be defined correctly.

A missing space matters.

A typo matters.

A wrong reference matters.

And CloudFormation will let you know immediately.

At times, it felt like I spent more time troubleshooting than building.

I encountered YAML syntax errors, incorrect references, file naming issues, stack deployment failures, and connectivity problems. Some days it felt like every time I solved one problem, another appeared.

But the biggest surprise was that many of the issues I faced were not actually CloudFormation problems.

I spent hours investigating what I thought were broken templates only to discover that the real issue was somewhere else.

I checked the wrong VPC.

I looked at the wrong Security Group.

I connected to the wrong EC2 instance.

I used the wrong filename because of a capitalization mistake.

I even spent time troubleshooting connectivity between EC2 instances, convinced my CloudFormation template was wrong. After digging deeper, I discovered the infrastructure had deployed successfully. The actual issue was related to a Security Group configuration that wasn’t allowing the traffic I was trying to test.

That experience changed how I think about cloud engineering.

I realized that the hardest part wasn’t writing YAML.

It wasn’t memorizing commands.

It wasn’t deploying infrastructure.

It was troubleshooting.

The AWS Console taught me what the services do.

CloudFormation taught me how those services work together.

ClickOps showed me the destination.

CloudFormation showed me the blueprint.

More importantly, CloudFormation forced me to slow down, think critically, verify assumptions, and understand the relationships between networking, security, and infrastructure.

Looking back, the errors that frustrated me the most ended up teaching me the most.

The successful deployment was satisfying, but the lessons hidden inside the failures were far more valuable.

Advice to Future Week 5 Students

If you’re struggling right now, don’t panic.

You’re probably learning more than you realize.

A few things I wish someone had told me before I started:

• Be patient with CloudFormation.
• Read error messages carefully.
• Double-check the resources you’re troubleshooting.
• Verify you’re in the correct AWS region.
• Make sure you’re looking at the correct VPC and Security Group.
• Don’t assume every issue is caused by your template.
• Focus on understanding why something works, not just getting it to work.

Most importantly, don’t compare your progress to anyone else’s.

Everyone sees the successful deployment screenshot.

Nobody sees the hours spent chasing a missing space, a wrong reference, or a networking issue hidden behind what looked like a CloudFormation error.

Before Week 5, I thought cloud engineering was mainly about building infrastructure.

After Week 5, I realized it’s equally about troubleshooting infrastructure.

ClickOps gave me the foundation.

CloudFormation helped me think like an engineer.

And while I may forget some YAML syntax in the future, I’ll never forget the lessons I learned while figuring out why things weren’t working.

Because sometimes the most valuable part of the journey isn’t the deployment that succeeds.

It’s the mistakes that teach you how to find your way there. 🚀