Store the game files on Amazon EBS volumes mounted on Amazon EC2 instances within an Auto Scaling group. Configure an FTP service on the EC2 instances. Use an Application Load Balancer in front of the Auto Scaling group. Publish the game download URL for users to download the package.
Store the game files on Amazon EFS volumes that are attached to Amazon EC2 instances within an Auto Scaling group. Configure an FTP service on each of the EC2 instances. Use an Application Load Balancer in front of the Auto Scaling group. Publish the game download URL for users to download the package.
Configure Amazon Route 53 and an Amazon S3 bucket for website hosting. Upload the game files to the S3 bucket. Use Amazon CloudFront for the website. Publish the game download URL for users to download the package.
Configure Amazon Route 53 and an Amazon S3 bucket for website hosting. Upload the game files to the S3 bucket. Set Requester Pays for the S3 bucket. Publish the game download URL for users to download the package.
Explanations:
Storing the game files on EBS volumes requires an EC2 instance to access the data, which introduces latency and limits scalability. Using an FTP service also complicates the setup for global access, as the performance may be hindered by the geographic distance from the data center.
Amazon EFS can provide shared file access, but it still requires EC2 instances for hosting, which may lead to latency issues and does not optimize for global distribution. Additionally, maintaining an FTP service complicates user access and doesn’t leverage the benefits of modern cloud services.
Using Amazon S3 for storage provides highly durable and scalable object storage, and with Amazon CloudFront as a CDN, it enhances download performance globally by caching files at edge locations, thus reducing latency. This option efficiently handles high traffic and provides low transfer costs.
While using S3 for hosting is effective, enabling Requester Pays complicates the access for users, as they need to be aware that they will incur charges for downloading. This could deter users and reduce download rates, making it less appealing than option C.
As far as I’m aware, the answer is:
Configure Amazon Route 53 and an Amazon S3 bucket for website hosting. Upload the game files to the S3 bucket. Use Amazon CloudFront for the website. Publish the game download URL for users to download the package.