- 최신
- 최다 투표
- 가장 많은 댓글
This sounds very much like resource exhaustion, your EC2 is running out of something like CPU or memory and becoming unresponsive.
Does the monitoring tab of the AWS Console indicate anything that looks concerning around the time that the instance goes off the air?
The behaviour you're reporting reminds me of this question recently, which was a similar set-up to yours (small-ish instance, running Docker, kept going offline after a short while and had to be rebooted) https://repost.aws/en/questions/QULkwTBPOTQn-Q6cTmltB3nA/can-t-connect-to-my-ec2-instance-with-ssh
It would certainly be worth installing CloudWatch agent to collect more detailed metrics to assist in troubleshooting should this happen again https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html
관련 콘텐츠
AWS 공식업데이트됨 일 년 전
Thanks for the response. Looking at the other question and the monitoring dashboard, it does look like this is a possibility. I think the problem is I'm running a memory hungry application in Docker and have no swap file on my 2GB machine.
I'm going to try enabling a swap file of 4GB before upgrading the instance.
Thank you