1
Update
This may be to do with my account potentially being in an 'isolated' state as per this post: https://forums.aws.amazon.com/thread.jspa?start=0&threadID=239202&tstart=0
I'm going to contact AWS and ask them if this is the issue.
Original Post
I'm fairly new to AWS but getting a recurring problem with connecting to EC2 via SSH. In short, I seem to be only able to connect once via SSH to my instance - all future attempts time out. The only fix is to stop it and start it each time.
Here is as much detail as I can provide - really hoping you guys can help me out here!
Video of timeout:
EC2 is a T2 Micro:
My EC2 is in a custom VPC -My Security Group has Port 22 open to the world and outbound it can access everything:
I'm using a public subnet in my VPC
My Network Access Control List (NACL) is default:
Route table has a route out to my Internet Gateway (which works fine):
When I connect first time it's fine:
After a few mins, I can't connect again:
(see video at top of post)
Notes: - Not that it matters but when I do successfully SSH in, I can curl webpages and get a response - I'm tethering from my phone but doesn't seem to be affecting things (I think this didn't work at home either) - If I just wait a minute or two after first SSH'ing in and exiting, when I try to reconnect after a couple of mins it will just time out
Thanks in advance.
if you have some application running and if it's a t2/t3 series instance, your instance is mostly likely running out of CPU credits leaving no processing power to establish the connection. Please [edit] your post and add details of what type of instance, what processes are running and cloudwatch graphs as well – Sathyajith Bhat – 2019-06-23T16:49:26.633
Thanks a lot @SathyajithBhat - I've updated the post accordingly – Rajtastic – 2019-06-30T11:55:09.090