Help improve AWS Support Official channel in re:Post and share your experience - complete a quick three-question survey to earn a re:Post badge!
free tier ec2 instance not launching through putty showing error "Network error : connection timed out"
I have created 2 ec2 instance (redhat linux)of free tier t3 micro size in Stockholm region.I have been using these ec2 instances from past few days but today when i tried to connect through PUTTY , it was throwing error "Network error : connection timed out".
AWS data transfer 1GB free transfer is exceeded. ec2 instance used 2GB . could this be the reason or anyother?
- Newest
- Most votes
- Most comments
hello Shyam,
Please below method once to helpful to connect your instance:
Go to Iam select the role and give ssm full permissions Create role.
Go to ec2 dashboard and select instance and Actiones seclect security AND Modify Role Add you previusloy created role and wait 2/2 instance state after select instance and click on connect through system manager.
Possible Reasons and Solutions Instance State:
Check Instance Status: Ensure that both EC2 instances are in the "running" state. Instances that are stopped or terminated cannot be accessed. Action: Go to the EC2 Dashboard in the AWS Management Console, check the state of your instances, and ensure they are running.
Security Group Configuration:
**Inbound Rules: **Make sure the security group associated with your EC2 instances allows inbound SSH (port 22) traffic from your IP address. Action: Go to the "Security Groups" section in the EC2 Dashboard, find the security group attached to your instances, and check the inbound rules. There should be a rule allowing SSH access (port 22) from your IP. If not, add a rule to allow inbound SSH traffic from your IP address or 0.0.0.0/0 (not recommended for production environments due to security risks).
Network ACLs:
Check Network ACLs: Ensure that the Network ACLs (NACLs) associated with the subnet of your EC2 instances allow inbound and outbound traffic on port 22. Action: Go to the VPC Dashboard, check the NACLs for the subnet, and ensure that they allow inbound and outbound traffic for SSH (port 22). Instance-Level Firewall:
Check IPTables: If you have configured a firewall on the instances themselves, ensure that it allows SSH traffic. Action: If you can access the instance through another method, such as an attached console, check the IPTables or firewalld configuration.
Elastic IP:
Public IP: Ensure you are using the correct public IP address or Elastic IP to connect to your instances. Action: Verify the public IP address assigned to your instances and make sure you are using that IP in PuTTY. Network Connectivity:
General Connectivity: Ensure that your internet connection is stable and that you can connect to other resources over the internet.
Action: Test your network connection by trying to access other websites or services to ensure your local network is not causing the issue.
AWS Maintenance or Issues:
Check AWS Health Dashboard: There might be ongoing maintenance or issues with the AWS infrastructure in the Stockholm region. Action: Check the AWS Service Health Dashboard for any reported issues in the Stockholm region.
Hello.
Even if you use up your free tier, you will not be unable to use SSH.
Is your IP address allowed for SSH in your security group?
Also, is the public IP address of the EC2 you are trying to connect to correct?
Please check the following documents for other troubleshooting methods.
https://repost.aws/knowledge-center/instance-vpc-troubleshoot
By the way, have you tried restarting EC2?
Also try connecting with Session Manager. https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager.html
You must use the public IP address of your instance instead of its private IP.
I used public IP , still it didnt connect. please check below answer
If you are using Putty, you can check the event log for more details. https://documentation.help/PuTTY/using-eventlog.html
Another person had the same error today.
There may be a problem with Putty, so try connecting using Teraterm.
https://repost.aws/ja/questions/QUkgAnWmSCQ4q6NV2k93Ma8g/no-supported-authentication-methods-available-server-sent-publickey#ANrlDjdOzeTi2SENGQBP0Fzw
when i select public ip it is throwing server refused to connect
Faced similar issue while trying to access from MobaXterm.Relevant content
- asked a year ago
- asked 4 days ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 years ago
Hello Anil , Thanks for answering. both the instances are running. i have set port range & protocal to - ALL
Please look at the below i mentioned another procedure connect your instance through IAM SSM-Role