An EC2 application needs SSD block storage.
Set capacity, IOPS, and throughput independently without buying excess disk capacity.
Which volume is most appropriate?
Use an EBS gp3 volume so capacity, IOPS, and throughput can be adjusted independently for a general-purpose SSD workload.
Detailed explanation
gp2 performance scales with capacity and may require unwanted extra storage.
gp2 performance scales with capacity and may require unwanted extra storage.
gp3 allows IOPS and throughput to be configured independently of capacity for common SSD workloads.
gp3 allows IOPS and throughput to be configured independently of capacity for common SSD workloads.
S3 is object storage and cannot be attached as a block device.
S3 is object storage and cannot be attached as a block device.
Instance store does not provide persistence across an instance stop or termination.
Instance store does not provide persistence across an instance stop or termination.
Check official documentation
Compare the following points with the official documentation.
Amazon EBS gp3とgp2の公式比較を確認する。
What to confirm
容量と性能の独立設定をgp3へ対応付けられる。
Key points
- EBS gp3
- IOPS
- Throughput
Notes
- Environment: AWS公式EBSドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Capacity and performance
A volume can have enough capacity while needing different IOPS or throughput settings.
Persistence
EBS is persistent block storage, unlike instance store data that is tied to the instance lifecycle.