Come back this is domain number five the storage options or the storage services in the US.
And we are going to start with some research or service or three.
This is not planned to be started from scratch or a 0 2 here on S-3 So it assumes that you already have
the associate level knowledge about S-3 you know what S-3 is what an S3 bucket is worth as an object
and so on and so forth.
This is going to stress on features of S3 that are important and relevant to that exam.
So just to set expectations right please do a quick review for the s 3 knowledge that you have had before.
And let's get into stressing or reinforcing what the features are and how important they are when we
use them and for the exam as well.
So let's dive in and find out what we have in the last couple of lectures.
Versioning is important when you would like to keep different versions of your files or when you want
to give yourself a second chance so let's say you edit a file you uploaded that to the bucket and it
is not in every version what will happen.
The new one that you're uploading will override the old one.
If they have the same key or the same name if you don't want that to happen.
And at the same time or you want to keep versions of the file so you can do versioning of the file and
you can keep track of what changes happen between the different versions.
Then you enable bucket version.
So bucket version is S3 bucket Sabri source.
It is used to protect against accidental object or data deletion or overwrite version can also be used
for data retention and archive.
So I will keep versions.
But I mean starting and keep let's say for vergence can't and anything older than four versions will
be archived so I can use it later on for other things or for any other purposes.
Once you are unable to back it versioning on a bucket it cannot be disabled but it can be suspended
and we'll discuss what happens when you suspend versioning on a bucket that had it enabled before when
enabled.
But that version will protect existing and new objects.
So if I had the bucket and the bucket already had objects before the Enable versioning.
Once you enable it then both the existing and the new objects that you will upload to the bucket will
be protected or we'll have versioning effective on them and it will start maintaining versions as these
objects the existing ones or the new ones are updated edited right into how can you update objects.
These are all HTP actions like the pupils to copy and delete action.
So these are all etched ETP delete markers.
So let's say I have a bucket the bucket has all objects uploaded to it and I enabled versioning on the
bucket when you tried to delete an object.
What happens to that.
I would do an HDTV delete four object ABC 2:59 this object doesn't get deleted permanently.
So when you do that the file will be merged with a delete marker.
So the file will not be deleted immediately.
It will have a delete marker on it from the object can still view that version or that the file.
Yes you can still view the object and the delete marker.
Now let's say I did that by mistake and I have the delete marker is not deleted permanently.
Can I reconsider deleting the object if it was a mistake can I just remove that delete marker and then
make the object available again.
Yes you can.
You can do that.
You will be charged.
And that's one thing to note that if you have any versioning it's cute and neat feature that you can
use comes in handy protect your files and all that.
But this is all storage right.
The more versions you store the more size you are using of a street the more cost will be there as well.
So we need to have a strategy as to how many versions you can keep and for how long.
So this is very important as well.
So you can use versioning with something we call S-3 lifecycle policy.
You can have a policy to decide what to do with the objects that do delete them do you archive them
to a cheaper storage what exactly you want to do with that.
So you can combine versioning with lifecycle policies and both are sub resources to as a three bucket
in order to either delete them or move them to a cheaper storage.
Glacier is one example and I'll talk about it later on.
That's the archiving of it.
Yes but it virginals state.
So if you have a bucket from a versioning standpoint what are the possible states for that bucket.
It's either version is enabled on the bucket or it was enabled and you suspended it or it was an inversion.
So this is the the initial one when you enable versioning you get to that enabled if he's suspended
you going to spend suspended state versioning applies to all objects in a bucket and not personally
applied.
So if I have a bucket and I have multiple objects can I say I want this object to be version but I don't
care about this one or that one.
No it's across the bucket the entire bucket.
Either it's all Virgine or it's all virgin or suspended objects existing before enabling versioning.
Have a virgin ID of null case or any version of the object that you upload before enabling versioning
on your bucket.
It will have a version ID of none.
If you have a bucket that is already divergent then you suspend versioning existing objects and their
versions remains as is.
So I have this bucket.
It was version it was enabled.
And then I went and suspended that and changed the state change it into suspended.
What happens to the objects that I had and their versions of these objects.
They are as is now what will happen if I upload a new version of an existing object.
After the versioning was suspended what happens to this one.
And what happens if I upload new ones.
Can I delete.
Let's see that in our next slide.
One thing to add before we move to the next line is if you have an object with its versions and you
suspended versioning the object on the verge of women as is however they will not be updated or version
further with future updates.
So what will happen then when I upload a new version to the bucket.
This is what we'll see in our next light while the bucket version is suspended.
What happens to the new object I'm going to upload.
New objects uploaded will have a version ID of nothing.
Now if I uploaded an object and it has an object id of NULL and then I upload a new version.
What will happen it will override the existing one.
So in this complete object over an object deletion in a suspended version bucket will only lead the
object with ID.
And if you delete totum if it delete if I need to protect my files and my file versions on my object
versions from being deleted.
So you want to do a second level of security and protection for your objects and your bucket.
OK so now we use MFH which is multi-factor authentication.
So basically if you have the credentials and permissions to access the bucket if you want to change
Buckett creatures or you want to delete objects or virgins within the bucket then your credentials are
not enough you will be prompted to have an MF a key combination of letters or digits depending on the
device you are using that you have to enter as well.
In addition to your permission so you have two levels of security in order to be able to do that change
the bucket or two an object multi-factor is in the kitchen.
Delete is a versioning capability.
So it's called M.F. delete.
That adds another level of security and keeps your account is compromised.
So it's a multi-part upload.
It's used to upload an object or a object in parts.
So instead of loading the whole object in one operation.
So what you do is if you use multipart upload the file will be divided into pieces and then these will
all be uploaded in parallel.
So what do you gain.
Of course you gain speed and you gain faster upload better use of performance or experience as well.
So parts are uploaded independently and in parallel in any order.
So which object size are recommended for that object sites hundred make or larger.
However you can use for object sizes starting from 5 megabyte to 5 kilobytes remember this is the largest
size you can do in S3.
You must use it for objects larger than 5 gigabytes.
So it is recommended for five hundred gigabytes or more.
It is a must for files five gigabytes or more.
The copy operation.
What does it do.
So you are copying an object in an S3 bucket.
You can copy it to the same budget you can copy to another bucket you can copy it even to another region.
You can create a copy of an object of your object up to five gigabyte in size in a single atomic operation.
Remember when we said the multipart upload is from a hundred megabyte recommended at 5 gigabyte it's
a must.
So up to five gigabyte you can make the copy in one atomic operations and basically are copying the
file as a whole.
But if it is larger than that larger than 5 gigabyte then multipart upload is your only option.
Use the copy operation to do what.
Generate additional copies of the objects renaming objects so you can copy the object to a new name
a new key changing the copy's storage class or encrypted at rest so you can have an object that is not
encrypted and then you can change the encryption status and then you have the choices.
It's as easy as three camis to encrypt it.
Let's discuss storage classes.
The first class which is the default when you try to upload something to an S-3 bucket is the as three
standard storage This one comes with or is designed for ninety nine point nine nine availability per
year what does that mean the chances are that you will not have access to your storage storage or S3
bucket is Point 1 percent per year.
We need to look at something called your ability as well what are the chances that I may lose some of
my data or objects of my data when it is stored on S3 and in that sense.
Has done a very good job and it is a machine mission critical storage they have what they call eleven
nines data durability.
So you need to distinguish between availability and your ability.
So what does the 11:19 rating mean.
So this is the ninety nine ninety nine point nine nine nine nine nine nine nine nine nine percent per
year.
So this is the fact that they will keep your data intact without any data.
So what is my chances to lose something that will be present.
So that the chances that you will lose data in Italy last year.
So as you can see it's a very small probability that you will lose your day.
So the third thing we need to look at is getting encrypted in transit and I trust you as you are uploading
data that is the three endpoint.
What happens then actually to us or SSL is used for that.
It is designed to sustain the concurrent loss of data in facilities.
The second type is called S-3 infrequent access class or S3.
So this is for long lived less frequently access data.
So data that will not be sync as frequent and it is designed like the previous one to to sustain the
concurrent loss of data into facilities and this is suitable for backups and older data so you have
all that data and you want to move it from a story into a story I say because this is cheaper and you
can do that.
It has lower availability.
So it's designed for ninety nine point nine nine the previous one the S3 standard was 9 9 which means
higher availability and it has the same durable if you have the same access speed.
So data is available in real time for you to access quick access and high performance like S3 standard
data is also like a stream encrypted in transit and at rest.
The flipside is if you want to put your data in street I say it has to be at least for 30 days and it
is suitable for objects greater than 128 kilobytes.
The third type is S3 used reduced redundancy storage or S3 r r s This one has less redundancy and it
is designed to sustain the data loss in one facility only the previous two were two facilities not one.
And consequently if you if this is only to sustain that data loss in one facility that means you have
higher probability of losing your data availability it's the same like the S3 standard but the is exactly
much less than the S3 standard and the S3.
So when the ninety nine point nine nine which is four nines the previous ones where 11 times when we
use it use it for non-critical reproducible data.
So if you saved anything in Honoris since it has a higher probability of losing data that means the
data you store here you must be able to reproduce it.
Let's take a break now and come back.
In order to continue on as three features and see what we have to do with nature as well.