EC2 not responding? The issue might be here (and it seems too basic to happen)
Source: Dev.to
The EC2 instance was running, with a public IP and everything seemingly correct.
- Status: running
- Public IP: available
- Alerts: none
Even so, every attempt to access it resulted in a timeout. No clear error, no direct clue.
The scenario
In day‑to‑day cloud operations, some incidents stand out not because of their complexity, but because the root cause is surprisingly simple.
Where to look first
Before assuming something more complex, start by reviewing the Security Group, specifically the inbound rules.
The problem
The Security Group had no inbound rules configured, meaning the instance was not accepting any external connections (no SSH, HTTP, or any other port). AWS denies all traffic by default unless explicitly allowed.
Why this happens
This situation is more common than it seems. Typical causes include:
- 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 detail is easy to overlook.
How to fix
Add the required inbound rule to the Security Group.
Example for SSH access
- Type: SSH
- Port: 22
- Source: your IP (recommended) or
0.0.0.0/0for testing
After the fix
Once the rule was added, access to the instance was restored immediately. No restart or additional changes were needed.
Practical takeaway
Before assuming complex issues, always check the basics. What looks like a serious incident is often a simple configuration that went unnoticed.
Quick checklist for unreachable EC2
- Security Group
- Network ACL
- Route Table
- Instance status
In most cases, the issue is the first item.
Further reading
The official AWS 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.