Here and welcome back.
Now, in the earlier video, we had a great introduction to the content delivery networks now in the
architecture diagram that we were discussing where between a user and the origin, there is a clear
that proxy's that exists between two.
And apart from Proxima, the request, Celian also can provide functionalities like the do as protection,
valve caching and others.
So today will be precisely looking into it in a demo aspect so that this concept is better understood.
Now what we have is we have a WALKSTATION.
So Walkstation is where we are actually recording this.
We do.
We have a screen.
So we're making use of the Idalis cloud service here and we have origin.
So Origin can be a server.
It can also be a stable where you're storing the fight.
So in our case for Demo we have a stable where the files are stored.
So if you see the bucket, there are four or five SOYER.
Some of them are indexed that estimate.
Some of them are a regular text files and some of them are the images over here.
Not instead of solving the files directly from the S3 bucket, what will be doing will be solving it.
Whitecloud.
So we also have a cloud distribution which is created over here and this cloud from distribution will
be acting as a proxy or acting as a middle aged between a workstation and the origin.
So let's try.
So I copy the domain name here and within the new tab.
Let me go ahead and adding grid.
So as soon as I press enter, you will see that you have a welcome to the demo page.
So this is nothing but the index, that HD file which got so.
So now let's say you want to open this regular.
So all you have to do, you'll put regulatory text and you should see the contents of regular order
to Fallujah.
Now, you'll also see that there is an image file which is showing that jpeg.
So let's try and open that as well.
So just add the name shivved and you should be able to see the image file also.
Now, again, since we discussing that a client can also provide functionality like deduces protection,
valve caching, etc., let's go in and look into it.
So this specific cloud print distribution is associated with the Web application firewall.
So currently we have a list of that which is created.
And this is why if you look into the associated resources, it is associated with our clutterham distribution.
So what would typically happen is that any request that comes to this area, it will be evaluated by
device and that can block the request depending on the rules that are configured at every level.
Now, I have configured one rule here which basically states that any request which has a part of it
may not be in its you are right that the request should be blocked.
Now, generally a lot of blogs, a lot of websites and only have the admin panel associated in the you
are a part of admin.
So that is something that we want to block as of now.
So this is a very simple rule.
So in the extra bucket, if you'll see that I have added a file admin, not so now.
Let's go ahead and see what happens if we go ahead and open that file.
So let's put admin, not 60.
And as soon as you put it, you basically see you get a four zero three, which is a request for.
So if you see the contents, it says a request has been blocked.
So this request being blocked is the responsibility of the of that which is associated with this claim.
So that is one part.
Now, you can also have things like gassing and gassing works pretty well.
In fact, let me quickly show you this part.
So let's open up the shift back.
So when you open this image, what would typically happen is that at this image, if it has been requested
for a lot of time, it would have been stored at the client level.
The image would not be requested from the origin, which is a theory.
Let me quickly show you to validate this one.
So let's open this up and refresh this page.
In fact, let me just maximize it, so this is a request, so this request, if you see in fact, let
me open this up.
Great.
So if you look into the request head as a lawyer, so this is the request which the browser had made
already.
So this request, if you see it, goes towards the host of cloud friendly gardening.
So my Web browser made a request to the cloud for distribution.
Now, in response to this request, Glau friend basically gave an email away.
So if you look into the response headers, the content type is image apparent.
And within your within the cache, you have a message from cloud front.
So that basically means that the image that we requested, that image was not present at the screen
level and it was requested from the origin.
So now when you request for the image multiple times, as we were discussing, Cloud friend will go
ahead and store that image within its own servers.
So let's explore that as well.
So I have quickly refreshed the page and let's open up the same image.
And within the response headers now you'll see that in the cache header there is a hit from cloud front.
So now what is happening is this image that we requested.
The response directly came from cloud, from cloud, from had stored that specific image.
And as soon as the WALKSTATION requested, it immediately sent back to the workstation.
So this hit from cloud front not only reduces the overall traffic, which goes to the origin servers,
but it also improves the latency.
That basically means that the website actually loads much more faster.
Great.
So that's the high level overview of Cloud four.
And now you can actually do a lot of things at a cloud first level.
So there are a lot of features which it offers.
For example, you can have a jurisdiction restriction as well as the cloud level.
So what you can do is that if you want a traffic to not come from a specific country now, many times
it has been observed that a lot of attacks, they originate from certain countries.
So if you do not want that country to make a request to your server, then you can block it either 7-Eleven
and whenever a request that comes, the screen will verify if it is originating from a specific country
or not.
And if that originating country is within the blocked list at a certain level, then they will go then
block it.
So that's the high level overview about the content delivery network in terms of a demo so that this
will conclude this video.
I hope this video has been informative for you.
And I look forward to see you in the next video.