Everyone, and welcome back.
Now, in the earlier video we were discussing about the basics of Fallujah routing, we also looked
into the demo on our Fallujah routing Woodfork.
So in today's video, we'll start with an interesting practical way.
We'll go ahead and implement this from scratch.
Now for Today said the first thing that we need is a two instance.
So currently I already have a AC2 instance that is currently in the running.
So this is basically a two micro based Amazon Linux to be easy to instant's.
So what we'll do is first we'll go ahead and create a zone and let's quickly just call it escapee Livedoor
Internal.
And this would be a private coastal zone and this will be associated with the VPC vadis, two instances
created.
So in this case, I have created it in Mumbai region and this is the default VPC.
So in the region, let's select episode one, which is Bombay, and there is only one default VPC.
So we'll go ahead and selected ones then let's go ahead and create the hosting zone.
Perfect.
So our coastal zone is created.
Are two instances created now for the fellow routing to work?
First thing we need is a Web page, so there has to be some web server at tector instance level.
So let's go ahead and quickly do that.
So let me copy the IP and let's go ahead and connect to the to will switch to route.
Let's do a young install.
Ingenix It will give you the exact amount to install in the next LED's copy and paste this up.
And I do have a great show, the installation is completed, let's go ahead and start in the next website,
Aurier.
Now, along with that, make sure that the security group allows portability.
So let's go ahead and for it quickly and I'll do a rules perfect.
So are instances up and running in order to verify the website is up?
Let's go ahead and copy the IP and the top secret in the browser and things seems to be working.
Well, that's great.
So now we have about 53.
We have two incidents.
Now, first thing that is needed here is that around 53 should be able to verify if the website is running
or not.
So in order to do that, what we need to do is we have to quickly create a health check.
So we'll be creating about 53 based healthcare.
Let's quickly create a health check, let's call it as Ingenix website.
And within the IP address, I'll post the IP address.
Where the Ingenix is running will keep things simple.
Let's do a next and I'll create a perfect sort all the time.
The status of this health care gets updated.
Let's go back to the hoster zones will open up our hoster tonier and let's create a new record.
So within the record name, let's just call it as demo failover.
And you have a record type of key and a value.
Let's go ahead and paste the IP address of, for instance.
Now, within the routing policy, this time will go ahead and select the routing policy of failure.
The failure type is primary.
So basically, this is the primary resource where the request would go to.
And now you also have to associate a hell with it so you can associate the health of Ingenix website
so it will quickly verify health check is healthy.
So things seems to be good.
And within the record you can specify Ecto in Mumbai.
All right.
You can go ahead and create a record.
Great.
So our first record of failure based routing policies created now at this stage at all fifty 53 will
go ahead and it will do a health check.
It will also direct the traffic.
Now, the second thing that we want is around 53.
If it detects that the health check has failed, it should be redirected to a different resource.
Now, when it comes to different results, it can be a different Pictou instance.
It can be a streeting point and so on.
So to keep things simple, what we do is we create a new S3 bucket, which will contain a maintenance
page.
So let's quickly open up history and let's go ahead and create a bucket.
Now, the bucket name.
Let's give it the same name that we have as part of our record, which is the most order capillaries
that internal.
So let me put this over here.
So this is very important.
The bucket name.
The next thing, let's go ahead and remove the option to block all public access, primarily because
this extra bucket will contain a maintenance beat, which should be allowed to be opened by anyone in
the Internet.
So we'll remove this part.
Let's go back down and highlight.
So we have to acknowledge it and let's do it perfect.
So our bucket is created.
Let's quickly open this up.
And what we'll do is we'll upload a simple maintenance page based HDMI file, so I'll quickly upload
it.
You can go ahead and click and add files and you can select the appropriate index.
Anyways, what I'll do is I'll go ahead and upload this in the external as part of the resource so you
can also use the same file in terms of permission we want.
Everyone should be able to work.
So I grant the public read access here and we'll do an upload.
Perfect.
So now let's go back to this subject.
Let's go to properties will go up, bit down and within the static website hosting.
I'll edit it and let's enable it within the indexed document you can specify in the e-mail.
So anyone who visits this, this file should be loaded by default once.
Then we can do a sea change.
Perfect.
So thing seems to be good as far as the Israeli budget is concerned.
Let's quickly verify I'll open up this index and it will give me the you are let's open this.
You are able to see if we're able to see the maintenance page and the answer is yes, we can.
Perfect.
So now at this stage, we have both the easy doing stance.
We have the S3 bucket with the maintenance, we have a.
So the only thing that is Bandino is to create a failure of type secondary.
So let's go ahead and create a record.
This record, you have to ensure that the name remains to be the same.
So it is demo failure exactly same as that of the previous record.
The record, they will select it as a.
And will enable the sort of, you know, as soon as you enable it now, you see you have various options
whether you want to have the secondary based on cloud front, network load balancer, a strain point
and so on.
So we want the secondary website to be based on a three point.
So I'll select this in terms of region.
Let me go ahead and select the Mumbai region.
And if you click Coya, you should see that your estimate of Luchador Kapil Absurd Internal has appeared.
So we'll go ahead and click here along with that routing policy.
Just keep it as a failure.
The failure to contain this thing would be secondary and already you can just sleep on it once, then
you can go ahead and create the record.
Perfect.
So now at this stage we have two records of routing policy failure.
One is based on S2, which is the primary, and the second one is based on S3, which is the secondary.
So now let's go ahead and test things out.
So within the easy to instance, let's quickly do a call on the move over the Internet.
And this should show you a big e-mail page which is based on Ingenix.
So things seems to be working fine.
So now what we'll do is we'll intentionally go ahead and stop the index so that our health check will
fail.
Now, after the health check will fail, then only about 53 will go ahead and roll the traffic to the
secondary failure record.
So let's go back to our old 53 Keltic.
So after a few minutes, let's refresh this.
And now the endpoint is showing us ANELLI.
So going back to the easy to instance, let's go ahead and run the call.
Come on on the demo.
Freeloader keep observed internal.
And this time you'll see you get the maintenance speed.
So this maintenance beat is coming from a history book.
Now, do know that if you're trying this practical and if you're not seeing this, you can go ahead
and maybe after two to three minutes try to run the call.
Come on again.
And it should work perfectly well.
That's great.
So I hope at a high level overview, you understood the basics about the implementation area of Falluja
routing based on about 50 to now make sure that after we have completed the practical, you go ahead
and delete the resources, specifically the about 43 Keltic and the other resources as well that are
not needed.
So this will conclude today's video.