🚀 Day 5 of Learning DevOps + Cloud ☁️

📅 Today's Journey

Today started with excitement — and a few hiccups.
The plan:

1. Launch an EC2 Instance → Named it "my-first-instance".

2. Connect via Git Bash using SSH.

3. Practice essential Linux commands inside AWS EC2.

---

🖥 Step 1: Launching EC2 Instance

Using AWS Management Console:

• Selected Amazon Linux 2 AMI

• Chose t2.micro instance (free-tier)

• Created a new key pair for SSH access

• Security group allowed port 22 (SSH)

• Named the instance "my-first-instance"

Reference: AWS EC2 Documentation

---

🔑 Step 2: Connecting via SSH (Git Bash)

Command I used:

ssh -i my-key.pem ec2-user@<public-ip>

⚠️ Faced errors like:

• Permission denied (publickey) → Fixed by setting correct permissions:

    chmod 400 my-key.pem
  

• Host key verification failed → Solved by removing old known hosts entry:

    ssh-keygen -R <public-ip>
  

After ~15 minutes of trial and error… Connected successfully! 🎉

Reference: Connect to EC2 via SSH

---

📂 Step 3: Practicing Linux Commands

Once inside EC2, I explored basic commands:

Reference: Linux Commands Cheat Sheet

---

📌 Key Learnings Today

• SSH errors are common, but solvable with patience.

• File permissions (chmod) are crucial for SSH security.

• Knowing a few Linux commands already makes working inside EC2 easier.

• Cloud computing is not just clicking buttons — the command line is powerful.

---

🔗 Additional Resources

• AWS EC2 User Guide

• Linux Essentials for Cloud Engineers

---

💡 Tip: Always keep your .pem file safe and never share it publicly — it’s your private key to access your instance.

---

#100DaysOfCloud #AWS #DevOps #Linux #LearningInPublic