- Newest
- Most votes
- Most comments
For the record and for the sake of helping anyone facing this same issue as Lightsail users won't get technical assistance; The solution isn't to upgrade your instance... as 2VCPUs and 1-2 gb RAM is a lot for a micro service or a webpage in wordpress... the solution is to set a swap file to double of your instance's RAM. By default neither bundle has a swapfile, this means when you face a memory usage spike the OS will kill any process to free some memory including SSH.
This command will help you to create a swap file... sudo fallocate -l 4G /swapfile && sudo chmod 600 /swapfile && sudo mkswap /swapfile && sudo swapon /swapfile && sudo sed -i '$ a/swapfile swap swap defaults 0 0' /etc/fstab
Jorge
Hello.
Is it possible to connect using ssh command etc. instead of via VSCode when bursting?
Also, have you ever used up all your burst credits when you were unable to connect?
https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-viewing-instance-burst-capacity
Just to complement, my burstable graph looks like this and sometimes it takes over 30 min to let me connect again and by then my nohup node process running was dropped and my service halted.
Hi, Thank you for reaching out to us about the issue you are facing. Some of your instances reaching 100% CPU Utilization may be causing the disconnection problem. We recommend upgrading to larger bundles from smaller ones, as this can help alleviate the issue of CPU Utilization reaching 100%.
Relevant content
- Accepted Answerasked 2 years ago
- asked 8 months ago
AWS OFFICIALUpdated 3 months ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
No, it's impossible to connect via ssh directly. As for the second question, never I'm always over 90% of burstable credits. I'm wondering if there's any issue regarding nodeJS. I've already migrated instance twice using snapshots as well as clean install, I always face this issue.