An application hosted on Amazon EC2 instances uses General Purpose SSD (gp2) EBS volumes. During a daily batch reporting process, write operations experience significant latency. CloudWatch metrics indicate that the volumes are consistently hitting their baseline IOPS limit and exhausting their burst balance. Which of the following is the most cost-effective action to resolve the storage performance bottleneck with the least administrative effort?
- ARequest a pre-warming of the Application Load Balancer (ALB) from AWS Support before the daily batch process begins to distribute the incoming request spikes.
- BEnable Amazon RDS Multi-AZ replication for the database storage layer to automatically scale the write transactions across standby instances.
- Modify the EBS volumes from gp2 to gp3 and provision the required IOPS and throughput independently of the volume size.Cevap
- DPurchase EC2 Instance Savings Plans to offset the high costs of upgrading the baseline storage performance of the EC2 instance volumes.
Cevap
Modify the EBS volumes from gp2 to gp3 and provision the required IOPS and throughput independently of the volume size.
Transitioning EBS volumes from gp2 to gp3 is the most cost-effective and low-effort way to solve this bottleneck. In gp2, baseline IOPS are tied to the volume size ( up to a maximum of ), whereas gp3 volumes offer a constant baseline of and throughput for free and allow scaling performance parameters independently without increasing the underlying storage volume size.
Adım Adım Çözüm
Anahtar Kavram
EBS storage performance optimization by transitioning from gp2 to gp3 to provision performance parameters independently of size.