Can't Connect To AWS EC2 Instance via Putty

Question

I've got an EC2 instance running on AWS:

1. It's an Ubuntu linux instance, and up until not long ago I used putty to access it on a regular basis - worked great.
2. I'm using Pageant to load the .ppk file (converted it from AWS's original .pem file as per the AWS docs).
3. I'm using these login settings:
4. Checked that my securtiy group for the instance allows SSH access on port 22 from my address - it does indeed.
5. Checked that my elastic IP did not change - it did not.
6. Tried to login into the Public DNS instead of the IP - no cigar.
7. Rebooted the instance and waited 15 minutes while making tea.

Having said that, I'm getting a "network error: connection timed out" error.

What can cause this?

Solution

So, It was a secuity group issue at the end.

AWS makes you include every IP you want to SSH into your server from in a special "group" of permissions to access the server. Otherwise it blocks you from enetering it. Super-good for protection on production servers, bad when accessing your dev server from cafes in the middle of nowhere.

Some more about Security Groups in the AWS Docs (Only for VPC - that's what I use)

Comments

[HopelessN00b]

Firewall get turned on? SSH server not running? Lots of things can cause this.

[itsalive]

I'd Imagine. But what specifically? Throw me some bones here, I'm kinda dumbfounded.

[Forest1206]

Did you check the System Log in the AWS console? From the EC2 Instances screen, click the Action button and then "Instance Settings", "Get System Log". Look for any error there.

[Forest1206]

Do you see anything related to OpenSSH? You should at least see a line like this:Starting OpenSSH server [ OK ]

[itsalive]

There's on like that. A couple actually - I rebooted twice since I started the instance.

[Forest1206]

What happened between the time it was working and the time it stopped working? Did you make any config change? Installed any update?

[Amol Chakane]

I am facing same issue. There is nothing about SSh in AWS system logs Have you resolved it? How?