Amazon QuickSight Administrator's guide to connecting Databricks - Amazon QuickSight
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Amazon QuickSight Administrator's guide to connecting Databricks

You can use Amazon QuickSight to connect to Databricks on Amazon. You can connect to Databricks on Amazon whether you signed up for through Amazon Marketplace or through the Databricks website.

Before you can connect to Databricks, your create or identify existing resources that the connection requires. Use this section to help you gather the resources you need to connect from QuickSight to Databricks.

  • To learn how to obtain your Databricks connection details, see Databricks ODBC and JDBC connections..

  • To learn how to obtain your Databricks credentials—personal access token or user name and password—for authentication, see Authentication requirements in the Databricks documentation.

    To connect to a Databricks cluster, you need Can Attach To and Can Restart permissions. These permissions are managed in Databricks. For more information, see Permission Requirements in the Databricks documentation..

  • If you are setting up a private connection for Databricks, you can learn more about how to configure a VPC for use with QuickSight, see Connecting to a VPC with Amazon QuickSight in the QuickSight documentation. If the connection isnt' visible, verify with a system administrator that the network has open inbound endpoints for Amazon Route 53. the hostname of a Databricks workspace uses a public IP , there needs to be DNS TCP and DNS UDP inbound and outbound rules to allow traffic on DNS port 53, for the Route 53 security group. An administrator needs to create a security group with 2 inbound rules: one for DNS(TCP) on port 53 to the VPC CIDR and one for DNS(UDP) for port 53 to the VPC CIDR.

    For Databricks-related details if you are using PrivateLink instead of a public connection, see Enable Amazon PrivateLink in the Databricks documentation.