Here you are.
And welcome back.
Now, in today's We Do will be discussing about one of the interesting features of about 53 of it is
checks.
Now at a high level overview, Amazon drought 53 health check basically allows us to monitor the health
and performance of your Web application, Web servers and other resources.
So basically, you have around 53 and you have your endpoint.
So let's consider this endpoint as AC2 instance or reservoir.
So with the help of health check, Waltraud, 53 will do is that it will go ahead and send certain request
to the server and it expects the response from it.
Now, depending upon the response and the configuration time that you have can figure it out.
We will consider this endpoint to be healthy or unhealthy.
If it is unhealthy, then that 53 can also send alarms to you if required.
Now, let me quickly give you a demo about this.
So basically I have three about 53 ticks that are configured for three different websites.
The first one is the key pillars, health check, which is currently healthy.
And within their description, you basically get the DNS with the health check is happening, which
is capable everything followed by the Port Authority.
Then you also have one hell check with the name of the website.
This is basically redirected to IP address, which is 124, 53, dot 184.
And then you also have one more associated with the name of the website.
And this is also redirected to a specific IP address here.
Now, since Roud 53 is able to successfully open up this specific domain, it considers it to be healthy.
However, for the other two, if you will see both of them are considered to be unhealthy.
Now, along with that, one out of three also allows us to set alarms.
So let's see our Hatake feeds, order website stops responding.
Then you can also set an alarm for that.
So far, one of the domains here which is associated with the IP address currently in alarm is associated
with it.
So if I quickly click over here, you see the state is currently in the alarm.
So in case if I also have to show you very quickly.
So let me go ahead and quickly open this up.
So currently, you see the website is not loading at all.
And this is the reason why the hatake associated with this is failing now along with this.
Let me also show you one more interesting thing.
So let's open this up.
Let me go here.
Now, in this case, you see a website is loading perfectly well.
However, still, the health check is showing is unhealthy.
Now, if you'll quickly go to the inspector here, let's go to the network and let me rephrase this
page.
Now, in the output of the status, you see, although the website is loading perfectly well, but the
status is for 034 dividend.
So you see the EDP status code is for 034 dividend.
And this is one of the reasons why it is showing is unhealthy, even though a page appears here.
So generally it expects it to work six or 3x HTP response, quote, for the website to be considered
as healthy.
So there are a lot of configurations that you can go ahead and do whenever you want to use it out.
53 for heretics know whenever we are discussing about that out 53 help take one another.
Very important item that comes up is that about 53 health articles.
So out of the three has helped us in locations across the world.
So basically what happens is that whenever you go ahead and create a heretic in Drought 43, the health
workers start to send a request to the endpoint.
I do specify to determine whether the endpoint is healthy.
So these hatake so you can consider them to be a small service that are distributed across the world.
And Route 53 uses this service to send a request to the endpoint and look into whether the response
is coming or not, and depending upon the response or target, is considered as healthy or not healthy.
Now, let me also show you that.
So let me open up one among them and let's look into the health tickers now currently within the health,
because you're you will see that there are a lot of healthcare types from which the query is made.
So your 15 one one seven six seventy three fifteen one one seven to seventy five and so on.
So there are a lot of locations from which the request can be made.
So you're under the heretically, then you have Tokyo, Singapore, Signy Island and many others.
So this is one of the great ways in which you can quickly identify if your website is accessible or
the world or not.
So that's a very high level overview about the health tech features in Drought 53.