3 hours 27 minutes
In this video
we will enable version ing on our bucket.
We will walk through a version ing example.
In our last video,
we created our first s three bucket.
We uploaded an object to our bucket
and we made our object accessible from the Internet.
In this video we will enable version ing on our bucket.
Then we will upload new objects to our bucket to demonstrate version ing.
as a review,
what does very thing do for us?
Version ing enables us to maintain multiple versions of the same object within our s three bucket.
Essentially, a new version could be something as simple as an update to an existing file.
This concept is better explained by an example.
So let's walk through a demonstration of version ing.
So from the console, let's type s three to get back into our bucket and cyber very rocks.
Let's click on our bucket,
then click properties.
Then we choose version ing
and then enable version ing.
Finally, we click save
version. Ng is now enabled on our bucket.
Now let's upload a new object to our bucket.
I have already created a test file called version example dot text
When we click on the file, we can see its properties
Notice the file size is about 71 bites.
And here is the girl that is assigned.
If we click show,
this is where we can see the different versions of objects within our bucket.
Notice the version I D. That A. W s has provided for this file.
It shows us that this is the latest version.
Also, you can see that our original object has a version I d off. No,
this is because we uploaded this object to our bucket
prior to enabling version ing.
let's click back on our new object to make it public, so that can show you the file contents.
If you recall from our last lesson,
files uploaded to a bucket are private by default.
So here is our example File
is just a simple text document that says Greetings one and all.
Cyber Harry is one of the coolest sites ever.
Now let's say that we want to add an update to this file,
but keep the same file name.
Here's how version ING helps us.
First, let's update our test file,
been safe and uploaded.
So now we have two versions of the same file
A W s indicates to us which is the latest version
and has assigned a new version i d.
The latest version is the file that are Earl will point to.
But when we click the Earl notice that we get an XML air,
remember, we have to make our objects public.
A W s tells us that it was a success.
Now we click our object again
and we could see the updated version of our file.
So what if we wanted to get rid of the old versions of our file?
How would we accomplish that?
We just click on the old version of the file
A. W s warns us that this is a permanent action.
So we then
just click delete.
And now the old object is going.
This is actually a good use case for combining M f a with version ing
that way on Lee. Someone duly authorized would be able to delete objects from our buckets
for more information,
visit the AWS documentation
and perform a search for managing objects
in a version ing enabled bucket
How does version ing assist us
version ING enables us to maintain multiple versions of the same object within Rs three bucket.
How do we enable bucket version ing
from the console? We click on our bucket,
then click properties and then select enable version.
Once I upload a new version of my file, will others be able to see it on the Internet?
When we upload a new version of an object, we will need to click make public
to enable it to be visible on the Internet.
In this video,
we enabled version ing on our bucket,
and we walked through a version ing example.