Ssh – Network timeout errors with Amazon EC2 instance after first 10 minutes

amazon ec2amazon-web-servicesputtysshubuntu-14.04

I create a new instance. Happens for both Amazon Linux or Ubuntu instances. I didn't try a windows instance.

Sometimes, I can log in once via ssh(putty). I do some cd .. and ls commands but that's it. I then get 'Software caused connection to Abort' from Putty. Future attempts at connection to the instance result in a "Connection timeout error".

I tried connecting with my Windows 10 Desktop, iMac and my Win10 Laptop (same router). My security group allows ssh (I tried allowing everything). Reboot the instance doesn't help.

I don't know how access Aws instances without ssh. Thanks.

EDIT:

I found some threads from 2011 with a similar issue

https://forums.aws.amazon.com/message.jspa?messageID=251001#251001

https://forums.aws.amazon.com/message.jspa?messageID=246274

EDIT 2:
Issue solved

Long story short: My account a long time ago was suspended (and unknowingly put into "isolation"). Then I got my account reactivated. Account Support said it was a technical issue. I paid for Tech Support for 2 months, Tech Support realized this was an account issue. I received a refund and $100 in AWS credits.

Best Answer

Solution: Ask customer support if your account is put into isolation and have them remove it. This behavior will most likely only happen if your account was suspended and it wasn't removed when it was re-activated. Account Isolation can at the region level.

Related Solutions

Python CGI on Amazon AWS EC2 micro-instance — a how-to!

(Strange post, so hopefully this won't be as strange a reply).

On the subject of security flaws: it is considered general bad practice to store cgi-bin scripts within the document root of the web server. Even the W3C eludes to it under "Are compiled languages such as C safer ..." in their World Wide Web Security FAQ:

Consider the following scenario. For convenience's sake, you've decided to identify CGI scripts to the server using the .cgi extension. Later on, you need to make a small change to an interpreted CGI script. You open it up with the Emacs text editor and modify the script. Unfortunately the edit leaves a backup copy of the script source code lying around in the document tree. Although the remote user can't obtain the source code by fetching the script itself, he can now obtain the backup copy by blindly requesting the URL:
    http://your-site/a/path/your_script.cgi~
(This is another good reason to limit CGI scripts to cgi-bin and to make sure that cgi-bin is separate from the document root.)

This is not as significant a threat as the ability to write a file within the document root. However, an attacker could obtain the source code of the cgi, devise a directed attack against it, and use it as a stepping stone into the server.

To mitigate this, you can add the following lines to the lighttpd.conf (or some variation therein) to direct cgi-bin to a directory separate from the /var/www/lighttpd document root.

$HTTP["url"] =~ "/cgi-bin/" { cgi.assign = ( "" => "" ) }
alias.url = ( "/cgi-bin/" => "/usr/lib/cgi-bin/" )

This requires both the cgi and alias modules for lighttpd.

Ssh – Does AWS not allow outbound SSH connections

Nope, AWS doesn't inherently block outbound SSH. Something else is going on.

Related Topic