The cloud service that I noticed a while ago really brought me a new world.
Previously I thought of cloud services like Naver N drive or Dropbox, and thought Amazon was a cloud service.
I am hosting a completely different cloud server ..
In any case, I got the Free tier right so I decided to create an AWS Instance.
[Status is running well with running.]
First of all, I followed the menu and made an instance
How to access this server console …..
Connecting to the AWS Console (ssh) with Putty
How to connect from Windows using Putty is as follows.
1. Download pem (key file) from AWS
2. Convert pem file to ppk file for access via PuTTY
3. Put the connection information in PuTTY and connect it by putting the generated ppk file.
A more detailed connection procedure is as follows.
# Create and download a pem file to download the key pair for access.
1. Access the AWS Console (https://aws.amazon.com/console/) and login
2. Create and download pem via “NETWORK & SECURITY”> “Key Pairs”> “Create Key Pair”
(Note that if you lose a pem file, there is no way to get it back.
# Putty does not support pem, so you need to convert it to ppk.
# To run the application for conversion, you need to install Full Package, not Putty.
3. Run PuTTYgen on the installed Putty Full Package.
(A process for converting a downloaded pem to a usable ppk in PuTTY)
3-1. When PuTTYgen is executed, the following window will appear. Press “Load” button to load the downloaded pem file in step 2.
(The remaining options remain as default (SSH-2 RSA, 2048))
3-2. After loading, the contents of the file are displayed as below. Press “Save private key” button to save as ppk (PuTTY Private Key) file.
4. Now that you have a key file to access AWS with PuTTY, run PuTTY.
4-1. Type ubuntu @ “public dns name” in Host Name as shown below.
In the example below, I installed ubuntu on the host and started with ubuntu @ because the default id is ubuntu.
In addition, the public dns name can be checked in the first snapshot, which can be found in the EC2 Console.
It will configure SSH (22) as it will use ssh.
Basic ID setting
Amazon Linux AMI: ec2-user
RedHat5 AMI: root or ec2-user
Fedora: fedora or ec2-user
SUSE: root or ec2-user
4-2. Now let’s put the key file we created earlier
Select “Connection”> “SSH”> “Auth”.
5. You will need to keep using the settings later.
First, enter the name you want to save and press the Save button.
Then press the “Open” button to connect.
6. A pop-up window will appear and you can connect.
[Final connection completed]
I think that there was an option to connect without using Key file.
However, this option is not recommended by the AWS policy, but the security is strengthened by using the key file.
It seems to be good for AWS or me to do this because it is as troublesome as policy.
Additional Information (Obtaining Ubuntu Root Authorization)
If you connect as above, you will be able to connect to ubuntu account, so the authority to install programs such as deb installation is limited.
So you need to have root privileges.
There is no root password because it is a connection after initial installation. You set the root password through sudo passwd.
If you try to acquire root privilege through su -, you can acquire root privilege with the passwd you just set up.
$ Sudo passwd
[Set root password]
$ Su –
[Enter the password that you have already set]
[Root privilege acquisition completed]