A company operates a web-based geographic information system (GIS) on AWS. The application runs on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB). The instances query an Amazon RDS for PostgreSQL database configured with Multi-AZ for high availability.
During predictable daily peak hours, the application experiences significant performance degradation. CloudWatch metrics indicate that the RDS primary instance CPU utilization consistently exceeds 90%. Additionally, the ALB drops multiple connections due to a sudden, massive surge in user traffic at the exact start of peak hours, and the EC2 instances experience high write latency on their attached Amazon EBS gp3 volumes.
Which combination of actions should a solutions architect take to optimize the compute and storage performance of the system?
- Create an Amazon RDS Read Replica and configure the application to route read-only queries to the read replica endpoint. Request AWS Support to pre-warm the Application Load Balancer before the peak hours start. Increase the provisioned IOPS and throughput of the existing EBS gp3 volumes.Cevap
- BConfigure the application to route read-only queries to the standby instance of the RDS Multi-AZ deployment. Request AWS Support to pre-warm the Application Load Balancer before the peak hours start. Replace the EBS gp3 volumes with gp2 volumes and increase the volume size to obtain higher baseline performance.
- CCreate an Amazon RDS Read Replica and configure the application to route read-only queries to the read replica endpoint. Rely on the Application Load Balancer's automatic scaling and decrease the scaling cooldown period in the EC2 Auto Scaling group to handle the traffic surge. Migrate the EBS gp3 volumes to Provisioned IOPS SSD (io2) volumes to reduce cost while increasing throughput.
- DConfigure the application to route read-only queries to the standby instance of the RDS Multi-AZ deployment. Deploy Amazon ElastiCache for Memcached to cache database queries and enable multi-AZ replication to ensure high availability of the cache. Migrate the EBS gp3 volumes to Cold HDD (sc1) volumes to improve write latency.