AWS EBS Volume types
- AWS supports the following EBS Volume types
- General purpose: These provide balanced speed
- Provisioned IOPS: Designed for larger iops and low latency
- Hard disk Drives: Designed for low cost storage
- For a root disk (disk with os) we can use only ssd disk types
- For additional disks we can select all the disk types
-
Decision tree for choosing ebs volume type
-
Workload patterns:
- General server (web, API, microservice)
- Need > 3000 IOPS:
- yes => gp3 with provisioned through put (upto 16000 IOPS)
- no => gp3
- Need > 3000 IOPS:
- Database server (mysql, postgres, oracle, mongo)
- need > 16000 IOPS
- no: gp3
- yes: io2 (Provisioned IOPS)
- need > 16000 IOPS
- Large sequential througput ( ETL, data lakes, logs, Hadoop)
- what is Access frequency
- Frequent
- Throughput optimized HDD
- Infrequent
- Cold Storage (Cold HDD)
- Frequent
- what is Access frequency
- Cold rarerly accessed
- General server (web, API, microservice)
-
Lets create a linux instance with an option not to delete volume when ec2 is deleted
- 10 gb gp3 as root ebs volumes
- 10 gb gp3 as additional ebs volumes
- Now create one more ec2 instance and try detaching the additonal volume and attaching this volume to new instance
- To do this both ec2 instances should be running from same zone
- Watch classroom video
- How can i get if not the disk directly any way to get the contents of disk to an ec2 instance running on differnt zone in same region
- Now if the ec2 is in diffent region:
- Create a snapshot in source
- copy the snapshot to a differnt region
- Using this snapshot create a new disk (EBS Volume)
