6.5 Create a Custom VPC Part 4

00:00

hello and welcome back to the course.

00:03

In our last video, we successfully logged into our private server from our public server

00:09

using SS H agent forwarding.

00:13

We quickly discovered, however,

00:15

that we were unable to perform a U. M update on the server

00:18

because it has no gateway to the Internet.

00:21

In this video,

00:23

we will add in that gateway and then attempt to update our private server again.

00:29

So, just as a quick review, what is it that giggling

00:34

the network address? Translation. Gateway is a highly available AWS managed service

00:41

that makes it easy for us to connect to the Internet. For Marty, see two instances

00:46

that are located within our private sub net.

00:49

Prior to the introduction of the Net Gateway in 2015

00:53

we would have to configure a monitor at least two E. C. Two instances in the cluster for high availability toe actors are in that gateway.

01:03

It just added additional complexity and monitoring to R V P. C.

01:07

With the Nat Gateway,

01:10

it WS handles all of the netting for us.

01:12

The gateway has built in redundancy for high availability.

01:17

Each gateway that we create can handle up to 10 gigabytes per second of bursting

01:23

T C P u T P

01:25

and I see MP traffic.

01:26

All that we need to do

01:29

is a sign an elastic I p address when we create our gateway

01:33

which I will show you how to do shortly.

01:37

So

01:38

let's connect today W s consul

01:42

then pullup are easy to dashboard.

01:51

We should have two running instances

01:57

our public and private servers.

02:01

So now let's go back to the console

02:05

and pull a power. Vpc dashboard

02:21

didn't select Nat Gateways from the menu on the left

02:27

Quick create Nat Gateway

02:36

Let's assign it to our public sub net.

02:44

We've never created an elastic I p to this point. So select create new E i p

02:52

and then click created that gateway

03:02

while are not ***, was spinning up.

03:05

Let's quick close

03:07

the net Gatewaycan take a few minutes toe become available so I will speed up the video a little

03:21

So now it's available in AWS has assigned us in the last guy p

03:27

One thing that I will mention is that the I p addresses and that gateways do encourage charges.

03:32

So make sure that you delete the gateway when you complete this lap

03:39

next we will need to edit our route table in our private sudden it

03:51

so select the private, sudden it

04:01

and then click edit routes.

04:03

We were at a default route that will send all traffic to the Net Gateway

04:16

and then save the route

04:19

So we're now ready to test.

04:24

Let's go back to the AWS Council and pull up the EEC to dashboard

04:36

and get the address of our public. Easy to instance.

04:42

Then let's go back to my limits. Instance.

04:46

Let's add the private key again to memory,

04:59

then verified that it's there.

05:05

Cool. It's a memory.

05:08

I'll clear my screen

05:10

and let's log into our public instance using sssh!

05:14

Agent forwarding.

05:30

Awesome! So we have successfully logged into our public instance.

05:34

Now

05:36

let's log into our private instance.

05:40

Let's go back to the easy to dashboard to get the private I P address,

05:50

copy it to the clipboard

05:58

and try to log in.

06:09

Great. So we have authenticated successfully.

06:13

Now let's make ourselves route

06:18

and attempt the Yum update again

06:30

and awesome are not. Gateway is working like a charm.

06:35

Our private instance can reach out to the Internet for its updates.

06:40

Great job. Everyone

06:44

in our final video. In this section,

06:46

we will create an A C L for a private summit

06:49

and then launch our first D B server.