Hey there! Warm greetings.
You have mentioned that you cannot connect to your instance via PuTTY. Which is giving you an error “Network error: Software caused connection abort”.
With regards to the error experienced, this error is usually experienced when using PuTTY to connect to the instance, and occurs when the session is left idle for some time, which causes PuTTY to break the connection. This can be resolved by setting a keepalive by navigating to "Connection" -> "Seconds between keepalives", and setting a value greater than 0. For more information on the error I have added a reference document [1].
Further more the CPU utilisation could have showed nothing and after a few minutes showed that it was being utilised because the instance was in a stop state. When it comes to CloudWatch metrics it takes about 5 minutes before it is populated, unless you have detailed monitoring configured which takes about 1 minute to populate the CloudWatch metrics [2].
References:
[1] https://superuser.com/questions/294824/putty-network-error-software-caused-connection-abort
[2] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-cloudwatch-new.html
Relevant questions
Lost connection to EC2 instance
asked 2 years ago"login successful... connection problem, giving up" after reboot
asked a year agoNot able to login to EC2 instance through putty.
asked 4 months agoPutty network fatal error: Connection timed out
asked a month agoLost connection to EC2 instance
asked 2 years agoUnable to enter other created instances with putty, except for first instance
asked a month agoUnable to connect to EC2 Instance through Putty
asked 3 years agoI need your help with EC2 - Network error: software caused connection abort
asked 3 years agoLOGIN INTO LINUX KALI EC2 INSTANCE FAILURE
asked 4 months agoConnection Timeout Error while connection EC2 with Putty
asked 5 months ago