1 Answer
- Newest
- Most votes
- Most comments
1
when the problem occurs, it can only be recovered by a reboot, then it makes it hard to debug because you cannot login while the problem is occurring. This type of problem is normally caused by software running on the instance, rather than anything to do with Amazon EC2 itself.
First thing to check would be Amazon CloudWatch Logs to see whether the CPU is 100% when the problem happens.
Next thing to check is the log files on the computer, which you can examine after the restart. You could configure a script to continually log the CPU and processes in use to a log file, so that you can examine them later to determine the underlying cause.
answered 23 days ago
Relevant content
- asked 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago