How to get onto AWS Instance from another PC

Question

I have an AWS Linux Instance with a LinuxDemo.pem key. I can access it from my own workstation no problem. But if I try and access it from home or if another colleague tries to we get the following result;

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@         WARNING: UNPROTECTED PRIVATE KEY FILE!          @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions 0644 for 'LinuxDemo.pem' are too open.
It is recommended that your private key files are NOT accessible by others.
This private key will be ignored.
bad permissions: ignore key: LinuxDemo.pem
Enter passphrase for key 'LinuxDemo.pem':
Permission denied (publickey).

Now the same command is ran on all workstations - ssh -i LinuxDemo.pem ec2-user@<IP_Address>

How can I make it that a others can access this Instance as this is important.

possible duplicate of [Trying to SSH into an Amazon Ec2 instance - permission error](http://stackoverflow.com/questions/8193768/trying-to-ssh-into-an-amazon-ec2-instance-permission-error) — Uri Agassi, May 04 '14 at 12:03

score 3 · Answer 1 · edited May 23 '17 at 12:32

3

You need to change the permissions on your PEM key on the other computers:

chmod 0400 LinuxDemo.pem

See Trying to SSH into an Amazon Ec2 instance - permission error

edited May 23 '17 at 12:32

Community

1
1

answered May 04 '14 at 12:01

Uri Agassi

36,848
14
76
93

I have seen that and tried it, but we still get the same response. – Dan May 04 '14 at 12:03
The error clearly says: `Permissions 0644 for 'LinuxDemo.pem' are too open.` recheck permissions – Uri Agassi May 04 '14 at 12:03
And be sure to distribute the private key (LinuxDemo.pem) to your other PCs – Sébastien Stormacq May 04 '14 at 14:28
I ran that command on my own PC in the directory where I keep my LinuxDemo.pem key and I forwarded it onto my colleague. He still got the same response – Dan May 05 '14 at 08:28
He should do it on _his own_ computer – Uri Agassi May 05 '14 at 08:32
Tried that too with no luck – Dan May 05 '14 at 09:37
Yes, the exact same error that I have in the question – Dan May 05 '14 at 09:59
`-rw-r--r-- 1 Daniel Dold None 1692 Feb 14 14:53 hostkeys\LinuxDemo.pem` – Dan May 05 '14 at 10:44
That's is exactly the problem! it should be `-r-------`! run the `chmod` line on that file, and try again! – Uri Agassi May 05 '14 at 10:47
`-r--------+ 1 Administrators None 1692 Feb 14 14:53 LinuxDemo.pem` Like that? – Dan May 05 '14 at 11:06
Just to confirm my colleague is still getting the same result – Dan May 05 '14 at 11:22

score 1 · Answer 2 · answered Mar 14 '17 at 08:08

1

If you dont own the private key. Adding it to your ssh agent will do the trick

eval `ssh-agent -s`
ssh-add LinuxDemo.pem
ssh user@host

answered Mar 14 '17 at 08:08

Kenichi Shibata

148
2
11

score 0 · Answer 3 · answered Jun 24 '17 at 11:11

0

Your error clearly states that it has bad permission. All you need to do is change the permission of pem file to 0400 and then try to ssh again.

chmod 0400 LinuxDemo.pem

answered Jun 24 '17 at 11:11

Prash

558
5
8

How to get onto AWS Instance from another PC

3 Answers3