Logging into an AWS instance with SSH doesn't have to be a challenge.
If you work with the AWS platform, chances are you're going to need to access your various instances using SSH. But unlike standard access to a server that runs an SSH daemon for access (where you can simply issue the command ssh USER@IP (where USER is a user account on the remove server at IP). That won't do with AWS—at least not "out of the box".
When you first launch an instance on AWS, you generate a key pair. You only have one opportunity to copy that key pair, so you must be sure to copy and paste it to any machine you'll use to access that instance via SSH. The file in question will have a .pem extension.
SEE: Windows 10 security: A guide for business leaders (TechRepublic Premium)
If you've saved that .pem file to your desktop, you shouldn't have any problem using SSH to gain access to your AWS instance.
Let me show you how.
The SSH Command
Remember, you're not using secure shell in the standard fashion. We have to instruct SSH that we're using an identity file. Said identity file will be the .pem file you've saved from your AWS instance. Let's call that saved .pem file mykey.pem and save it in ~/.ssh. I'm going to assume you already have your AWS instance up and running and said instance is of the Linux sort. To use that .pem file with SSH, the command would be:
ssh -i ~/.ssh/mykey.pem USER@INSTANCE_ADDRESS
Where USER is your AWS instance username and INSTANCE_ADDRESS is the actual address of your Amazon AWS instance.
Importing your own key pair
Let's say you want to import your own key pair to an AWS instance. If you already have your SSH .pub key to import, all you have to do is log into your Amazon EC2 console and follow these steps:
- Go to NETWORK & SECURITY.
- Click Key Pairs.
- Click Import Key Pair.
- Click Browse.
- Navigate to the directory housing your .pub file.
- Type a name for the key pair and click Import.
If you have yet to generate a key pair, here's how (I'll demonstrate from the Linux command line). Open a terminal window and generate the key with the command:
ssh-keygen -P "" -f ~/.ssh/mykey.
The above command will create the following two files:
Once you have your key pair, you can then import the mykey.pub file as shown above.
What about ssh-copy-id?
With regular Linux servers, you can easily copy your key pair with the ssh-copy-id command. But with an AWS instance, things get a bit tricky. However, there is a way around the complication.
First off, you need to log into your AWS instance and issue the command:
sudo nano /etc/ssh/sshd_config
In that file, change:
Save and close the file. Restart SSH with the command:
sudo systemctl restart sshd
Before you copy the key pair, you need to make sure you have your original AWS key saved to the local machine and issue the command (assuming you've saved your AWS key to ~/.ssh):
Where KEY is the name of your AWS key.
Once that command completes, you can now copy those keys with the command:
ssh-copy-id -i ~/.ssh/id_rsa.pub USER@INSTANCE_ADDRESS
Where USER is your AWS instance remote username and INSTANCE_ADDRESS is the public address of your AWS instance.
That should successfully copy your key to the AWS instance. You can then go back into the /etc/ssh/sshd_config file and change PasswordAuthentication from yes to no. Restart the sshd service, and you're good to go. At this point you should be able to access your AWS instance in the standard SSH fashion (ssh USER@INSTANCE_ADDRESS).
- The clearest sign of AWS' open source success wasn't built by Amazon (TechRepublic)
- How to create an instance of S3 cloud storage in AWS (TechRepublic)
- How to create a virtual machine using Lightsail in AWS (TechRepublic)
- The 4 most important files for SSH connections (TechRepublic)
- Top cloud providers 2019: AWS, Microsoft Azure, Google Cloud; IBM makes hybrid move; Salesforce dominates SaaS (ZDNet)
- How to become a cybersecurity pro: A cheat sheet (TechRepublic)
- 10 dangerous app vulnerabilities to watch out for (TechRepublic download)
- Online security 101: Tips for protecting your privacy from hackers and spies (ZDNet)
- The best password managers of 2019 (CNET)
- Cybersecurity and cyberwar: More must-read coverage (TechRepublic on Flipboard)