Sometimes when you try to connect to AWS EC2 instance, whether by SSH or HTTP, you get one of these errors: “access denied,” or “operation timed out,” or some other variation and you will not be able to login. Please find some of the below common issues which may cause connectivity issues to an EC2 instance.
Check whether your EC2 instance passes both System and Instance Status checks or not.
Check your instance state whether it is running or in stopped state.
Ensure that the security group which is attached to your EC2 instance allows access to port 22 for Linux, port 3389 for Windows and port 80/443 for web access.
Verify whether your network access control list (network ACL) allows access to the instance.
Verify that the internet gateway is attached to the VPC in which your EC2 instance has been provisioned.
Make sure the route table of your instance's subnet contains a rule for the destination via the internet gateway.
Ensure you are using correct key pair to access the instance.
Verify the DNS Name whichever you are using whether that is correct or not.
Verify the System Logs to check the error messages.
Verify whether Public IP address changed recently, as stopping and restarting an instance can result in a new IP, if you are using Public IP.
Verify storage as well, because full disks may cause problems.
Comments