2 Answers
- Newest
- Most votes
- Most comments
1
Hello.
Snapshots and the website inaccessibility issue are not related, so deleting the snapshot will not resolve the issue.
Have you checked the web server or application error logs?
Also, isn't the CPU usage rate high?
Depending on the instance type you are using, it may stop working even if the CPU usage is slightly high.
If you are using t2 instances, etc., it is possible that CPU credits are being consumed, so you may want to check CloudWatch.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-credits-baseline-concepts.html
Relevant content
- Accepted Answerasked 5 months ago
- asked 2 months ago
AWS OFFICIALUpdated 4 months ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Yeah, deleting the snapshots didnt resolve the issue, also all security inbounds rules are disabled cannot connect to anything even witht he instance running! ... What you recommend mate, Im so frustrated, I took a lot of time to put this running last weeks. I stopped the instance and change the instance type to t3a.large ... which one do you recommend for a small bussiness!?
Have you checked the web server or application error logs? Not yet
Also, isn't the CPU usage rate high? How I know!
Thanks
Since you won't be able to connect anything unless you allow the necessary port number for the security group's inbound rules, why not change it to only allow your IP address? I think "t3a.large" is an instance type that can handle a certain amount of load, but perhaps its specs are still insufficient. Also, check the instance system logs. You won't know for sure unless you look at the logs, but I think it would be a good idea to check if you don't have enough storage space. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/troubleshoot-unreachable-instance.html#instance-console-console-output
Changing the instance type made the trick mate ... thanks a lot mexicogym.com is alive again! thanks for your help mate! blessings