The moment we saw the announcement for Amazon Athena, we knew it’s a perfect match for Redash. For those who missed the news, Athena is a new service from AWS to analyze data directly from S3 using Standard SQL. It’s basically Presto as a service.
Creating new data source for Redash is quite easy, but our friends at Amazon decided to make it a bit more difficult this time — for now they released only a JDBC connector to connect with Athena. Redash’s backend is written in Python and using a JDBC connector is not straightforward. But we won’t let something like this to be in our way. 😎
Long story short, I’m happy to share with you that Redash supports Amazon Athena now! Those of you who use our hosted service, you can already connect to it. See instructions in our user guide.
As with any data source, by connecting Redash with Amazon Athena, you get all the regular Redash benefits — nice query interface, visualizations, dashboards and alerts.
(the following is technical details on how this query runner works and relevant for on-premise users only)
👉 Update: starting from v2.0.0 you no longer need the proxy and we have a direct connector to Athena.
If you run Redash on-premise, you can either wait for the v1.0 release or back port the support to your current deployment. Note that you need to run Redash v0.12 to use this new query runner as is.
Note that to overcome the language barrier, we created a simple proxy service that takes AWS credentials & the Athena query, processes it and returns the data to Redash. You will need to run this proxy along side your Redash instance to be able to use the new query runner.
We will post instructions on how to do the back port in our discussion forum.
As always, your feedback is more than welcomed. We are eager to hear how you use Redash in general and this new Amazon Athena support.