A county document-management database on Amazon EC2 needs sustained…

Question

A county document-management database on Amazon EC2 needs sustained IOPS and throughput for peak scanning days without overpaying for idle capacity overnight. Which block-storage design best meets performance and cost goals?

Accepted Answer

Select an EBS volume type that matches the IOPS/throughput profile (for example gp3 with provisioned IOPS/throughput or io2 where required), baseline from metrics, and avoid oversized always-on Provisioned IOPS beyond measured need. — Think of EBS like choosing the right truck for scanning day—match volume type and provisioned IOPS/throughput to real metrics, not folklore. Oversizing io2 forever or parking an OLTP DB on cold HDD or S3 object GETs is how budgets and SLAs both get hurt.

Answer

Use only instance store ephemeral disks so all documents vanish when the instance stops, removing EBS cost entirely.

Answer

Attach a single cold HDD (sc1) volume for the OLTP document database because throughput is always cheaper than IOPS.

Answer

Place the database data files on S3 Standard accessed over the internet from the EC2 host for every transaction.

A county document-management database on Amazon EC2 needs sustained IOPS and throughput for peak scanning days without overpaying for idle capacity overnight. Which block-storage design best meets performance and cost goals?

Short Explanation

Full Explanation