惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

GbyAI
GbyAI
The GitHub Blog
The GitHub Blog
小众软件
小众软件
美团技术团队
博客园 - 司徒正美
G
Google Developers Blog
Blog — PlanetScale
Blog — PlanetScale
Hugging Face - Blog
Hugging Face - Blog
博客园_首页
大猫的无限游戏
大猫的无限游戏
罗磊的独立博客
Recent Announcements
Recent Announcements
酷 壳 – CoolShell
酷 壳 – CoolShell
D
Docker
J
Java Code Geeks
Last Week in AI
Last Week in AI
V
Visual Studio Blog
Microsoft Azure Blog
Microsoft Azure Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
P
Proofpoint News Feed
V
V2EX
C
Check Point Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
MyScale Blog
MyScale Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
EC2 not responding? The issue might be here (and it seems...
Angelo Alber · 2026-05-01 · via DEV Community

In day-to-day cloud operations, some incidents stand out not because of their complexity, but quite the opposite.

They are those cases where, once you discover the root cause, you think:
“this can’t be it”.

This is one of them.

The scenario

The EC2 instance was running, with a public IP and everything seemingly correct.

  • Status: running
  • Public IP available
  • No visible alerts

Even so, every attempt to access it resulted in a timeout.

No clear error. No direct clue.

Where to look first

In situations like this, before assuming something more complex, the first step is always to review the Security Group.

More specifically: the inbound rules.

The problem

When analyzing the Security Group, the situation was straightforward:

No inbound rules configured.

This means the instance was not accepting any external connections.
No SSH, no HTTP, no any other port.

This is expected behavior in AWS:
everything is denied by default unless explicitly allowed.

Why this happens

This type of situation is more common than it seems.

Some examples:

  • Creating an instance without reviewing the Security Group
  • Using a default Security Group with no rules
  • Changes made during testing that were not reverted
  • Switching Security Groups without proper validation

In the middle of daily operations, this kind of detail is easy to overlook.

How to fix

The fix is simple: add the required rule to the Security Group.

Example for SSH access:

  • Type: SSH
  • Port: 22
  • Source: your IP (recommended) or 0.0.0.0/0 for testing

After the fix

Once the rule was added, access to the instance was restored immediately.

No restart required. No additional changes needed.

Practical takeaway

Before assuming complex issues, always check the basics.

In many cases, what looks like a serious incident is just a simple configuration that went unnoticed.

And precisely because it looks simple, it happens more often than expected.

Quick checklist for unreachable EC2

  1. Security Group
  2. Network ACL
  3. Route Table
  4. Instance status

In most cases, the issue is in the first item.

Further reading

If you want to dive deeper, the official documentation explains how Security Groups work and how rules are evaluated:

Note

This content is based on real-world scenarios from day-to-day operations.
AI tools were used only for text review.