A newspaper organization has a on-premises application which allows the public to search Its
back catalogue and retrieve individual newspaper pages via a website written in Java. They have
scanned the old newspapers into JPEGs (approx. 17TB) and used Optical Character Recognition
(OCR) to populate a commercial search product.
The hosting platform and software are now end of life and the organization wants to migrate its
archive to AWS and produce a cost efficient architecture and still be designed for availability and
durability.
Which is the most appropriate?

A.
Model the environment using CloudFormation, use an EC2 instance running Apache webserver
and an open source search application, stripe multiple standard EBS volumes together to store
the JPEGs and search index

B.
Use a single-AZ RDS MySQL instance to store the search index and the JPEG Images, use an
EC2 Instance to serve the website and translate user queries into SQL

C.
Use a CloudFront download distribution to serve the JPEGs to the end users and install the
current commercial search product, along with a Java Container for the website on EC2 instances
and use Route53 with DNS round-robin

D.
Use S3 with standard redundancy to store and serve the scanned files, use CloudSearch for
query processing, and use Elastic Beanstalk to host the website across multiple availability zones

E.
Use S3 with reduced redundancy to store and serve the scanned files, install the commercial
search application on EC2 instances and configure with auto-scaling and an Elastic Load
Balancer

Explanation:
Cloud search is the perfect option for the search related content.