Which solution will meet these requirements MOST cost-effectively?
Store the logs in Amazon S3. Use Amazon Athena tor analysis.
Store the logs in Amazon RDS. Use a database client for analysis.
Store the logs in Amazon OpenSearch Service. Use OpenSearch Service for analysis.
Store the logs in an Amazon EMR cluster Use a supported open-source framework for SQL-based analysis.
Explanations:
Storing logs in Amazon S3 allows for cost-effective storage of large amounts of data. Amazon Athena can be used for on-demand SQL queries directly on the data in S3, eliminating the need for additional infrastructure management and supporting standard SQL, which fits the requirement for analysis once a week.
Amazon RDS is designed for transactional workloads and may incur high costs due to provisioning and managing a database instance, especially for large volumes of logs. Additionally, running regular analyses might require scaling the database, increasing costs further.
Amazon OpenSearch Service is suited for real-time data analysis and search but can be more costly for storing large volumes of logs compared to S3. It is also less optimal for standard SQL queries, as it primarily uses a different query language, which may not meet the requirement effectively.
While Amazon EMR can handle large-scale data processing and supports SQL-based analysis using tools like Hive or Presto, it involves more management overhead and costs compared to using S3 with Athena. Additionally, setting up and managing an EMR cluster for infrequent analyses can be inefficient and costly.