> Amazon Athena is an interactive query service that makes it easy to analyze data in Amazon S3 using standard SQL. Athena is serverless, so there is no infrastructure to manage, and you pay only for the queries that you run. > Athena is easy to use. Simply point to your data in Amazon S3, define the schema, and start querying using standard SQL. Most results are delivered within seconds. With Athena, there’s no need for complex ETL jobs to prepare your data for analysis. This makes it easy for anyone with SQL skills to quickly analyze large-scale datasets. ## My #OpenQuestions - What are all the considerations for how to make [[DynamoDB]]-mastered data queryable from Athena? Is it [[DynamoDB streams]] to [[AWS Lambda|Lambda]] to [[AWS S3|S3]], or can it be done directly without custom code in a Lambda? And does [[DynamoDB single-table design|Single-table design]] make this more difficult? - Given an RDBMS in [[AWS RDS]], what's the best way to make it queryable from Athena? Can the schema already present in the RDBMS be re-used in some way for defining the schema in Athena? - How strict or loose can the Athena schema be? - How does Athena compare to [[Rockset]] in terms of best fit use cases? - Is there any delay between an object being updated in S3 and the Athena query using the new version of the object in its read process? --- ## References - https://aws.amazon.com/athena