1 Answers
0
It looks like the instance ends up being unresponsive after gradual increase in load over the day. Depending on the instance type chose, you should check the CPU Utilisation / CPU Credits of the instance before you attempt a stop + reboot to rule out CPU bottleneck. Memory metrics are not available by default and you would need to configure CloudWatch agent for this. Another quick fix alternative, would be to switch to a higher instance type to check if the system uptime increases also. But that would obviously mean an increase in cost for that duration.
Based on the behaviour you described, I'd assume system resources being a constraint and the need to switch to higher instance type. But better to validate it with metrics
--Syd
answered 3 days ago
Relevant questions
Not able to login to EC2 instance through putty.
asked 4 months agoNew feature DAY NIGHT CYCLE Editor
asked 5 years agoEc2 instance goes down every day
asked 4 months agoA Record (Cloudflare) pointing to EC2 instance not reachable
asked 4 months agoOnly can reachable one day
asked 4 days agoCognito set user MFA required when using TOTP only
asked 4 months agoEC2 Linux Instance is up but not reachable
asked 19 days agoA new EC2 instance is created after termination of the only instance
Accepted Answerasked 2 years agoWebsite not reachable
asked 3 years agoEMR main instance is not reachable. Please check your instance status.
asked 5 months ago