🛡️ Day 2 of AWS — The Security Group Saga

A beginner’s honest story of misreading a task, making a mistake, and accidentally learning three things instead of one. 😅

Day 2 of my 50 Days of AWS journey on KodeKloud. 🚀 Yesterday it was key pairs. Today? Security Groups — and once again, I found a way to learn more than I was supposed to. 📝

🔐 What is a Security Group?

Before diving in, let’s understand what a Security Group actually is! 😊

A Security Group in AWS acts as a virtual firewall for your EC2 instances. 🔥 It controls what traffic is allowed in and out of your instance.

• Inbound Rules 📥 — Traffic coming into your instance (e.g. someone accessing your website)
• Outbound Rules 📤 — Traffic going out of your instance (e.g. your instance calling an external API)

A few important things to know: 🧐

• Security Groups are stateful — if you allow inbound traffic, the response is automatically allowed out, and vice versa
• By default, all inbound traffic is blocked and all outbound traffic is allowed
• You can attach one or more Security Groups to an EC2 instance

Think of it like a bouncer at a club 🎭 — decides who gets in, who gets out, and who gets turned away at the door.

📋 The Task

The assignment was simple: Create a Security Group with 2 inbound rules — one for HTTP and one for SSH. 🎯

HTTP — for web traffic on port 80. 🌐 SSH — for remote access on port 22. 💻

Simple enough, right? 😄 Well…

🌀 What I Actually Did

I read the task. Or at least I thought I did. 👀

My brain processed it as: “Two rules — one inbound, one outbound.” 🤦

So that’s exactly what I created:

• Inbound — SSH on port 22 ✅
• Outbound — HTTP on port 80 ❌ (wrong!)

I submitted it feeling pretty good about myself. 😎

Task Failed. ❌

That’s when I re-read the task.

Both rules were supposed to be inbound. 😭😂

I sat there for a second thinking — “This is Day 2 and I’m already failing tasks.” 😤

🛠️ The Silver Lining — Editing the Security Group

Here’s where it got interesting. 💡

To fix my mistake, I had to edit the Security Group — remove the wrong outbound rule and add the correct inbound HTTP rule.

And just like that, without planning to, I learned:

• How to edit inbound and outbound rules on an existing Security Group ✅
• The difference between inbound and outbound rules in practice — not just in theory ✅

The mistake forced me into the edit workflow. I would have skipped it entirely if I’d done it right the first time. 🤷😄

🗑️ And Then I Deleted It Too

Once I had the correct Security Group — HTTP inbound + SSH inbound — I thought, why not practice deleting it too? 🧐

So I did.

EC2 → Security Groups → Select → Actions → Delete

Gone. ✅

Three operations in one session: Create, Edit, Delete. Not bad for a task that was supposed to be just one. 💪

🧠 What I Actually Learned Today

1. Inbound vs Outbound — know the difference. 📥📤 Inbound = traffic coming into your instance. Outbound = traffic going out. Read the task carefully before creating rules. 😅

2. Security Groups are stateful. 🔄 You don’t need a separate outbound rule to allow responses to inbound traffic. AWS handles that automatically. This is different from Network ACLs which are stateless — but that’s a story for another day!

3. Editing rules is straightforward. 🛠️ You can add, modify, or remove rules from an existing Security Group at any time without recreating it. Changes take effect immediately.

4. HTTP = Port 80, SSH = Port 22. 🔢 These are the two most common ports you’ll deal with in EC2. Burn them into memory.

🎯 The Takeaway

I misread the task. Made the wrong configuration. Had to go back and fix it.

But here’s the thing — Focus on the outcome, not the obstacle. ✨

The obstacle was the mistake. The outcome? I didn’t just learn how to create a Security Group — I learned how to create, edit, and delete one. A single mistake turned one skill into three. 💪

If you’re learning AWS and things don’t go as planned — don’t stress. The detours are often where the real learning happens. 🌍

Day 2 of my 50 Days of AWS journey on KodeKloud. One mistake, three lessons, zero regrets. Follow along if you’re on a similar path! 🙌🔥