DEV Community: Pawan Joshi

EC2 SSH Not Connecting? Here Are the 5 Things That Were Wrong (And How I Fixed Them)

Pawan Joshi — Sat, 23 May 2026 16:10:47 +0000

I spent 3 hours staring at this error my first week with AWS:

"Permission denied (publickey)"

My EC2 instance was running. My terminal was open. I'd followed a tutorial step by step. And still — nothing.

Here are the 5 things that were wrong (and how I fixed each one):

Wrong .pem file

I had downloaded the key pair but was pointing to the wrong file path in my command. Sounds obvious. When you're new, it's not.

Fix: always use the full absolute path.
ssh -i ~/Downloads/my-key.pem ec2-user@

Wrong username

Different AMIs use different default usernames. I kept typing "ubuntu" on an Amazon Linux instance.

Amazon Linux → ec2-user
Ubuntu → ubuntu
RHEL → ec2-user or root
Debian → admin

This one catches almost everyone.

.pem file permissions too open

SSH refuses to use a key file that other users can read.

Fix: chmod 400 my-key.pem

Run that once and you'll never see "WARNING: UNPROTECTED PRIVATE KEY FILE!" again.

Security group blocking port 22

I'd launched the instance but never added an inbound rule for SSH. The connection wasn't being refused — it was being silently dropped at the firewall level.

Fix: go to EC2 → Security Groups → Inbound Rules → add SSH (port 22) from your IP. Not 0.0.0.0/0 — just your IP. Keep it tight.

Using the wrong IP

I was copying the Private IP from the console instead of the Public IPv4 address. Private IPs only work if you're inside the same VPC.

Fix: use the Public IPv4 DNS or Public IP shown in the instance details.

The honest truth: none of these errors showed up in the tutorial I was following. Tutorials show the happy path. Real learning happens when something breaks and you have to figure out why.

If you've hit any of these — you're not alone. Every person working in cloud has been here.

Which one got you the longest? Drop it in the comments.

Why Building Small Projects Matters More Than Certifications (At First)

Pawan Joshi — Tue, 13 Jan 2026 17:03:35 +0000

When students start learning cloud computing, the first goal is often a certification.
While certifications are valuable, they shouldn’t be the starting point.

In my experience, real understanding comes from building small, imperfect projects.

Launching a simple EC2 instance, hosting a static website on S3, or setting up IAM permissions may look basic—but these tasks teach fundamentals that no exam guide can. You learn why services exist, how they interact, and what breaks when configurations are wrong.

Small projects also build confidence. Instead of memorizing concepts, you start recognizing patterns. Debugging errors becomes part of learning, not something to fear.

Certifications make more sense after you’ve built things. At that point, exam topics feel familiar instead of abstract, and preparation becomes faster and deeper.

My advice to students learning AWS:

Build first
Break things safely
Understand basics deeply
Certify later

Cloud skills grow through practice, not pressure. Every small project is a step toward real-world readiness.

Learning AWS as a Student: What Actually Works

Pawan Joshi — Sun, 11 Jan 2026 17:04:58 +0000

When I started learning AWS, I quickly realized one thing: watching tutorials is not enough.
Cloud computing makes sense only when you build.

As a student, it’s easy to feel overwhelmed by the number of AWS services. My biggest learning came when I stopped trying to “learn everything” and instead focused on doing small, practical tasks.

I began with the basics:

Understanding what cloud really solves
Using core services like EC2, S3, and IAM
Deploying simple projects instead of complex architectures

Hands-on practice changed everything. Even a small experiment—like hosting a static website or setting up basic permissions—taught me more than hours of passive learning.

Another key lesson was learning with others. Discussing problems, explaining concepts, and working in a community helped me gain clarity and confidence. Cloud is not just about services; it’s about collaboration and real-world problem solving.

My advice to students starting AWS:

Start small
Build consistently
Don’t rush certifications
Learn by doing, not just watching

Cloud learning is a journey. Progress may feel slow at first, but every small build compounds into real understanding.

How Students Can Learn AWS Without Spending Any Money (Real Roadmap)

Pawan Joshi — Thu, 01 Jan 2026 05:29:02 +0000

The Ultimate Zero-Cost AWS Roadmap for Students: Learn Cloud Without Spending a Cent 🚀

