The city's open-data portal is a static site of CSVs, maps, and HTML with a few dynamic query APIs still on the permitting backend. The current design serves everything from a pair of always-on EC2 web servers. Which storage-and-delivery modernization should architects select?
Select an answer to reveal the explanation.
Short Explanation
A pile of CSVs and HTML is a brochure rack, not an application server. Park the static files on S3, let CloudFront hand them out, and keep the living queries on APIs. Don't freeze the whole portal into Glacier.
Full Explanation
Static website modernization uses an Amazon S3 origin plus Amazon CloudFront for global delivery, while dynamic query paths remain on APIs. That split reduces always-on EC2 for file serving and fits multi-account public content. Glacier is not a website origin for interactive open data, and EC2 local disks or USB clients miss the S3-centered pattern.