[MUSIC] In this video, we are going to look at a couple of important points about object storage related features. Number one is bucket names. And number two is the storage tiers that you can choose for buckets and objects. You need to remember that when you use the object storage UI and create a bucket, let me go back to London region. When we create a bucket here, you created in a particular compartment as with every other resource and you are creating it in a region. Remember, object storage is a regional service, it is automatically replicated within the region across all Eddie's when you create a bucket there is a default name that is given, which is dependent on the year, month and day with some random number added. And if you want to create your own bucket name for example, demobucket 1 is the name I'm giving. What you need to realize is, bucket naming for a Tenant has to be Unique in a Region even across all Compartments. Which means if in this tenancy, in London region, even in any other compartment, if there is a bucket named demobucke1 nobody else can create one within the same tenancy. So reason for that is the URL includes the bucket name, which means, if there is a URL for a given bucket with a particular name, the region specific URLs cannot have two different buckets with the same name within a given region. And there is no compartment structure for the URL. We will see that when we upload objects. But before that, we also need to understand about the storage tiers. As you can see here there are two storage tiers available as the default for a bucket. What you need to understand is from a storage tiering perspective In object storage, you actually have three storage tiers, standard, infrequent access, and archive. There are three tiers that are available for a tenant to use. When you create a bucket, you choose which is the default tier for the bucket and the choices you can use is either you can set it as standard or you can set it as archive, only these two can be used. So first of all we need to understand what is the difference between the storage to tiers. Every bucket that is created has all three tiers with the net. So every bucket actually has all three tiers available. For example, if you create a bucket and of whichever default tier whether you use standard or archive, you need to realize that every bucket has all the three tiers. So if I were to call this as the standard tier within the bucket ,this as the infrequent tier and this as the archived here within the same bucket. If you set a bucket to have its default tiers standard tier, then when you upload objects into this bucket, it will get uploaded into the standard tier. On the other hand, if you created a bucket with its default storage as archived tier, then by default when you upload objects into this bucket, it will go into the archived tier. So what is the difference? The fundamental difference is that, the cost and access limitations are available. But as a result of this you may have within the same bucket objects which are in any of these tiers because after you upload objects into a bucket, you can move them between the storage tiers which we will see in a demonstration that is coming up. So how are these three tiers different to each other? Standard tier objects are readily accessible. Infrequent tiers are fast to access but rather I would say is not as fast as standard tier, but still readily accessible whereas archive objects are not readily accessible. You need to restore to STD tier to be able to access it but from a cost perspective, it costs only 1/10th of STD tier, which means if you have objects in the standard tier of a bucket, you can readily download them. But if you have objects in archive tier, you need to make a request to restore the object to standard tier and only then you will be able to download them. And when you make a request to restore, you can tell for how long you want to copy of the object to be in standard. Let's say you say two days, then for the two days duration, you are charged for both archive and standard tiers for the size of the object that you keep. When it comes to infrequent access, there is a limitation that you need a minimum of 30 day billing for any object you put in there, but there is no requirement to restore it. It is readily accessible and any objects you put in archive tier, there is a minimum of 90 day billing that happens which means even if you delete the object, within 90 days, the billing will happen for the amount of storage consumed by the object for 90 days. Thus, if this is the way the storage tiers work, how do you use buckets tiers. That's pretty simple. Any file that you feel is going to be frequently used, you keep it in the STD tier or in a bucket. Whereas or a period of time you might have your own archiving requirements and whenever you feel that certain objects have to be still kept, but you are not going to access them, you can archive the object into ARC tier. And in the standard tier, you can move objects between standard and infrequent access. The idea about infrequent access is it costs lesser than standard tier at the same time, you can access it directly immediately unlike the case of archive storage. Let's quickly have a look at how this works within object storage. Now I am going to create a demo bucket here and I will call it as default storage standard. And let me also create another bucket here as demo bucket archive. And this is bucket number two. I will choose the archive tier and put it there. Let me upload some files into both these buckets. When you upload a file in a bucket which is standard tier, you have the ability to choose, do you want to put it in standard tier, infrequent tier, or archive tier or you have the ability to choose. Let's say I uploaded the standard tier, a couple of files and let me add one more file also to standard tier. And let me upload a file to the infrequent access within the same bucket. And let's say it will be this file. And let's say I add one more file, but this time I will put it into archived tier within the same bucket. And let's say it is this particular file. I have uploaded multiple files within the same bucket in different tiers. If I want to access them, I can download any object which is in standard tier and I will be able to see the file as such, over here, I'm just opening the file here. That is the file that got downloaded. Same way infrequent access also I can download, right whereas archive, the download option is not enabled. If you want to download it, you need to make a request to restore and you can tell for how long the file should be available in standard tier also. Because what happens when you restore is the file and archive tier is still there. A copy of it is put in the standard tier for you to download for so much time and restore the object will start the restore. It can take a minimum about 4 hours for any object to be restored. And depending on the file size, the total time taken can vary. But what you need to remember is once it is restored, you will get the download option enabled, whereas, when you work with an archive bucket when you upload files, you don't get to choose the storage tier, you will by default uploaded only to the archived tier. And once the file is uploaded it is an archived tier, if required to access it, you can restore it and give a duration for how long it should be available for download. And once it is restored, it will be accessible. With that, we get an idea about the bucket naming convention and the storage tiers that are available. Now we had a restriction about the bucket naming convention to be unique within a region for a tenancy. The reason for that is if you look into the object details, we see the object URL. And if I bring in our text editor for us to have a look at this URL in a larger font, we see that the URL to access an object is having a structure, which is the region in which you have created the bucket has a region specific URL. So object storage.uk.oracleloud.com is a common URL For any object in London, the tenancy name bucket name followed by the object name there is no compartment structure here. That is why in a given region for a given tenant bucket names would have to be unique. With that, we come to our conclusion on these two topics wherein we looked at how you need to take care of bucket names and the comparison of storage tiers that are available in the form of standard tier, archive storage tier and infrequent access tier. In the next few videos we will go into little more details about other options which you will explore in the remaining videos.
