A company runs a three‑tier web app on‑premises: Apache frontend, monolithic Java middle tier, and PostgreSQL storage. A recent promotion overloaded all tiers, the app crashed, and the database hit read capacity limits. Several promotions are planned. You must design a migration to AWS that maximizes scalability and minimizes operational effort. Which three steps accomplish this? (Choose three.)

Serving static assets from Amazon S3 and distributing them via CloudFront offloads the web servers and improves performance, maximizing scalability and minimizing operational effort for the frontend. Rehosting the Java application on AWS Elastic Beanstalk with auto scaling provides automatic scaling and managed infrastructure, addressing the middle-tier overload with minimal operational overhead. Migrating PostgreSQL to Amazon Aurora PostgreSQL using AWS DMS and enabling Aurora Auto Scaling for read replicas offers a highly scalable, high-performance, and fully managed database solution that automatically handles read capacity limits. Rehosting the Apache frontend on EC2 with EFS for static assets adds operational overhead and does not fully leverage AWS managed services for static content delivery. Refactoring the Java application to Fargate is a good option for scalability but involves more refactoring than simply rehosting on Elastic Beanstalk, which is a valid first step for minimizing operational effort. Rehosting PostgreSQL on an EC2 instance does not provide the managed scalability and high availability of Aurora.