What should the solutions architect do to meet these requirements?
Deploy the application in AWS Lambda. Configure an Amazon API Gateway API to connect with the Lambda functions.
Deploy the application by using AWS Elastic Beanstalk. Configure a load-balanced environment and a rolling deployment policy.
Migrate the database to Amazon ElastiCache. Configure the ElastiCache security group to allow access from the application.
Launch an Amazon EC2 instance. Install a MySQL server on the EC2 instance. Configure the application on the server. Create an AMI. Use the AMI to create a launch template with an Auto Scaling group.
Explanations:
AWS Lambda is designed for serverless applications and is not suitable for deploying a complex Java application with Apache Tomcat. Additionally, it does not provide the high availability requirements directly as a web server environment would.
AWS Elastic Beanstalk supports Java applications and provides a platform for deploying applications on Apache Tomcat. It automatically handles load balancing and scaling, which meets the high availability requirement, and allows for rolling deployments, ensuring minimal downtime during updates.
Amazon ElastiCache is an in-memory caching service and not a suitable replacement for a MySQL database. Migrating the database to ElastiCache would result in data persistence issues and would not satisfy the requirement for a MySQL database for the Java application.
While launching an EC2 instance and installing MySQL is feasible, it lacks built-in high availability. This solution does not automatically handle scaling or load balancing, making it less ideal compared to using a managed service like Elastic Beanstalk. Additionally, creating an AMI and using it in an Auto Scaling group would require more manual setup and management.
I evaluate that the answer is:
Deploy the application by using AWS Elastic Beanstalk. Configure a load-balanced environment and a rolling deployment policy.