Which solution will meet these requirements with the LEAST operational overhead?
Use AWS Application Migration Service to migrate the application server to Amazon EC2 instances. Create an Auto Scaling group for the EC2 instances. Use an Application Load Balancer to distribute the requests. Modify the application to use Amazon S3 to persist the files. Use Amazon Cognito to authenticate users.
Use AWS Application Migration Service to migrate the application server to Amazon EC2 instances. Create an Auto Scaling group for the EC2 instances. Use an Application Load Balancer to distribute the requests. Set up AWS IAM Identity Center (AWS Single Sign-On) to give users the ability to sign in to the application. Modify the application to use Amazon S3 to persist the files.
Create a static website for uploads of media files. Store the static assets in Amazon S3. Use AWS AppSync to create an API. Use AWS Lambda resolvers to upload the media files to Amazon S3. Use Amazon Cognito to authenticate users.
Use AWS Amplify to create a static website for uploads of media files. Use Amplify Hosting to serve the website through Amazon CloudFront. Use Amazon S3 to store the uploaded media files. Use Amazon Cognito to authenticate users.
Explanations:
Migrating the application server to EC2 instances with Auto Scaling may not reduce operational overhead significantly. While Amazon S3 can replace the file server for persistence, the migration of the application server still requires management of EC2 instances, which adds complexity. Amazon Cognito can handle authentication, but this solution involves more infrastructure management.
Similar to option A, migrating to EC2 instances with Auto Scaling introduces additional management overhead. While AWS IAM Identity Center (AWS Single Sign-On) is a good option for user authentication, it doesn’t solve the core problem of reducing operational overhead for both scaling and file management.
While AWS AppSync with Lambda can be used to create a serverless solution, it introduces additional complexity compared to a more integrated service like AWS Amplify. Managing resolvers, API integrations, and Lambda functions can still result in higher operational overhead than necessary.
AWS Amplify simplifies the process by providing a fully managed solution that includes hosting, file storage in Amazon S3, and built-in authentication with Amazon Cognito. This solution is serverless, has minimal operational overhead, and accelerates development by abstracting much of the infrastructure management.
From what I’ve seen, the answer is:
Use AWS Amplify to create a static website for uploads of media files. Use Amplify Hosting to serve the website through Amazon CloudFront. Use Amazon S3 to store the uploaded media files. Use Amazon Cognito to authenticate users.