welcome back to part two of our easy to lab.
As you can see, we're on my *** unto Lennox VM.
I am using the linens, Veum,
because it is much easier interact with are easy to instance natively
If you are using a windows machine for this video,
then you will need to download putty.
For those of you who may not be familiar with putty,
it's a free terminal emulator
that will lie you to interact with your PC. To instance,
some things are slightly different.
So I will make a second video to show you how to set up putty from a Windows box.
So if you recall from the last lesson
I downloaded the private key that AWS generated for us
to my documents directory.
So what I will do now is create a new directory
sshh, underscore keys.
I will run the L s command
to ensure that the new directory has been created.
now I will move our private key to the SS H Keys directory.
let's change into that directory.
We will run a L s command again to verify that the move was successful.
Now we need to change the permissions on our private key to make it read only
this is very important for the security of our private key.
let's make ourselves route,
to make the file permissions read. Only
we can verify the commission by running
This shows us that the file is now read only.
now we are ready to log into our e c two instance
sssh space e c to dash
Then we paste in that public i p address that we copied from the last lesson.
we provide the dash I flag, which is telling our easy to instance to read the identity file,
which is our private key for authentication.
let's copy and paste our file name.
Remember that without this private key, we will not be able to authenticate toh ar e c two instance
And now we see the EEC, to instance, has responded to us
and it's telling us that has never seen our key before.
This is normal for the first time that we log in.
And now the EEC, to instance, will add a copy of our key toe a host file.
The next time that we log in, it will compare the key that we present
to the one in its host file and basically will say, Oh, yeah, I know you already
Now we have successfully authenticated toe are easy to instance,
if you recall from previous lessons
A W S provides the basic operating system that are easy to system will run on
We are responsible for the security updates software etcetera
A. W s calls this the shared responsibility model
R e c two instances informing us
that we need to apply at least six of the 14 security updates
that are available, for instance.
let's update those now
we need to change to root.
this part is a matter of preference.
We use yum toe update this flavor of lyrics.
Since this will be our Web server,
I like to install the Web server first
and then apply all the updates.
So let's type yum space install
to load Apache server.
so that it was installed without prompting us.
Next we perform a young update dash. Why?
To install the necessary system updates.
Let's create a landing page for our Web server.
We change directories to force Last bar forward slash dubbed dubbed up
From here, we use a text editor.
to make a static home page for our Web server.
We will name the file index dot html,
and I will paste in simple HTML coat,
then click control Dash X to close out the file.
perform a shift. Why, then enter?
we need to enable the Apache server on our instance.
H t t p d Space start, then enter.
Finally, we are ready to test our Web server.
Let's open up a browser
and type in the I. P address of our easy to instance
and there is our web page.
Great job, everyone.
we created our first easy to instance,
we created our first security group.
We created a P K I I ke pair for our easy to instance,
we created a Web server