I need SSH access to an Amazon EC2 instance running Ubuntu 10.4. All I have is the Amazon username and password. Any ideas?
13 Answers
Basically, you need a private-key file to login into your EC2 via SSH. Follow these steps to create one:
- Go https://console.aws.amazon.com/ec2/home & sign in to your existing Amazon account.
- Click on "Key Pairs" on LHS or https://console.aws.amazon.com/ec2/home?region=us-east-1#s=KeyPairs.
- You should see the list of KEYs generated by you (or during EC2 creation process).
- Click on "Create Key Pair" if you don't see any or you lost your private-key.
- Enter a unique name and hit enter.
- A download panel will appear for you to save the private-key, save it.
- Keep it somewhere with the file permission "0600"
- Click on "Instances" on LHS or https://console.aws.amazon.com/ec2/home?region=us-east-1#s=Instances
- You should see the list of ec2-instances, if you don't see any, then please create one.
- Click on the EC2 machine and note down the Public DNS address.
- Open your Terminal (in Linux) and type the following command
ssh -i /path/to/private-key root@<ec2-public-dns-address>
- the root username has been avoided in the latest releases, based on your distribution selectec2-user
orubuntu
as your username.- hit Enter
- That's it.
STEP 1) Download private keys assigned to your ec2 machine (which is only one time download when created. so recommended to commit somewhere)
STEP 2) and fire following commands,
chmod 400 MyKeyPair.pem
ssh -i MyKeyPair.pem [email protected]
Official Doc : Connecting to Your Linux/Unix Instances Using SSH
If you are using MacOS, you should create/edit SSH configuration file (~/.ssh/config) and put something like:
Host *.amazonaws.com
User ubuntu
Port 22
StrictHostKeyChecking no
UserKnownHostsFile=/dev/null
IdentityFile ~/PATH/YOUR_DOWNLOADED_KEY.pem
Then to connect to any of EC2 instances:
ssh MYNAME.amazonaws.com
Nothing more!
To setup Ubuntu on AWS, please follow the following steps:
- Log-in to Amazon Web Services and select EC2.
- Choose Launch Instance and follow wizard by selecting the right image (Ubuntu), instance type, configuring VPC network and Subnet, storage and allowing SSH access in Security Groups. Then Launch.
- For the first time, you probably need to setup the key pair and assign it to the instance. You can also create key pair in Key Pairs. Once created, download the PEM file and keep it in a safe place.
- Once the instance is launched, wait until the instance is Initialized and running.
To access the instance via SSH, run:
Connect to Linux box by specifying your PEM file, e.g.
ssh -i "file.pem" [email protected]
Make sure your PEM file has 600 permission (
chmod 600 file.pem
).
Troubleshooting
If you're running VPC instance, and your security group is correct (with the right rules) and it still doesn't work, in VPC section check your subnet which should be attached to your VPC (both used by your instance) and setup new rule in Route Table that has 0.0.0.0/0
as Destination and your Internet Gateway as Target.
For more details check: Troubleshooting Connecting to Your Instance
See also: Possible reasons for timeout when trying to access EC2 instance
1) First chmod
the .pem file
for restricting the file permissons as below
chmod 400 my-key-pair.pem
2)Then
ssh
with the following commands directly from .ssh
folder
ssh -i my-key-pair.pem [email protected]
Note:- To navigate into .ssh
folder. First press Ctrl + H
to display all the hidden files and finallycd .ssh
Not logging in as the correct user for you OS Distro could be the issue. For certain new AMI, the username may not be "ubuntu", but "ec2-user". For Amazon Linux, for instance I believe the user is "ec2-user". Eric Hammond gives examples here: http://alestic.com/2014/01/ec2-ssh-username
My suggestion, try:
ssh -i /path/to/file.pem ec2-user@ec2...
ssh -i /path/to/file.pem ubuntu@ec2...
ssh -i /path/to/file.pem root@ec2...
If you have the wrong AMI, you might just want to restart the machine altogether so you have uniformity amongst your clusters. If this is your problem, you'll probably want the same OS Distro's at least for your linux boxes.
Doing what is suggested in all these answers is not enough. Against each instance you see a security group. When you launch a new instance, you will have this thing set to default. You need to edit the security group and add the ssh port it. Later you need to add the 8080, 8443, 80, 443 ports also when you want to host your website.
First change permission of pem file by
chmod 400 path/to/key_pair.pem
Inside the file ~/.ssh/config add the following lines, at the top of the file
Host AWS
Hostname myserver.com
User myuser
IdentityFile path/to/.pem/file
port 22
Hostname take IP or link of server, User take username of server and Identity file is file downloaded from AWS when you created instance. Just Run the following command in terminal
ssh AWS
and enjoy it!
Note: To navigate into .ssh
folder. First press Ctrl + H
in home folder to display all the hidden files and finally cd .ssh
Make sure these thing in check
private key must have 400 permission
Make sure port 22 is open for AWS instance you are trying to access.
ssh -i privatekey.pem [email protected]
// XXX.XXX.XXX.XXX = your instance public ip