QuickSight can connect to on-premise ClickHouse setup (23.11+) via MySQL interface using the official MySQL data source and Direct Query mode.Documentation Index
Fetch the complete documentation index at: https://private-7c7dfe99-page-updates.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
On-premise ClickHouse server setup
Please refer to the official documentation on how to set up a ClickHouse server with enabled MySQL interface. Aside from adding an entry to the server’sconfig.xml
mysql_user that uses the generated hash:
/etc/clickhouse-server/users.d/mysql_user.xml
password_double_sha1_hex entry with your own generated Double SHA1 hash.
QuickSight requires several additional settings in the MySQL user’s profile.
/etc/clickhouse-server/users.d/mysql_user.xml
config.xml, uncomment out the following to listen on all addresses:
mysql binary available, you can test the connection from the command line.
Using the sample username (mysql_user) and password (LZOQYnqQN4L/T6L0) from above the command line would be:
Connecting QuickSight to ClickHouse
First of all, go to https://quicksight.aws.amazon.com, navigate to Datasets and click “New dataset”:Search for the official MySQL connector bundled with QuickSight (named just MySQL):
Specify your connection details. Please note that MySQL interface port is 9004 by default, and it might be different depending on your server configuration.
Now, you have two options on how to fetch the data from ClickHouse. First, you could select a table from the list:
Alternatively, you could specify a custom SQL to fetch your data:
By clicking “Edit/Preview data”, you should be able to see the introspected table structure or adjust your custom SQL, if that’s how you decided to access the data:
Make sure you have “Direct Query” mode selected in the bottom left corner of the UI:
Now you can proceed with publishing your dataset and creating a new visualization!
Known limitations
- SPICE import doesn’t work as expected; please use Direct Query mode instead. See #58553.