I was also running into this - turns out I was using a community-created AMI - and the default username was niehter root, nor was it ect-user or ubuntu. In fact, I had no idea what it was - till I tried 'root' and the server kindly asked me to login as xxx where xxx is whatever it tells you.
If you are using EBS, you can also try to mount the EBS Volume on a running instance. Then mount it on that running instance and see what's going on in /home. You can see things like is the user ubuntu or ec2-user ? or does it have the right public keys under ~/.ssh/authorized_keys
Its ec2-user for Amazon Linux AMI's and ubuntu for Ubuntu images. Also, RHEL 6.4 and later ec2-user RHEL 6.3 and earlier root Fedora ec2-user Centos root
Just adding to this list. I was having trouble this morning with a new user just added to an AWS EC2 instance. To cut to the chase, the problem was selinux (which was in enforcing mode), together with the fact that my user home dir was on a new EBS attached volume. Somehow I guess selinux doesn't like that other volume. Took me a while to figure out, as I looked through all the other usual ssh issues (/etc/ssh/sshd_config was fine, of course no password allowed, permissions were right, etc.)
The fix?
For now (until I understand how to allow a user to ssh to a different volume, or somehow make that volume a bona fide home dir point):
发布评论
评论（20）
对于 Ubuntu 实例：
对于其他实例，您可能必须使用
ec2-user而不是ubuntu。我使用过的大多数 EC2 Linux 映像仅默认创建 root 用户。
另请参阅：http://www.youtube.com/watch?v=WBro0TEAd7g
For Ubuntu instances:
For other instances, you might have to use
ec2-userinstead ofubuntu.Most EC2 Linux images I've used only have the root user created by default.
See also: http://www.youtube.com/watch?v=WBro0TEAd7g
现在是：
Now it's:
Canonical 的发行版默认使用用户“ubuntu”，任何使用 ubuntu 映像登陆此处但遇到相同问题的人都可以使用该用户。
Canonical's releases use the user 'ubuntu' by default for anyone landing here with a ubuntu image that is coming up with the same problem.
如果您使用的是 Bitnami 图像，请以“bitnami”身份登录。
看起来很明显，但我忽略了一些事情。
If you're using a Bitnami image, log in as 'bitnami'.
Seems obvious, but something I overlooked.
对于我的 ubuntu 映像，它实际上是 ubuntu 用户而不是 ec2 用户；）
For my ubuntu images, it is actually ubuntu user and NOT the ec2-user ;)
如果您正在运行 Bitnami 的 AWS 映像。用户名是bitnami。干杯!
查看我的调试并查看最后一个
**
：
If you are running AWS image from Bitnami. The username would be bitnami. Cheers!
see my debug and look at the last one:
*
*
使用 openSSH 的 Ubuntu 10.04
这是确切的用法：
例如：
上面的示例直接取自 AWS 连接到 Linux/UNIX 机器的教程，网址为：
http://docs.amazonwebservices.com/AWSEC2/latest/GettingStartedGuide/
Ubuntu 10.04 with openSSH
this is the exact usage:
for example:
above example was taken directly from the AWS tutorial for connecting to a Linux/UNIX machine at:
http://docs.amazonwebservices.com/AWSEC2/latest/GettingStartedGuide/
如果 pem 文件权限过于开放，它也会抱怨。 chmod 文件到 600 来解决这个问题。
It will also complain if the pem file permissions are too open. chmod the file to 600 to fix that.
我也遇到了这个问题 - 结果我使用的是社区创建的 AMI - 默认用户名是 niehter root，也不是 ect-user 或 ubuntu。事实上，我不知道它是什么 - 直到我尝试“root”，服务器友好地要求我以 xxx 身份登录，其中 xxx它告诉你什么。
-干杯！
I was also running into this - turns out I was using a community-created AMI - and the default username was niehter root, nor was it ect-user or ubuntu. In fact, I had no idea what it was - till I tried 'root' and the server kindly asked me to login as xxx where xxx is whatever it tells you.
-cheers!
您需要在本地计算机中拥有您的私钥
您需要知道远程计算机或服务器的 IP 地址或 DNS 名称，您可以从 AWS 控制台获取此信息
如果您是 Linux 用户
（
chmod 600 <私钥文件的路径>）(
ssh -i <私钥文件的路径> <用户>@<远程服务器的 IP 地址或 DNS 名称>)如果您是 Windows 用户
You need have your private key in your local machine
You need to know the IP address or DNS name of your remote machine or server, you can get this from AWS console
If you are a linux user
(
chmod 600 <path to private key file>)(
ssh -i <path to private key file> <user>@<IP address or DNS name of remote server>)If you are a windows user
使用...
不要使用 600 权限，否则您可能会意外覆盖您的密钥。
use...
don't use the 600 permission otherwise you might overwrite your key accidently.
对于 Debian EC2 实例，用户是
admin。For Debian EC2 instances, the user is
admin.连接有 2 个步骤：
对您的私钥进行 Chmod 400，这样其他人就无法访问您的密钥：
要通过 SSH 连接到您的实例，您需要知道实例的公共 IP 地址：
希望它有帮助！
There are 2 steps to be connected:
Chmod 400 on your private key, like this the others cannot access to your key:
To connect to your instance in SSH, you need to know the public IP address of your instance :
Hope it helps !
这对我有用：
删除工作站上存储的旧密钥
也可以使用而不是
再次执行相同的 ssh 它有效：
在 ubuntu 实例上，用户名是：ubuntu
在 Amazon Linux AMI 上，用户名是：ec2-user
我不必从映像重新创建实例。
this worked for me:
to delete the old keys stored on the workstation
also works with instead of
then doing the same ssh again it worked:
on ubuntu instances the username is: ubuntu
on Amazon Linux AMI the username is: ec2-user
I didn't have to re-create the instance from an image.
ec2-keypair.pem的权限应为400chmod 400 ec2-keypair.pemPermission for
ec2-keypair.pemshould be400chmod 400 ec2-keypair.pem如果您使用的是 EBS，您还可以尝试在正在运行的实例上挂载 EBS 卷。然后将其安装到正在运行的实例上并查看 /home 中发生了什么。您可以看到诸如用户是 ubuntu 还是 ec2-user 之类的内容？或者它在 ~/.ssh/authorized_keys 下是否有正确的公钥
If you are using EBS, you can also try to mount the EBS Volume on a running instance. Then mount it on that running instance and see what's going on in /home. You can see things like is the user ubuntu or ec2-user ? or does it have the right public keys under ~/.ssh/authorized_keys
就我而言（Mac OS X），问题在于文件的中断类型。试试这个：
1.- 使用 TextWrangler 打开 .pem 文件
2.- 在应用程序底部，验证中断类型是否为“Windows(CRLF)”。
In my case (Mac OS X), the problem was the file's break type. Try this:
1.- Open the .pem file with TextWrangler
2.- At Bottom of app, verify if the Break Type is "Windows(CRLF)".
它的 ec2-user 用于 Amazon Linux AMI，而 ubuntu 用于 Ubuntu 映像。
此外，RHEL 6.4 及更高版本 ec2-user
RHEL 6.3 及更早版本 root
Fedora ec2-用户
Centos 根
Its ec2-user for Amazon Linux AMI's and ubuntu for Ubuntu images.
Also, RHEL 6.4 and later ec2-user
RHEL 6.3 and earlier root
Fedora ec2-user
Centos root
只是添加到这个列表中。今天早上，我在刚刚添加到 AWS EC2 实例的新用户时遇到了问题。言归正传，问题出在 selinux （处于强制模式），而且我的用户主目录位于新的 EBS 附加卷上。不知何故，我猜 selinux 不喜欢其他卷。我花了一段时间才弄清楚，因为我查看了所有其他常见的 ssh 问题（/etc/ssh/sshd_config 很好，当然不允许密码，权限正确，等等）
修复？
现在（直到我了解如何允许用户 ssh 到不同的卷，或者以某种方式使该卷成为真正的主目录点）：
就是这样。现在我的新用户可以使用他自己的 id_rsa 密钥登录。
Just adding to this list. I was having trouble this morning with a new user just added to an AWS EC2 instance. To cut to the chase, the problem was selinux (which was in enforcing mode), together with the fact that my user home dir was on a new EBS attached volume. Somehow I guess selinux doesn't like that other volume. Took me a while to figure out, as I looked through all the other usual ssh issues (/etc/ssh/sshd_config was fine, of course no password allowed, permissions were right, etc.)
The fix?
For now (until I understand how to allow a user to ssh to a different volume, or somehow make that volume a bona fide home dir point):
That's it. Now my new user can log in, using his own id_rsa key.
有同样的问题。尝试使用“ec2-user”或“root”登录时权限被拒绝（公钥）。
在 Google 上搜索了机器映像的 AMI 编号，它在 Debian wiki 页面上有 SSH 登录信息。
希望这有帮助。
Had the same issue. Permission denied (publickey) when trying to login in with 'ec2-user' or with 'root'.
Googled the AMI number of the machine image and it had the SSH login information right their on the Debian wiki page.
Hope this helps.