What is the MOST operationally efficient solution that meets these requirements?
Deploy the application to AWS Elastic Beanstalk. Migrate the database to an Amazon RDS Multi-AZ DB instance.
Create an Amazon Machine Image (AMI) that contains the application code. Create an Auto Scaling group that is based on the AMI. Integrate the Auto Scaling group with an Application Load Balancer for the web servers. Migrate the database to a MySQL instance that runs on an Amazon EC2 instance.
Deploy the application to AWS Elastic Beanstalk. Migrate the database to a MySQL instance that runs on an Amazon EC2 instance.
Create an Amazon Machine Image (AMI) that contains the application code. Create an Auto Scaling group that is based on the AMI. Integrate the Auto Scaling group with an Application Load Balancer for the web servers. Migrate the database to an Amazon RDS Multi-AZ DB instance.
Explanations:
AWS Elastic Beanstalk automatically manages the application, including scaling, load balancing, and version management. Migrating the database to Amazon RDS Multi-AZ ensures high availability and automated backups, which reduces operational overhead.
Using EC2 instances for both the web servers and the MySQL database increases operational complexity. Managing EC2 instances and backups for MySQL is more cumbersome than using Amazon RDS, which offers automated backups and maintenance.
Using Amazon EC2 for both the web servers and the database increases complexity. Elastic Beanstalk simplifies deployment, but using EC2 for the database lacks the operational efficiency of Amazon RDS, which offers better scaling, backup, and maintenance features.
While using Amazon RDS Multi-AZ for the database is a good choice for high availability, managing EC2 instances for the web servers through AMIs and Auto Scaling is less efficient than using Elastic Beanstalk. Beanstalk abstracts away much of the management overhead and simplifies deployments.