The GIS office publishes a large open geospatial dataset in Amazon S3 that external researchers download heavily, driving up the city’s request and data-transfer bills. Which S3 feature best shifts those request and download costs to the requesters?
Select an answer to reveal the explanation.
Short Explanation
If outsiders pull terabytes of open GIS data, don’t eat every GET on the city card. Requester Pays hands request and download charges to the researchers pulling the objects. Outlook ZIPs, turning off logging, or anonymous FTP on gp2 don’t fix the bill fairly.
Full Explanation
Amazon S3 Requester Pays configures a bucket so requesters pay for requests and data downloads rather than the bucket owner, which suits large open datasets shared with external researchers. Emailing giant archives, disabling audit logging, or hosting anonymous FTP on EC2 shift risk and operations without a clean cost-allocation model. Requester Pays is the purpose-built cost control for this sharing pattern.