What should a solutions architect recommend to accomplish this?
Use Amazon S3 static website hosting to store and serve the front end. Use AWS Elastic Beanstalk for the application layer. Use Amazon DynamoDB to store user data.
Use Amazon S3 static website hosting to store and serve the front end. Use Amazon Elastic KubernetesService (Amazon EKS) for the application layer. Use Amazon DynamoDB to store user data.
Use Amazon S3 static website hosting to store and serve the front end. Use Amazon API Gateway and AWS Lambda functions for the application layer. Use Amazon DynamoDB to store user data.
Use Amazon S3 static website hosting to store and serve the front end. Use Amazon API Gateway and AWS Lambda functions for the application layer. Use Amazon RDS with read replicas to store user data.
Explanations:
While using Amazon S3 for static hosting is a good choice, AWS Elastic Beanstalk may introduce unnecessary operational overhead compared to serverless options. It is not optimized for low-latency access to JSON documents like DynamoDB.
Amazon S3 is appropriate for static content, but using Amazon EKS for the application layer adds complexity and higher operational overhead compared to serverless architectures. DynamoDB is suitable, but the combination is not optimal for the described requirements.
This option effectively uses Amazon S3 for static website hosting and employs serverless architecture with API Gateway and AWS Lambda, minimizing operational overhead. DynamoDB is ideal for storing JSON documents with low-latency access. This setup accommodates expected low traffic with the ability to handle peaks efficiently.
Although using S3 for static hosting is correct, using Amazon RDS with read replicas can lead to increased operational overhead and complexity. RDS may not provide the same level of low-latency access for JSON documents as DynamoDB, making this option less suitable for the given requirements.