chmod-600 file: A private file only changeable by the user who entered this command.chmod-400 file: To protect a file against accidental overwriting.Ssh -i “username.pem” username For deleting user, admin needs to just execute following command to delete the user. So that by following command user can ssh to the EC2 server.Provide private key to the user to whom we are providing access to the server.Copy that key and add into authorized_keys file in EC2 instance that we have already created.pemĮnter file in which the key is (/Users/tudip/.ssh/id_rsa): Generate a public key for the user from the private key-pair ( username.pem) that admin already has created in AWS account.Switch to created user account to add public key so that user can SSH to the EC2 instance.Īdd permissions: chmod 600 authorized_keys.This will create a new account with the name “myusername” in the EC2 instance.Admin will create a new user into EC2 machine with the particular username to identify the user to whom we are allowing access to this server.Ssh -i “root-access.pem” Shows overall AWS KEY MANAGEMENT process. AWS root user has his root PEM file by which admin can “SSH” into the server with root access.AWS root user needs to create a Key-Pair for the particular user.

One short answer is that create separate PEM for all the users.

Here comes the IDEA of AWS KEY MANAGEMENT. In such a case, when multiple developers are there it is very risky to allow all developers/users to access the instances with admin PEM file.

There is an application installed on EC2 from where we can create a multiple AMI under VPC and using load balancer we can distribute or route the traffic on the instances. As you know we can create multiple EC2 (AMI) in VPC (Virtual Private Cloud) and create load balancer to route the traffic.

Chmod 400 pem