In AWS, there are so many storage services to choose from, it's difficult for a novice to figure out which one to choose. Because as a cloud architect, you don't just need to make your product usable, but consider Resilient, Performance, Secure, Cost optimized, and finally achieve an operationally excellent system. These are also several core points of the AWS SA associate exam.

This article focuses on the three storage services of AWS.

AWS S3 (simple storage service)

S3 is an object storage service that can store anything, files, videos, pictures, and it will be stored in a Bucket, which is A storage method without hierarchy, you can imagine that there is no relationship between data, it is a flat structure. Each file will have a Header and storage content of 0-5TB in size when it is created. Each of these files will then have a unique ID associated with it. This ID will be able to access the file by any web application. For example, a VM virtual machine in your AWS can call files stored in S3. So it is suitable for storing files that need to be accessed frequently.

S3 also has a very useful function, that is, it can host a static website (that is, a pure display website that does not require background database login and various operations). We will introduce it later.

S3 is a scalable, the storage capacity can be expanded or decreased, and payment is made according to the actual amount used. The S3 is known for its 11 nines and ease of use. Its stability is a horrible 99.99%, so basically your data is unlikely to be lost in S3.

One sentence summary: AWS S3 is a particularly reliable, scalable data storage service that is easily accessible to the outside world. To store the files you want to use frequently, use S3!

EBS (elastic block storage)

EBS is also a storage service specially used to allow you to run your virtual machine. Just like you install a windows operating system, install it on the C drive, or install a virtual machine on the D drive. All the EC2 you use on AWS will run on EBS. But keep in mind that the HDD storage in it cannot be used as OS storage.

Since it is the storage of the running system, it must require access speed, right? So for EBS, the main things to remember are the following:

  • EBS cannot be used as a separate storage, it is always created at the same time as EC2.
  • The size of the EBS at the time of creation cannot be changed later. After all, a system is installed (but the capacity can be increased by creating a new EBS and then attaching it to EC2) EC2 needs to pause to update EBS .
  • EBS has three storage methods, mainly related to performance and price.
    • General purpose SSD storage

    This is the most important way to choose, depending on the parameters and your needs, it can usually meet all ordinary systems practical needs.

    • IOPS-optimized SSD storage

    This IOPS (input/output operation per second) is read-write optimized SSD storage. If your system needs a lot of Read and write operations, this will be your choice. It depends on the parameters and your needs.

    • Disk (magnetic) storage is actually HDD

    The last one is the relatively cheap HDD disk storage, the price is cheap, it is more suitable for storing those sequence data (squential data), such as log data, big data or something, it is very cost-effective. Its I/O read and write speed is also good at 500MB/s. It is also divided into two types, one is st1, which has fast read and write speed and is cheap. There is also a cheaper, sc1, with relatively slower read and write speeds.

    Various choices of EBS

    EFS (elastic file system)

    EFS, don't look at its name as file system, in fact, it is mainly used to allow you to run some IO storage requirements relatively high App. What is the difference? S3 is used to store files, and EBS is mainly used to run virtual machines and store some system files, or store large data, etc., which requires a lot of IO access. It seems that EBS can also be used to run applications. Yes, you can run an application in your system disk, but if your application suddenly needs to be scaled up, for example, your user visits suddenly increase from 1,000 to 100,000. One, remember that EBS cannot automatically scale up. So the app should not run in your EBS, this is the role of EFS.

    EFS can automatically scale up or down, so you never have to worry about running out of resources. And there is no need to worry about wasting resources. When demand becomes low, EFS automatically scales down, and you only need to pay for the part of the storage you use.

    An EFS can be used by multiple resources at the same time and is a shared system. Therefore, EFS is very suitable for running some shared servers, big data operations, and other applications that require flexible scale up and down storage resources.


    The process of becoming a networker isn’t considered for the faint-hearted. It requires lots of hard work and nice and trustworthy AWS SAP-C01 Dumps, like that offered at the ITCertDumps, to clear this grueling exam.


Leave a comment