Learning AWS can feel overwhelming—especially for students.

There are hundreds of services, confusing pricing pages, and a constant fear of getting charged accidentally. Many students assume you must pay to learn AWS.

That’s not true.

I’m a student myself, and here’s a real, zero-cost roadmap to learn AWS properly—without spending a single rupee or dollar. No fluff. No paid courses. No hidden traps.

Step 1: Understand What AWS Actually Is (Before Touching the Console)

One of the biggest mistakes beginners make is jumping straight into EC2. Before creating anything, understand this: AWS is a collection of services, not one tool.

At a beginner level, you only need to understand the four pillars:

Compute: (EC2, Lambda)
Storage: (S3)
Networking: (VPC basics)
Identity & Security: (IAM)

📌 Free Resource: AWS Skill Builder (Free Tier)

AWS provides official learning paths designed specifically for beginners. You don’t need a credit card to start learning concepts.

Step 2: Use AWS Free Tier (But Carefully)

AWS Free Tier is your biggest ally—if used correctly. What many students don’t realize:

Free Tier is limited, not unlimited.
Misconfiguration = surprise bills.

Services you can safely learn for free:

EC2: (t2.micro / t3.micro) – limited hours per month.
S3: Small storage usage.
Lambda: Generous free requests (1 million per month).
CloudWatch: Basic monitoring.
IAM: Always free.

💡 Golden Rule: Always delete/terminate resources immediately after your practice session.

Step 3: Practice Without Risk Using Guided Labs

Instead of randomly clicking around the AWS Console, use guided labs. These platforms simulate real AWS environments without the risk of hitting your personal credit card.

Best free lab platforms:

AWS Workshops
AWS Builder Labs (Look for the "Free" filter)

Why use labs?

They provide auto-clean resources.
They don't require your own AWS account.
They teach real-world scenarios rather than abstract theory.

Step 4: Learn Through Projects (Not Tutorials)

Watching tutorials alone won’t teach you AWS. You need "muscle memory." Instead of a 10-hour course, try building these small projects:

Static Website: Host a simple HTML page using S3.
Serverless API: Create a "Hello World" API using Lambda and API Gateway.
EC2 Deployment: Deploy a simple Node.js or Python backend on a Linux instance.
Security First: Set up specific IAM roles for your services instead of using the Root account.

Pro-tip: Document what you build on GitHub or a blog. That’s how real learning happens.

Step 5: Follow a Certification Path (Without Paying)

Even if you don’t plan to take the exam immediately, certification paths are excellent learning roadmaps.

The Beginner Path:

AWS Cloud Practitioner (The "What" of Cloud)
AWS Solutions Architect Associate (The "How" of Cloud)

Free Prep Resources:

Official AWS Exam Guides.
AWS Cloud Quest (A gamified way to learn).
Community blogs and YouTube channels like FreeCodeCamp.

Step 6: Learn With a Community

Learning AWS alone is hard. Learning with others keeps you consistent and exposes you to use cases you might have never considered.

Where to join:

AWS Cloud Clubs: Student-led groups on campuses.
Developer Forums: DEV.to, Reddit (r/aws), and StackOverflow.
Open Source: Contribute to projects using AWS SDKs.

Step 7: Avoid These Common Beginner Mistakes ❌

Mistake #1: Creating resources without understanding pricing.
Mistake #2: Leaving EC2 instances running overnight.
Mistake #3: Copy-pasting CLI commands without understanding what they do.
Mistake #4: Trying to learn all 200+ AWS services at once.
Mistake #5: Thinking a certificate equals mastery. Projects = Mastery.

A Simple 30-Day Free AWS Learning Plan
Week 1:
Cloud basics + IAM + S3

Week 2:
EC2 + basic networking

Week 3:
Lambda + serverless concepts

Week 4:
Small project + documentation

That’s it. Simple. Free. Effective.

Final Thoughts
You don’t need money to learn AWS. You need discipline, clear direction, and hands-on practice. AWS is not hard—unstructured learning is.
If you’re a student starting your cloud journey, start small, stay consistent, and build responsibly.

💬 Question for you:
How are you currently learning AWS—and what’s your biggest challenge? Let’s discuss below! 👇