EBS Volume Types / Multi attach

EBS Volumes come in 6 type

 

1. gp2 / gp3 (SSD) 
   • general purpose SSD volume which balances price and performace
2. io 1 / io2 Block Express (SSD)
   • Highest-performace SSD volume for mission-critical low tanancy or high through workloads
3. st1 (HDD) 
   1. Low cost HDD volume designed for frequently accessed, throughput- intensice workloads.
4. sc1 (HDD)
   1. Lowest cost HDD volume designed for less frequently accessed workloads

EBS volumes are characterized in Size | Throughput | IOPS (I/O Ops Per Sec)

When in doubt always consult the AWS documentaion - its good!

 

 

gp2 / gp3 (SSD)

-General purpose

• - cost effective storage, low-latency
• - System boot volumes, Virtual desktops, Dev and Test enviromnets.
• - 1 GiB ~ 16TiB
• - gp3 : baseline of 3000 IOPS and throughput of 125 MiB/s  + can increase to 16000 IOPS and 1000 Mibs (Independenyly)
• - gp2 : small gp2 volume can burst IOPS to 3000 + Size of the volume and IOPS are linked, max IOPS is 16000 + 3 IOPS per GB , means at 5335 GB we are max IOPS.

io 1 / io2 Block Express (SSD)

• - Critical business applications with sustained IOPS performance
• - Or applications that need more then 16000 IOPS
• - Great for databases workloads (sensitive to store perf and consistency)\

io1

• - max PIOS: 64000 for Nitro EC2 & 32000 for other
• - can increase PIOS independtly from storage size

io2 (4 Gib ~ 64 Tib)

• - sub - millisecond latency
• - Max PIOPS : 256,000 with IOPS:GiB ratio of 1,000:1

--

• -Supports EBS Multi-attach

st1 (HDD) 

• - Cannot be a boot volume
• - 125 GiB to 16 TiB

Throughput Optimized HDD (st1) 

• - Big Data, Data Warehouses, Log Processing
• - Max throughput 500 MiB/s - max IOPS 500

Cold HDD (sc1)

• - For data that is infrequently accessed
• - when lowest cost is important
• - Max throughput 250 MiB/s ~ max 250 IOPS

 

EBS Multi-Attach - io1/io2 family

- Attach the same EBS volume to multiple EC2 in the same AZ

- each instance has full read & write permissions to the high-performance volume

 

Use case :

- Achiece higher application availability in clustered Linux applications ( ex : Teradata )

- Applications must manage concurret write operations.

 

Up to 16 EC2 instances at a time

Must use a file system that's cluster-aware ( not XFS, EXT4 , etc...)