Which solution will meet these requirements?
Create a virtual server by using Amazon Lightsail. Configure the web server in the Lightsail instance. Upload website content by using an SFTP client.
Create an AWS Auto Scaling group for Amazon EC2 instances. Use an Application Load Balancer. Upload website content by using an SFTP client.
Create a private Amazon S3 bucket. Use an S3 bucket policy to allow access from a CloudFront origin access identity (OAI). Upload website content by using the AWS CLI.
Create a public Amazon S3 bucket. Configure AWS Transfer for SFTP. Configure the S3 bucket for website hosting. Upload website content by using the SFTP client.
Explanations:
While Amazon Lightsail is a cost-effective solution, it introduces unnecessary complexity for a static website, which can be efficiently hosted on S3. Additionally, Lightsail requires management of instances and does not leverage the benefits of a scalable, serverless architecture.
Using an Auto Scaling group with EC2 instances and an Application Load Balancer is more complex and costly than necessary for serving static content. This architecture requires management of instances and does not offer the simplicity and cost-effectiveness of using Amazon S3 for static website hosting.
A private S3 bucket with a policy for CloudFront’s origin access identity provides a secure and cost-effective way to host static content. S3 is designed for high durability and scalability, making it ideal for static websites. The AWS CLI can be used to upload content easily.
Although this option allows for SFTP uploads, a public S3 bucket is not ideal for security. Configuring S3 for website hosting adds unnecessary complexity, as static content can be hosted securely in a private bucket with CloudFront. Additionally, using AWS Transfer for SFTP introduces management overhead for a simple static website.