Error connecting to your Ec2 instance: Connection timed out
Have you faced Fatal Error while accessing your AWS EC2 instances? What are the alternatives if the SSH access fails to the EC2 instance?
Firstly, you will check the security groups and network connectivities to the instance, once it’s ok, then you need to try and connect to the instance using AWS SSM Session Manager if all the prerequisites are met.
If you try to connect to your instance and get an error message Network error: Connection timed out or Error connecting to [instance], reason: -> Connection timed out: connect, try the following:
Check your Aws security group rules that is attached to your Ec2 Instance.
You need a security group rule that allows inbound traffic from your public IPv4 address on the proper port for ssh connection you have to enter Port 22 as shown in Screenshot.
If you already allow port number 22 in your AWS Security Group then check your connection with Aws Ec2 instance through Telnet command
[email protected]:~$ telnet 53.22.22.19 22
Trying 52.22.24.99...
Connected to ec2-53-22-22-19.compute-1.amazonaws.com.
Escape character is '^]'.
SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8
Connection closed by foreign host.
[email protected]:~$
Each time you restart your instance, a new IP address (and host name) will be assigned to your Ec2 Instance.
If your computer is on a corporate network, ask your network administrator whether the internal firewall allows inbound and outbound traffic from your computer on port 22 (for Linux instances) or port 3389 (for Windows instances).
If you have a firewall on your computer, verify that it allows inbound and outbound traffic from your computer on port 22 (for Linux instances) or port 3389 (for Windows instances).
Check the CPU load on your instance; the server may be overloaded. AWS automatically provides data such as Amazon CloudWatch metrics and instance status, which you can use to see how much CPU load is on your instance