Which solution will meet these requirements?
Set up a new Amazon EFS share, move all image and video files to this share, and then attach this new drive as a mount point to all existing servers. Create an Elastic Load Balancer with Auto Scaling general purpose instances. Enable Amazon CloudFront to the Elastic Load Balancer. Enable Cost Explorer and use AWS Trusted Advisor checks to continue monitoring the environment for future savings.
Implement Auto Scaling with general purpose instance types and an Elastic Load Balancer. Enable an Amazon CloudFront distribution to Amazon S3 and move images and video files to Amazon S3. Reserve general purpose instances to meet base performance requirements. Use Cost Explorer and AWS Trusted Advisor checks to continue monitoring the environment for future savings.
Move the entire website to Amazon S3 using the S3 website hosting feature. Remove all the web servers and have Amazon S3 communicate directly with the application servers in Amazon VPC.
Use AWS Elastic Beanstalk to deploy the .NET application. Move all images and video files to Amazon EFS. Create an Amazon CloudFront distribution that points to the EFS share. Reserve the m4.4xl instances needed to meet base performance requirements.
Explanations:
Amazon EFS is a good solution for shared file storage, but CloudFront should be used with S3 rather than EFS for static content delivery. Using instance storage with EFS in this scenario is costly and inefficient for serving media files. Also, using XL storage instances for handling traffic and replication issues does not address the root problem.
This option moves the media files to Amazon S3, which provides durability, scalability, and high availability. It also includes Auto Scaling with general-purpose EC2 instances and CloudFront for content delivery, addressing both reliability and cost considerations effectively. Reserved instances can be used to lower costs for baseline performance.
Moving the entire website to S3 using the S3 website hosting feature is not a suitable solution for a dynamic .NET application, as it would require significant architectural changes and could limit the flexibility of the application. S3 is not designed to run dynamic .NET applications directly.
While using Elastic Beanstalk can simplify application management, serving media files via EFS is not ideal for high-performance content delivery. CloudFront is better suited to S3 for static content distribution, and using m4.4xl instances would incur unnecessary costs without addressing the underlying reliability issue in storage.
I organize that the answer is:
Implement Auto Scaling with general purpose instance types and an Elastic Load Balancer. Enable an Amazon CloudFront distribution to Amazon S3 and move images and video files to Amazon S3. Reserve general purpose instances to meet base performance requirements. Use Cost Explorer and AWS Trusted Advisor checks to continue monitoring the environment for future savings.