A global web application runs on a single EC2 instance and performs read‑intensive operations on an Amazon RDS for MySQL database. During peak load the EC2 instance becomes unresponsive and needs manual restarts. You must improve reliability with minimal development effort. Which solution best meets this requirement?

The correct solution addresses both the application and database bottlenecks with minimal development effort. Hosting the application on EC2 instances in an Auto Scaling group behind an Elastic Load Balancer (ELB) provides high availability and automatically scales the application to handle peak loads, preventing unresponsiveness. Migrating the database to Amazon Aurora and using Aurora Replicas offloads read-intensive operations, improving database performance and reliability. Incorrect options: Creating a CloudFront distribution would cache static content but wouldn't solve the EC2 instance's unresponsiveness under load for dynamic content. Using the Multi-AZ standby for reads is not its intended purpose and can lead to performance issues and increased costs. AWS Global Accelerator improves global performance but doesn't resolve the underlying EC2 instance's scaling or database read issues. Refactoring to Lambda functions is a significant development effort, which the question explicitly seeks to minimize. While creating read replicas is good, it doesn't address the application's single point of failure.