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 a serverless compute service and is not suitable for deploying a complex Java application that requires a persistent environment like Apache Tomcat. It also does not directly support MySQL connections in a manner that would maintain high availability without additional configuration.
AWS Elastic Beanstalk provides a managed service that can deploy Java applications on Apache Tomcat with built-in support for load balancing, auto-scaling, and rolling deployments. This approach meets the high availability requirement by distributing traffic and maintaining application performance during updates.
Amazon ElastiCache is a caching service and not a replacement for a relational database like MySQL. Migrating the database to ElastiCache would result in data persistence issues, as ElastiCache is designed for transient data. It does not fulfill the requirement for a MySQL database.
While launching an Amazon EC2 instance and installing MySQL is a valid approach, it does not inherently provide high availability. Using a single EC2 instance with MySQL does not ensure fault tolerance or load balancing. Additionally, managing MySQL on EC2 adds operational overhead compared to using managed services like Amazon RDS.
If I’m not mistaken, the answer is:
Deploy the application by using AWS Elastic Beanstalk. Configure a load-balanced environment and a rolling deployment policy.