# Heal your brain from negativity & doomscroll, read this AWS stuff - I was stuck today. — retained record

> Retained reddit record from reddit:aws.

Canonical: https://highsignal.app/data/records/c2d2b1689e1415f7

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:aws)  published 2026-09-03 18:27 ingested 2026-09-04 02:42

[original source ↗](https://www.reddit.com/r/aws/comments/1w6foiz/heal_your_brain_from_negativity_doomscroll_read/)

## retained text



```
AWS EC2 SSH Timeout — Solved with VPC Flow Logs

I was troubleshooting an EC2 SSH timeout. VPC, subnet, route table, IGW, NACL, and EC2 health checks all looked correct.

My Security Group allowed SSH from my public IP:

198.51.100.10/32 → TCP 22

But SSH still failed.

As a test, I temporarily changed it to:

0.0.0.0/0 → TCP 22

SSH immediately worked.

I enabled VPC Flow Logs and discovered the interesting part:

Expected IP: 198.51.100.10

AWS actually saw:
198.51.100.20 → 10.10.0.69:22 → ACCEPT

So my network was using a different egress/NAT IP for the TCP connection than the IP reported by ifconfig.me.

Key takeaway

Don't always assume the IP shown by ifconfig.me is the IP AWS will see.

VPC Flow Logs can show the actual source IP reaching your EC2 ENI, which makes them extremely useful for debugging Security Group and connectivity issues.
```



document fetched 2026-09-04 00:45 · canonical https://reddit.com/r/aws/comments/1w6foiz/heal_your_brain_from_negativity_doomscroll_read
