I have created an EC2 Instsnce on a t3.medium and I can't ssh to it. I used NextClouds image at boot and managed to configure my Next Cloud service.
I tried adding a custom domain I have on CloudFlair to it and it seemed to work. I was able to hit it and login to NextCloud. Then the next day when I tried to hit it I couldn't and also when trying to SSH to it i was unable too with it just saying it had timed out. In the Instance console everything apeared to be running with no errors and looked normal.
I then gave it a reboot and about 30 mins later everything seemed up and running again. Not sure what is causing this behaviour weather I haven't set up my custom domain correctly or something to do with NextClouds image.
I can't see anything in the logs suggesting something has gone wrong and can't think of any trigger that may cause it's seemingly random downtimes.
Any knowledge about this is much apreciated.
Thanks,
James
AWS OFICIALAtualizada há 3 meses
Hi, thanks for responding. Yes it does look like there are spikes in the CPU usage rate up to 60%. No OS System Log errors by the look of things.
Are there any metrics that are showing abnormal values when checking the EC2 CloudWatch metrics?