- Newest
- Most votes
- Most comments
Hello.
What is the CPU usage rate and memory usage rate?
When t2.micro's CPU burst credits are used up, the performance drops to the baseline throughput, which may make SSH unusable.
By the way, t2.micro starts consuming burst credits when the CPU usage exceeds 10%.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-credits-baseline-concepts.html
Like 6% CPU - not sure where to see memory, not on the monitoring tab in EC2 instance dashboard
Also, just spun up another fresh t2.micro instance and installed WordPress....same issue, still serves HTTPS but no longer SSH.
sshd within the EC2 instance may have stopped due to some problem.
Connect to EC2 using Systems Manager Session Manager and check if there are any problems with sshd and check the system logs to see if any errors have occurred.
https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager.html
Yeah, I had tried that (goes along with that link I posted). I was able to SSM, but logs didn't have anything to say.
Can you confirm that sshd is running with the command below?
If sshd does not seem to be starting, try starting it with the following command.
sudo systemctl status sshd
sudo systemctl start sshd
This didn't work. Bottom line, It randomly stops serving traffic on ports 443 and 22. The EC2 console in AWS says the instance is running, but it randomly stops serving traffic and after a while (maybe an hour) it will come back up again. I am not doing anything, it happens on it's own. This is a problem because my website keeps going offline
Did you find a fix? I launched a new instance yesterday, used SSH to connect fine, did some stuff, then exited last night before going to bed. Went to SSH in again this AM and I keep getting a connection timeout, checked network interface, security groups, network ACLs, tried rebooting, and it still times out.
Didn't change anything since connecting last night, everything looks good, it won't connect.
