1 Answer
- Newest
- Most votes
- Most comments
0
If this problem reoccurs you might also try accessing the instance using the EC2 Serial Console. Another place to check is CloudWatch Metrics to see what the CPU usage is - there could have been a runaway process.
Otherwise, in cases like this I always recommend creating a support case and talking to the team about what the root causes may have been.
Relevant content
- asked 3 years ago
- asked 4 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated a year ago