- 最新
- 投票最多
- 评论最多
Confirm the EC2 instance has a public IP address, and use AWS Console / EC2 Instance Connect to establish browser-based SSH session. If you are still unable to connect, recommend launching a new EC2 instance using the defaults (including Allow SSH traffic from 0/0) in a public subnet. If you are able to connect to the new instance then recommend comparing the VPCs, Security Group, and subnet route table to ensure a path between your client and the EC2 instance. There is also the Network Access Analyzer tool that can assist with troubleshooting.
More information: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html
is it possible that the instance which you are able to connect exist in public subnets and other server which you are not able to connect is in private subnet?
Security group is open for port 22 and VPC subnet route table internet gateway configured correctly. On the same configuration already existing ec2 instance is working. One of the instance and other being created new instances are not accessible. SSH connection refused. Would you advise further