An ecommerce company runs a PostgreSQL database on premises using high-IOPS Amazon Elastic Block Store (Amazon EBS) block storage. Daily peak I/O does not exceed 15,000 IOPS. The company plans to migrate to Amazon RDS for PostgreSQL and needs to provision disk IOPS independently of storage capacity. Which solution is the MOST cost-effective?

The MOST cost-effective solution is to configure the General Purpose SSD (gp3) EBS volume storage type and provision 15,000 IOPS. gp3 volumes allow you to provision IOPS and throughput independently of storage capacity, making them ideal for workloads requiring specific performance levels without over-provisioning storage. gp3 offers a baseline of 3,000 IOPS and 125 MiB/s throughput for free, with additional IOPS and throughput provisioned at a lower cost than io1. Configuring gp2 would be less cost-effective because gp2 IOPS scale with storage size, meaning you might have to provision more storage than needed to achieve 15,000 IOPS. Configuring io1 would also be less cost-effective as io1 is designed for the most demanding, mission-critical workloads and is significantly more expensive per provisioned IOPS than gp3. EBS magnetic volumes are legacy and offer very low performance, making them unsuitable for a high-IOPS database.