CodePudding user response:

Please help have a look at the great god, I'm a sister, is no other solution, please help me,,,,,

CodePudding user response:

1. Wait five minutes the server completely started complete
2. Check the security group 22 port instance open
http://docs.aws.amazon.com/zh_cn/AWSEC2/latest/UserGuide/using-network-security.html

Finally according to others' tutorial
https://leonax.net/p/3280/connect-amazon-ec2-instance-through-putty/

CodePudding user response:

1. The ec2 instances created whether to enable public access?
2. Look at your set of VPC correct?
Can refer to "learning - EC2 amazon AWS custom VPC configuration" :
http://blog.csdn.net/dongdong9223/article/details/47153421
"Amazon AWS learning - VPC inside a few relations of the concept of" :
http://blog.csdn.net/dongdong9223/article/details/47724029
The hope can help you,

Welcome to visit my aws column: http://blog.csdn.net/column/details/amazon-aws.html

CodePudding user response:

I also encountered the same problem with you, is configured with a lot of times, is not even in, have the public IP, but get less than public DNS, browser connection and putty to connect all not line, just indicate connection timeout

CodePudding user response:

Learn

PPPCLOUD arrow cloud hosting, the country's first full SSD cloud disk host free take! www.pppcloud.cn

CodePudding user response:

Solved? I remember correctly, I was connection should be to download an encrypted file, and then import the file decryption in the PUTTY, before they can be connected,,,,,,, so many days you would have to solve

CodePudding user response:

User name ec2 - user, not the root

CodePudding user response:

The problem how to solve??

CodePudding user response:

Should be 22 of TCP port is not open, you can refer to the following article,
http://blog.csdn.net/aiyueqingfeng/article/details/51332234

CodePudding user response:

Refused access SSH refused, check the Auth under SSH KEY file within the pair?

CodePudding user response:

I also encountered the same problem, the solution is the security group in the port 22 of limiting access to the address, to your own public address or any address line:

CodePudding user response:

There is something wrong with the Settings, aws manual of it,,,,