A gaming company operates a multiplayer online game where player session state and matchmaking queues are managed by an application running on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB). The backend database is an Amazon RDS for PostgreSQL DB instance configured in a Multi-AZ deployment. During daily peak hours, players experience severe latency spikes and disconnected sessions. Monitoring data shows that the RDS primary DB instance has 90% CPU utilization and read IOPS throttling while the standby DB instance has 0% CPU utilization. Additionally, the EC2 instances experience a sudden CPU utilization spike of 98% for the first 5 minutes of the peak window, causing the ALB to report 502 Bad Gateway errors before the Auto Scaling group can successfully launch and bootstrap new instances. Which combination of actions should a Solutions Architect recommend to resolve the database and compute performance bottlenecks?
- ADeploy Amazon RDS Read Replicas to scale read queries, and request AWS Support to pre-warm the Application Load Balancer to handle the initial traffic spikes.
- BRoute player session read queries to the passive standby DB instance in the Multi-AZ deployment, and configure a warm pool for the Auto Scaling group.
- Deploy Amazon RDS Read Replicas to offload the read-heavy matchmaking queries from the primary DB instance, and configure the Auto Scaling group with a warm pool and step scaling policies.Cevap
- DIncrease the Auto Scaling group default cooldown period to prevent rapid scaling actions, and upgrade the RDS instance to a larger instance class with Multi-AZ enabled.