Haroon, and welcome back now into this, we will be discussing about the basics of routing policy and
our 53 now at a high level overview against fellow routing, basically allows you to rout the traffic
to a resource when the resources help or to a different resource when the first resource is unhealthy.
So let's assume that this is a setu instance and this is the first resource area.
So all of the traffic that is directed towards the road, 53 will go to this force resource of easy
to instant's.
However, in case of this instance goes down, then with the help of fellow routing, we can tell Roud
53 that all the queries should be directed toward the different end point altogether.
And this is very common in a lot of Lipsett.
So basically you might have seen a lot of maintenance beedis that might be upcoming.
So in case if the primary website is not running due to some reason, then automatically Deerness like
it out 53 with the help of fellow routing, can direct to a maintenance pit so that the overall inconvenience
remains lesser in terms of user experience.
So let me do one thing.
Let me give you a quick demo so that we can understand this in a better way.
So currently within Route 53, I have two records that have been set and they are based on Filho routing
policy, Soyuzes routing policies based on failure, and Varnum on the record is referred as a primary
and second record is called secondary.
So basically the fourth is doing things with the primary.
Traffic should go is also referred as the primary.
And the maintenance base that we were discussing is a reference to the secondary recall.
Now, what will happen is that if this primary record fails, then Route 53 will automatically direct
the traffic to this secondary value, which is the maintenance page hosted on Amazon s three.
Now, let me quickly show you both of them.
So let's quickly open up the first value in the browser.
You see, the website works perfectly fine.
Now, one of the questions that comes is how does the Road 53 determine if the resource is healthy or
not?
And that determination is through the health check.
So currently I have a health check that is configured for an easy two instance.
And currently, if you see the health check is perfectly healthy.
So this website is basically loaded from the SC to instanced for which the health check is associated
with.
Now for this AC2 instance, if I have to quickly show if I lose Estancia status, Angelique's you see
the Engine X is currently active and running and this is where the website is from.
So let's do one thing.
Let's go ahead and do a call on field or dot.
Keep eLab starting now at this stage, this specific record failure, Kapil observed Internet the associated
health check is healthy.
That basically means that the Routt 53 will direct the traffic to this first value, which is the IP
address of these two.
So when you do a call, you should see the big admin file that is upcoming.
In fact, if you will quickly do a call on failover dot KP lives dot Internet, you should basically
see that the server here is Ingenix, followed by the version number.
And if you'll quickly do it and lookup on field or dot keeping tabs on the Internet, it is basically
directing to the server with IP ending time before that one to one, which is same as the value that
we have defined.
Now let's take another scenario where this is two instance.
The website will go ahead and stop it.
So let me go ahead and those systems can stop.
Ingenix All right.
So now if you quickly refresh the page, you see you immediately get an error stating that the site
cannot be reached.
Now, since the site is not working, even the Hatake, subsequently, it will change from healthy to
unhealthy.
So let's quickly wait for a moment here.
So on a subsequent refresh, now, you see the status has changed from healthy to unhealthy.
Now, if things are working perfectly well as far as the fellow routing is concerned, then the request
should not go too easy to instanced, but instead it should go to the secondary endpoint associated
with S3.
So let's try it on.
So let's clear the page and this time let's do a call again on Freeloader Capi on Internet.
You see, you are getting a message stating that this is a maintenance page.
Now this specific maintenance page is coming from a three bucket called Freeloader Kapil, the Internet,
which in turn basically contains this index data.
So let me also show you this.
So if I quickly open up this objective URL, you see, this is.
A maintenance beat, and this is the exact beat that we are getting as far as that girl is concerned,
and now even if you do and look up on the Internet this time, you see you basically get a different
IP address altogether.
That's correct.
So with this, I hope at a high level overview, you understood the basics as well as the advantages
that of Fallujah routing policy provides.
So with this will conclude today's video.