A rehosted public-health epidemiology database will land on Amazon EC2 with Amazon EBS. On-premises SAN metrics show sustained 12,000 IOPS and 250 MiB/s during month-end reporting. How should architects size the block storage?
Select an answer to reveal the explanation.
Short Explanation
The SAN already told you how hard the database hits the floor. Bring those IOPS and throughput numbers to EBS instead of picking a tiny default and hoping. S3 and instance store don't magically become a measured database disk.
Full Explanation
For rehosted databases, Amazon EBS must be selected and sized from measured on-premises storage baselines for IOPS, throughput, capacity, and latency. Map those numbers to volume types such as gp3 or io2 with explicit performance settings rather than a default disk. Assuming AWS auto-matches SAN behavior, using ephemeral instance store as the only data volume, or placing database files on S3 for POSIX IOPS produces an undersized or invalid target architecture.