A document-management database volume was provisioned as io2 during a peak project. CloudWatch now shows IOPS and throughput well below io2 provisioning for sustained periods. Which cost-conscious architecture choice should the team make?
Select an answer to reveal the explanation.
Short Explanation
io2 was the racing slick for a peak that ended. If metrics say you’re cruising, price out gp3 against real IOPS needs and move if it fits. Striping Cold HDD under a document DB is how you invent a new outage.
Full Explanation
Cost-conscious storage design revisits volume type when telemetry shows provisioned io2 capacity is unused. gp3 often meets moderate IOPS/throughput needs at lower cost; architects should compare requirements and migrate when justified. io2 can be modified/migrated in supported patterns; sc1 is inappropriate for transactional document databases; encryption is not a substitute for volume-type cost analysis.