Not able to connect : Putty, winscp and jenkins

Hello.
How is the performance of EC2?
For example, SSH connections may fail if CPU usage or memory usage is high.
If Systems Manager is available, "AWSSupport-TroubleshootSSH" may be used to find the cause.
https://repost.aws/knowledge-center/ec2-ssh-errors-automation-workflow

• Check instance status: Make sure your instance is running. You can check this from the EC2 console.

• Check your IP address: Your IP address may have changed, especially if you are using a dynamic IP address. Make sure the IP address you are connecting from is allowed in your security group and network ACL rules.

• SSH Port: Confirm that the SSH port (default 22) is open in the instance's security group and that your network ACLs allow traffic on port 22.

• Check system logs: If you can't connect to your instance, checking the system logs can help you find out why. To view the system logs, select the instance, choose Actions > Monitor and troubleshoot > Get system log.

• Check network connectivity: Make sure your network allows traffic on port 22. Some corporate networks block certain ports. You might need to check with your network administrator.

• Check with another client: Try connecting with another SSH client to see if the issue is specific to Putty and WinSCP.

• Verify the key pair: Confirm that you're using the correct private key (.pem) file that corresponds to the public key associated with the instance.

If you're still having trouble, you might consider contacting AWS Support. They have access to more detailed logs and information that can help diagnose the problem.