Amazon S3 – Cloud Object Storage
Cloud Object Storage
Cloud Object storage (also known as object-based storage) is a computer data storage architecture that manages data as objects. In our last post we have discussed the Block Storage and today we are going to focus on one of the greatest services of AWS i.e. S3 which is based on object storage.
We know that EBS is one of the services for storage in AWS. In our last post, we learned how to make our instance storage persistent. So, whenever the OS is stopped or terminated we don’t lose our data.
Today, we are going to focus on some other parameters like what if the data center where we created our volume get crashed? Although the chances are very less & you know that we have 3 Availability zones in our Mumbai. Let’s imagine all are not working. They got corrupted. As you might know about the term corruption, Hardware is a physical thing that might get corrupted. You never want to lose your data. Because when you implement something the most important thing in your project is the data of your client. Now due to any issue, the volume might get corrupted and you will lose the data.
You might not able to figure the importance of data but imagine the data is of any bank. The data is so crucial and at this time you can’t take the risk even the loss probability is 1%.
What you can do? You can have multiple backups. You can create multiple backups and creation is not a big deal, but managing the multiple backups is a big deal. If there any update in your data you have to update that in each and every backup volume. Technically in today’s world, it is not a good thing. It’s definitely frustrating work.
To resolve this issue AWS has a cloud object storage service named S3(Simple Storage Service). In S3 you have to just put your data and your backup work will manage by the AWS itself. In S3, AWS gives 99.99999% of assurance that your data will be secured & can’t be loosed anyhow. S3 has two best qualities:
How Object Storage is better than Block Storage
We know about the EBS(Elastic Block Storage) service that is good for launching the instances but in the case of storing data and providing high availability S3 is the service that leads. There are tonnes of reasons that make Amazon S3 the most useful service of AWS.
- At EBS you guys know we have a max size 16 TiB but at S3, Amazon gives you infinite storage. You can store as much as data you want.
[[Note: 5 GiB of space is free in S3]]
- Let’s imagine you have two different OS named A & B. If EBS is connected to A can’t connect with B at the same time. While in S3 you can connect A & B or as many OS as you can. You don’t have to copy the data again and again to the different EBS storage.
- If you will go through my EBS post you will come to know that there is a restriction that if the OS is in 1a availability zone, the EBS only inside the 1a AZ can connect to the OS. But S3 is a global service hence there is no restriction of AZ, you can actually connect to any os of any AZ.
- In EBS after creating the volume, you have to make a partition then mount, and then only data can be stored while in S3 there is no need for that. It is object storage, as we create the bucket in S3 we can put our data inside it.
- In Amazon S3 you find a unique bucket URL and that URL can be used to refer to your data.
- In S3, AWS itself creates multiple backups and we don’t have to worry much about the backups and new updates of data in that backup as we have to worry in EBS.
- For the files like images and videos, S3 is very beneficial. These files are large in size and hence can easily be managed by the S3.
Limitations of S3:
In spite of some great use cases of AWS Simple Storage Service, there are some limitation in S3 and some of them are as follows
- In object storage, we can’t make the partitions and that is the reason we can’t install os on S3. To install the os we still need an EBS volume.
To know more about the different services of AWS stay tuned with BrighterBees.
You can connect with the author on