AWS not letting me ssh into instance and cannot connect to my website due to timeout error

Question

1 hour ago I could connect to my website, stringapi.net, but now, it is taking too long to respond and I also cannot ssh into my instance as that is also not loading (I assume also timeout error). Does anybody have any suggestions? I just setup certbot a few days ago, could it be a problem with this?

I have checked and ec2 does not appear to be down.

Either the instance is legitimately down - Out-Of-Memory is a common cause on small instances like t3.nano - or the security group no longer allows access, or you have the Ip wrong — erik258, Aug 06 '21 at 17:08
First check the security group and that the public IP didn't change (which it will any time the instance is stopped). If those look right, I'd just reboot the instance. AWS can't introspect memory usage directly. — erik258, Aug 06 '21 at 17:11
I am building a rest api. Would it be a good idea to use auto scaling if I do not know how many people will use the service? — CuriousCoder, Aug 06 '21 at 18:12
The security group and public ip are the same. I rebooted the instance and the site is still down. Should I try to setup autoscaling? — CuriousCoder, Aug 07 '21 at 01:20
I rebooted it and it is now up, how do I make sure this doesent happen again? — CuriousCoder, Aug 07 '21 at 01:22

score 0 · Accepted Answer · answered Aug 07 '21 at 01:29

0

Rebooting the instance worked!

answered Aug 07 '21 at 01:29

CuriousCoder

13
4

AWS not letting me ssh into instance and cannot connect to my website due to timeout error

1 Answers1