A data engineering team runs a nightly job on EC2 that reads multi-terabyte log files from start to finish on an attached EBS volume, computes aggregates, and writes a small summary. The job performs almost no random I/O, but it must finish inside its nightly window, so the volume has to stream data quickly every night. Which volume type meets the requirement MOST cost-effectively?
Choose one.
HDD volumes sell throughput and SSD volumes sell IOPS; for large sequential scans, st1 delivers the required throughput at HDD prices.
The access pattern is large and sequential with almost no random I/O, which is what st1 is built for: high sequential throughput at HDD prices. gp3 and io2 would both work, but they charge SSD prices for random-I/O capability the job never uses, which the cost qualifier punishes. sc1 is the trap in the other direction: it is cheaper per gigabyte but is designed for cold, rarely read data and delivers lower throughput, so a nightly job with a deadline can miss its window.
- Identify the access pattern: large sequential reads, minimal random I/O.
- Map pattern to media: sequential throughput favors HDD volumes over SSD on price.
- Check the access frequency: nightly, throughput-sensitive scans are regular work, ruling out cold-tier sc1.
- Confirm st1 meets the throughput requirement at lower cost than gp3 or io2.
Exam tip: Sequential big-data scans resolve to st1 — SSDs overpay for unused IOPS, and sc1 undershoots on regularly accessed data.
High-Performing Storage: S3 vs EBS vs EFS, Volume Types, and Hybrid Options — the lesson that teaches this.