Which solution will meet these requirements?
Create an Amazon S3 bucket. Enable static web hosting on the S3 bucket. Upload the static content to the S3 bucket. Use AWS Lambda to process all dynamic content.
Deploy the web application to an AWS Elastic Beanstalk environment. Use URL swapping to switch between multiple Elastic Beanstalk environments for feature testing.
Deploy the web application to Amazon EC2 instances that are configured with Java and PHP. Use Auto Scaling groups and an Application Load Balancer to manage the website’s availability.
Containerize the web application. Deploy the web application to Amazon EC2 instances. Use the AWS Load Balancer Controller to dynamically route traffic between containers that contain the new site features for testing.
Explanations:
This solution is suitable for static websites but not for dynamic content requiring Java and PHP processing. AWS Lambda can handle some dynamic content, but it’s not a complete replacement for a full web application stack.
AWS Elastic Beanstalk is a managed service that simplifies deployment and scaling of web applications. URL swapping allows for easy testing of new features by routing traffic between different environments with minimal operational overhead.
While deploying on EC2 with Auto Scaling and an Application Load Balancer offers high availability, it requires more operational management, such as server maintenance and scaling configuration, which contradicts the requirement for minimal operational overhead.
Containerizing the application is a valid approach, but managing EC2 instances for this purpose involves more complexity and operational overhead than necessary. Using AWS services like ECS or EKS would be more appropriate for easier management.
From my point of view, the answer is:
Deploy the web application to an AWS Elastic Beanstalk environment. Use URL swapping to switch between multiple Elastic Beanstalk environments for feature testing.