Sie sind auf Seite 1von 3

How to create another user in ec2 instance and connect using putty.

[root@ip-10-50-1-135 etc]# adduser shyam -passwd

[root@ip-10-50-1-135 etc]# id shyam

uid=1003(shyam) gid=1003(shyam) groups=1003(shyam)

[root@ip-10-50-1-135 etc]# passwd shyam

Changing password for user shyam.

New password:

Retype new password:

passwd: all authentication tokens updated successfully.

[root@ip-10-50-1-135 etc]# su - shyam

[shyam@ip-10-50-1-135 ~]$

[shyam@ip-10-50-1-135 ~]$ ssh-keygen -t rsa -P '' -f ~/.ssh/id_rsa

Generating public/private rsa key pair.

Created directory '/home/shyam/.ssh'.

Your identification has been saved in /home/shyam/.ssh/id_rsa.

Your public key has been saved in /home/shyam/.ssh/id_rsa.pub.

The key fingerprint is:

SHA256:PiKA4TBbpU4HmP4UF248GBl4iSIk8xYuWgUXkjl9kyM shyam@ip-10-50-1-135.ap-south-
1.compute.internal

The key's randomart image is:

+---[RSA 2048]----+

|++BBOo.. |

|**+&E.= |

|O Xo+B o |

|+& o. . |

|+.= S |

| o . |

| . . o |

| . . . |

| |
+----[SHA256]-----+

[shyam@ip-10-50-1-135 ~]$ cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys

[shyam@ip-10-50-1-135 ~]$ cd .ssh

[shyam@ip-10-50-1-135 .ssh]$ ls -ltr

total 12

-rw-r--r-- 1 shyam shyam 430 Jul 2 17:14 id_rsa.pub

-rw------- 1 shyam shyam 1679 Jul 2 17:14 id_rsa

-rw-rw-r-- 1 shyam shyam 430 Jul 2 17:15 authorized_keys

[shyam@ip-10-50-1-135 .ssh]$ cp id_rsa ../id_shyam_rsa.pem

[shyam@ip-10-50-1-135 ~]$ cat id_shyam_rsa.pem

-----BEGIN RSA PRIVATE KEY-----

MIIEpAIBAAKCAQEA1UTWFtDYBj8Km+DXaeOyhwnydZnMa31BK5WdWaGYMFt9JsF1

wT52iXdclXY9hFWeydkoeUE49p1U6qc8gD0wuLeGmOJdngTAx6XtyBo516Q43ZVZ

7nDQB00EfddgnqncysPY/Ht2RSNyZ16lolfxA5L54GcIACLDOQO3BBDdE82OH0DW

qx6RxfGGiOp3caOvdhnpRTEOE10Y80JGnyHgt5TfR9D8Zu64bNi2NJUFAeCstoDV

2I6almfliUzTVJaYVK2kmIuMS+y8UfsUrOepOMK9GVg/DNcPK73lsOVENR6zM5EV

+xQe//GZvhdFxtJ1MBDbiN9WCOMZYjlQz/3ELwIDAQABAoIBAAZ0zwZhzChkQC33

4I2UFxN/eZeV0FpwsEhhfyH3gmP0YRWLRcVT3sLKmkLsEXCwJt51dIQ3NUJCARAZ

f/th3te4tppqP+tIuY1RuKEWKiodDpumqdJOF/4glsI4gvRKsCRzSV5bXnk5WX1H

oDwJ7YHuMSJZ/CQE6WQQeLnmyMqQoFWSV5ov3UGvY42xOQUxF5Rq8WT8wT6g3nNw

nIFLqnb9s68CgdDnoGfM2fNp6To7Kz+4kMOjPujDiHjN4J4EL1ho1aZ9dcJ46zI5

4aj9sbl5tGx/PB4ud5fJu8eT+pBAHi09jQCgxCM9KyGhHssVBkS45GWLd2o+VWns

ZO2hGgECgYEA8Ik2d2hqMMEC3GVcR6qm+tkNMjc9rk9yPWBNcKNh11j6qEE2Vpmo

dNi2euQwznvcRxUrX9re8ke+O4e7Ci+41uOJdOacFLqXs32ldDmVsrGlMUwQEyT6

2xZOUigDf2iNJ5GbaWFTd53lsV3kGAIzZj52+1vL0Vm1fPPMHPJIH30CgYEA4vrb

QL2ctXbp3BBbxajHcdaH1gf+9QGUhl926FFnzzhjKP+cmwn91ju2pqJ5SqJaZkoh

yQ+/2E5Y/Q8zqrTDQeGiX0QdXs1fqGx0F9JfCC7uVVMA3cmXVE8SNnZVGvaLjgm8

nFHITAcKDbEzH85zh34YsvVaGqg+K+HOYg562hsCgYEAt3tzmNKFbntM+2I2alS6

208Gye9plbX0puz3JZz73ZF6Yy6bjKPZ5IgLauL2eAvzlCWJ2KzUtGwVqMN44eRV

U1ZuXEYteYJ8heaqd2YV0yG/qUMkX/YthUIWrITpZh8SzcQ8kL41NWG0/P9qJwZG

vw+XI1Z6u097Kb2vTcVjTuECgYEAtXexyzTNERedKN+7P3AM5KqLt0Z1RBSbVkME

ogBTaoy+Wozh++IlGx5qjRbguhbLB3TFRiZdTuZ0pv18ZUJXyVhHpLqkcKLpk5IB
zvnWGIjM61KNIsSFRFZjTT+WExSBxnFqZd/Mr1wBYakGIqvAGddqj8kw3Jcd/Z9u

jV7eQXkCgYBtHjrtcpUzSIAJw/Xhj3VCHYWYM8CvizJmnqO+/LkWkKvC6gkbFEZx

Ogx+CPI/iSIbLfQfryEMryqjEdurOcQmdXswrJ7zL0JzWA2YZl4ne8Tp9aO2vsxX

mvDkaN0qyKfwEMWOSrTXqplYMWz6wI7yUmTec/pEfidYPp5+ktBobg==

-----END RSA PRIVATE KEY-----

copy this file and save it in desktop name "shyam.pem"

now using git

ssh -i "shyam.pem" shyam@ipaddress

you are able to conect now.

troubleshoot:
$ ssh -i "shyam.pem" shyam@13.233.161.96

shyam@13.233.161.96: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).

login using ec2-user and sudo su

vi /etc/ssh/sshd_config
#PasswordAuthentication yes

uncomment and restart the sshd service


[root@ip-10-50-1-135 ec2-user]# service sshd reload
Redirecting to /bin/systemctl reload sshd.service
[root@ip-10-50-1-135 ec2-user]# client_loop: send disconnect: Connection reset by peer

try again you are able to login.

Das könnte Ihnen auch gefallen