This is what I have found about it For usage with EC2 instances, Amazon Elastic Block Store (Amazon EBS) provides block-level storage volumes. EBS volumes operate as unformatted, raw block devices. These volumes can be mounted as devices on your instances. EBS volumes attached to an instance are exposed as storage volumes that last indefinitely regardless of the instance's lifespan. You can utilize these volumes to establish a file system or use them in any way that a block device would be used (such as a hard drive). A volume associated with an instance can have its settings changed dynamically. In a given Availability Zone, you create an EBS volume and then attach it to an instance in that same Availability Zone. You can create a snapshot of a volume and restore it to a new volume anywhere in that Region to make it available outside of the Availability Zone. It's easier to use several AWS Regions for geographical growth, data centre transfer, and disaster recovery by copying snapshots to other Regions and then restoring them to new volumes there. The following volume types are available on Amazon EBS: General Purpose SSD, Provisioned IOPS SSD, Throughput Optimized HDD, and Cold HDD. See EBS volume types for further information. The performance and use cases for each volume type are summarised below. General Intentions For a wide range of transactional applications, SSD volumes (gp2 and gp3) strike a balance between price and performance. These volumes are appropriate for boot volumes, medium-size single-instance databases, and development and test environments, among other applications. I/O-intensive workloads that are sensitive to storage performance and consistency will benefit from provisioned IOPS SSD volumes (io1 and io2). When you build the volume, you can set an IOPS rate. This allows you to expand to tens of thousands of IOPS per instance in a predictable manner. In addition, io2 volumes have the best volume durability. And you can also check out this blog for more information: AWS Classes In Pune