Here and welcome back.
Now, in the early video we were discussing about the basics of about 53 heretics, and we also looked
into some of the important concepts, like about 53 health.
So in today's video, we'll go ahead and implement that outwardly, three health checks from scratch
so that we understand the practical steps required to configure one.
So going back to that outfit, Fredricka.
So let's go ahead and open up the health checks section here.
And from here, you can go ahead and create a healthy.
Now, one of the first things that you will have to specify is the name.
So this can be any let's just call it the more health check and now comes on.
What is the exact resource that you want to monitor?
So you want to monitor it and point out as part of a cloud, watch alarm and so on.
So for simplicity, let's use end point for the time being.
So what we'll be doing is we'll go ahead and create a server and we'll be providing the IP address of
the server as part of the endpoint.
Or, you know, when you discuss about monitoring an endpoint, you can go ahead and specify the endpoint,
both in terms of IP address or domain name, whichever is convenient for you.
So let's do one thing.
Let's go to the instances will quickly go ahead and launch.
An easy to instance will use Amazon Linux too, and we'll use the instant tape associated with the fruitier
eligible will do a review and launch.
And let's quickly go ahead and launch the instance.
That's great.
So our instance has been created along with that, just for a better understanding, will also go ahead
and create elastic IP.
Let's look at a new elastic IP.
Great.
So first, let's do one thing, let's copy of this elastic IP address and we'll go ahead and put it
over here.
All right.
Now in the protocol as well, you have a GDP is GDP as well as TCBY.
We keep it simple.
Let's use Eastbay for the time.
Now, if you'll click on the advanced configuration here, you can do a lot of things.
You can specify what is the request interval, the failure threshold, the latency graph and so on.
And one of the important things that we were discussing here is the healthcare region.
So these are the regions that are part of the U.S. recommended option.
However, in case, if you want to customize it, that is also something that you can do.
So you can go ahead and add or remove certain regions as part of the healthcare here once.
Then you can go ahead and click on next.
You can also go ahead and create alarm.
If that is required for simplicity, let's do a no and will create a Hatikvah.
So currently the status is unknown, however.
Now what will happen is the healthcare will go ahead and start to send the request to the specific IP
address and it will realize that there is no response that is coming.
And then this the status would change accordingly.
Now, for the time being, let's go to the instances.
Here are instances running.
Let's go ahead and quickly connect it from the easy to connect.
So now will quickly go ahead and install a Web server.
So just yum install it.
If you'll do that, it will basically give you the command, which is Amazon, Linux extras install
and the next one.
So let's go through this up and will paste it.
I do away and perfect.
And it is up and running.
So now you can quickly verify the status of the Web server.
The Web server is currently in the inactive stage, so let's go ahead and quickly started.
So now let's quickly verify their status yet again.
And perfect.
Our Web server is running as expected.
So now let's go back to the instance.
Let's copy the public IP associated with this easy to instant's and let me Gordon, paste it within
the browser.
So currently, if you see you're not seeing any website aurier primarily because of the security group.
So let's go to security will open up the security group.
Let's edit the inbound will because there is no rule associated with the port.
It will either neutral.
The range would be pretty and will do a zero zero zero zero one.
Then you can go ahead and save that.
Once you've added a security loophole, if you deface this page, you should see the end Web site.
That's great.
So now let's go ahead and refresh the page.
And for the first health check that we have created, the status is now unhealthy.
So now let's go ahead and create one more healthy picture.
Let's call it as Ingenix.
The website will specify the endpoint and the IP address will use this IP address here.
The portal remains to be seen.
You can also specify the path in case if you also want to specify the advanced configuration here,
you can do that.
However, for the time being, let's keep it simple and we'll go ahead and create the healthcare.
Let's do a next album.
We don't really need for that.
I mean, I'll create it.
All right.
So our health is currently in the unknown stage.
So now, as expected, around 53 health workers will start sending request to this end point.
So if you want to quickly monitor that request, let's quickly go to valore you have a director of engineers
and let's monitor the access logorrhea.
So within the access log here, you'll see that there are multiple requests that are coming from the
road, 53 health workers.
So you see you have Amazon and all 53 health service and there are multiple different requests associated
with it.
No.
One more important thing that you will see that the response code is 200.
That basically means that the destination client was able to successfully load the website.
Let me do a Andruzzi.
One more important thing that you should know is that there are multiple different IP addresses from
which the request is made.
So you have 15, 177, 34, 71, 10-15, 15, 177, 38, 71, then 58, 71, 60 to 70, 150, 73 and
so on.
And this is the benefit associated with healthcare because health good are in multiple regions.
You can go ahead and quickly identify if there are any issues that are ongoing across the globe.
Now, let's quickly refresh the page now.
Since the health worker was able to successfully see the website, the oral status is healthy.
Now, you can also from health take a step.
You can also see the details, basically the IP address in the healthcare region and in the state.
As you see it is getting this data scored of 200.
That's great.
So I hope this you understood the basic concept of Rule 53, Keltic, as well as the importance of health
TICAS.
So with this will go ahead and will conclude today's video.