- Newest
- Most votes
- Most comments
Hello,
The issue appears to be memory related based on the symptoms you have described, you can also reference this link [1] that covers the same remediation steps. "Reboot the instance to return it to a non-impaired status. The problem will probably occur again unless you change the instance type".
Exhausted memory [1]
When the memory is exhausted, the kernel doesn’t have enough memory to run. When this occurs, other processes are stopped to free memory, making the instance unresponsive. You can try to reboot or stop and start the instance. These procedures reduce memory usage.
Unfortunately, AWS Cloudwatch does not natively monitor memory metrics on instance level, however you can configure the cloudwatch agent to report memory usage metrics to cloudwatch. I've linked this AWS blog [2] which covers a detailed walk-through on setting up memory monitoring. You can also use linux tools like top, atop and even the free -m command to view memory usage whilst being connected to the instance via ssh.
If the problem is indeed memory related you will need to upsize your lightsail [3] instance to a bigger instance.
[1] Unresponsive Lightsail Troubleshooting: https://aws.amazon.com/premiumsupport/knowledge-center/lightsail-instance-failed-status-check/
[2] Monitoring memory usage: https://aws.amazon.com/blogs/compute/monitoring-memory-usage-lightsail-instance/
[3] Creating a larger instance: https://lightsail.aws.amazon.com/ls/docs/en_us/articles/how-to-create-larger-instance-from-snapshot-using-console
Relevant content
- asked 2 months ago
- asked 2 months ago
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 months ago
Thank you so much.