Allow Direct Connections to Data Hosted on a Cloud Platform

If you maintain SQL-based data on a cloud platform, you can use direct connections to that data when you publish workbooks and data sources to Tableau Online. When you use a direct connection, you do not need to publish a static extract of the data. Instead, depending on the underlying data type, you can determine how to keep the data current: through a live connection or refreshing an extract on a schedule. You can also require users to provide credentials for accessing the data when they open views that connect to content.

In this context, the term cloud platform means that the service is available on the public internet. Cloud platforms can include Amazon Web Services, Microsoft Azure, Google Cloud Platform, and so on.

Support for direct connections to data hosted on cloud platforms

The list below includes both live connection and extract refresh support specifically for SQL-based data hosted on a cloud platform.

Note: Make sure that Tableau Online is on your data provider's authorized list (safe list). For more information, see Tableau Online IP addresses for data provider authorization.

Encrypting connections using SSL is an option for these underlying data types. For more information, see Enable encrypted connections later in this topic.

Supported connectors

Note: Not all connectors in this list are supported by Tableau Prep Conductor. To see the supported list of connectors, open Tableau Prep Builder and expand the Connect pane.

  • MySQL

  • PostgreSQL

  • Amazon Redshift

  • Amazon Aurora (MySQL-compatible)

  • Amazon Athena

  • Amazon EMR Hadoop Hive

  • MemSQL

  • Azure SQL Database (SQL Server-compatible)

  • Azure SQL Data Warehouse (SQL Server-compatible)

  • Microsoft SQL Server

  • Google BigQuery, Google Sheets

  • Google Cloud SQL (MySQL-compatible)

  • Cloudera (Hive, Impala)

  • MongoDB BI Connector

  • Snowflake

  • EXASOL (EXASolution)

  • SAP HANA

  • Spark SQL

  • Vertica

  • Presto

  • Teradata

Notes:

  • Because of driver limitations, Tableau Online cannot support direct connections to Oracle data hosted in the cloud. To keep hosted Oracle data fresh, use Tableau Bridge, described in Expand Data Freshness Options by Using Tableau Bridge.

  • MongoDB BI Connector requires SSL. Tableau doesn’t support MondoDB Connector for BI authentication plugins.

  • For more information about supported features by connector, refer to the specific connector topic in the Supported Connectors section of the Tableau User Help.

Enable encrypted connections

You can enable SSL encryption for connections to your hosted SQL data. You do this when you create the connection in Tableau Desktop.

Notes:

  • This information does not apply to Google BigQuery, which connects over HTTPS by default and uses OAuth for authentication.

  • Tableau Online does not currently support SSL using Google Cloud SQL.

 

  1. In Tableau Desktop, connect to the data.

  2. In the Server Connection dialog box, select the Require SSL check box.

  3. For PostgreSQL and SQL Server-compatible connections click OK to complete the steps.

    For some MySQL-compatible connections, linked text appears under the Require SSL check box. This indicates that you can specify an alternative certificate file to use, such as a self-signed certificate.

  4. (Optional) Use a self-signed or other custom certificate to connect to this data over SSL.

    Note: This step does not apply to Google BigQuery, because it uses OAuth for authentication to the server.

    1. Select the link text that appears.

    2. In the Configure and Use SSL Certificate dialog, specify the certificate’s .pem file.

      For example, for MySQL connections to data hosted on Amazon RDS, you can point to Amazon’s self-signed certificate file at this address.

      Note: If you plan to publish with an SSL connection that uses a self-signed or other custom certificate, test your configuration to make sure it works as expected. For some configurations, Tableau Online supports only certificates that are signed by a publicly trusted certificate authority, such as Verisign, Thawte, GlobalSign, and so on.

See also

Thanks for your feedback! There was an error submitting your feedback. Try again or send us a message.