Hey and welcome back.
Now, today, we'll be discussing about the three request that appears now in general bucket on a piece
for all the S3 storage, as well as the data transfer cost, which is associated with their booking.
So let's say that we have a distributed Aurier and this is a book.
It has many big fights, so many user requests to download a one bibliophile S3, but Bucket will go
ahead and share it the file according to the policies which are attached to the user.
So assuming the user has a proper policy attached, the estimate it will go ahead and allow the user
to download that when people file.
Now, although this might not look something that can impact the building, but that data transfer out
charges associated with big fights in history is huge.
Let's quickly look into.
So when you look into the street pricing, one of the important factor here is the street, but apart
from the storage, you also have to pay for data transfer charge.
So that would be a data transfer in, as well as the data transfer out from the street market to the
Internet.
And if you look into the pricing here, it is zero point zero nine per GB for the next nine point ninety
nine per month.
So let's quickly calculate it.
So if you consider zero point zero nine per Gbps into one zero two 4G, which is one TV, the amount
of data transfer out judge that the database account will have to pay is ninety two point six US.
So this is huge and if there are multiple users who are downloading that seem fine, then the aid of
this account will have to bear not only the storage costs associated with these big files, but also
the data transfer charges.
Now, in order to overcome such scenarios, you can make use of requestor piece so that the requested
piece Buckett the requested instead of the bucket owner pays the cost of the request and the data downloaded
from the bucket.
So the bucket owner pays the cost of storing the data.
So again, this can be better explained with a diagram where you request to download of one file.
So a user from Account B, he requests to download a one fine.
So depending upon the permissions, the extra bucket will give it access granted message.
But it will also say that the account from which this request has been initiated, that account will
be the judges.
So let's say that the user belongs to Account B and this S3 bucket belongs to a county.
Then if the user is requesting and he's downloading the file from the account B, then the account from
which the user is downloading that account will have to pay for the entire charges.
So at the end of the billing, the order charges will be uploaded then.
So that's the high level overview about the request that B but let's quickly look into how we can go
ahead and enable it.
So they did the instructions.
Currently I have one bucket which is available, so let's go ahead and go inside and within the properties
section.
If you go a bit down, you have an option for the requested piece so you can go ahead and you can enable
the request piece option you and that's the only thing that is required.
So as we have seen, that enabling a requested piece in a state bucket is very simple.
Now, there are a few important part to remember.
The first one is that if you enable requestor B, then you cannot really have an anonymous request.
That means that you cannot really allow a user who is a guest to go ahead and download public objects
that are part of that bucket.
So no anonymous request will be allowed in a requested based bucket.
Second point is that if the user belongs to the same account, so let's say that the account in which
we have created a stable gate there is already a Amusa and that I am a user is downloading the object
from the history bucket, then the account from which the user belongs.
Even if it is a self account, then this is a gonda will be Jeyes before the.
So that's the high level overview about the S3 requested piece.
I hope this video has been informative for you and I look forward to seeing the next video.