Most beginners learning AWS make the same dangerous mistake.

They launch an EC2 instance… Open all ports… And unknowingly expose their server to the entire internet.

I almost did the same.

But while learning EC2 and Security Groups, I realized something powerful:

In AWS, security is YOUR responsibility.

This post will walk you through:

• What EC2 really is (without confusing jargon)

• How Security Groups actually protect you

• A real-world mini project (deploying a live website)

• Clean diagrams you can visualize instantly

This diagram summarizes everything we’ll build in this post.

☁️ What EC2 REALLY Is (No Buzzwords)

Forget definitions.

Think of EC2 like this:

👉 You are renting a computer in another country.

👉 You can turn it on/off anytime.

👉 You control everything inside it.

That’s it.

---

⚠️ The Mistake That Can Cost You

When I first launched an EC2 instance, I saw this option:

Allow: 0.0.0.0/0

It looked harmless.

But it actually means:

"Allow ANYONE on the internet to access this port"

That’s when Security Groups became real to me.

---

Security Groups = Your Cloud Firewall

Security Groups decide:

• Who can enter your server

• Which doors (ports) are open

Simple Mental Model

Internet → Security Group → EC2 Server

If the Security Group blocks it — it NEVER reaches your server.

---

The Only Ports You Should Care About (As a Beginner)

Port	Purpose
22	SSH (connect to server). Linux
21	FTP (File Transfer Protocol)
80	HTTP (website)
443	HTTPS (secure website)
3389	RDP (Remote Desktop Protocol) . Connecting to Windows EC2 instances

---

REAL PROJECT: Deploy a Live Website on EC2

This is where most tutorials stop being useful.

Let’s actually build something.

---

🪜 Step 1: Launch EC2 Instance

• Choose: Amazon Linux

• Instance type: t3.micro (It can be t2.micro for you, depending on your region)

• Create key pair ( and download the '.pem' file for later use)

---

🔐 Step 2: Configure Security Group (CRITICAL)

Add ONLY these rules:

SSH Access

Port: 22
Source: Your IP only

HTTP Web Access

Port: 80
Source: 0.0.0.0/0

---

⚙️ Step 3: Auto-Install Web Server (User Data)

Paste this during launch: This is a one time script that runs at launch of the instance.

#!/bin/bash
yum update -y
yum install -y httpd
systemctl start httpd
systemctl enable httpd
echo "<h1>Deployed from AWS EC2 🚀</h1>" > /var/www/html/index.html

---

🌍 Step 4: Access Your Website

Copy your EC2 public IP → paste in browser

Boom.

You now have a LIVE website.

---

🧠 What Just Happened (Architecture)

User Browser
     ↓
Internet
     ↓
Security Group (checks rules)
     ↓
EC2 Instance (Apache running)
     ↓
Returns your webpage

---

Production Insight (This Is What Makes You Stand Out)

Beginners do this:

• Open all ports

• Use access keys inside servers

• Ignore cost tracking

Professionals do this:

• Restrict SSH to specific IP

• Use IAM Roles (NOT access keys)

• Set AWS Budgets alerts

---

🔑 IAM Roles vs Access Keys (Real Talk)

If you remember ONE thing from this post:

Never store AWS access keys inside your EC2 server.

Use IAM Roles instead.

Why?

• Temporary credentials

• Automatically rotated

• Much safer

---

Don’t Skip This (Budget Setup)

Before doing anything serious in AWS:

Set a budget alert.

Because cloud bills don’t warn you — they surprise you.

---

🎯 Final Takeaway

Learning AWS isn’t about memorizing services.

It’s about understanding:

• How systems connect

• Where security boundaries exist

• How real applications are deployed

---

🚀 What I’m Learning Next

• Load Balancers

• Auto Scaling

• VPC Networking

---

💬 If You’re Starting Cloud/DevOps

Don’t just watch tutorials.

Build things. Break things. Fix things.

That’s how this finally starts making sense.

---

Final Note

If this helped you even a little, you’re already ahead of most beginners.

I’ll keep sharing as I go deeper into AWS.

Let’s build in public ☁️🔥