---
schema_version: "1"
id: 342cdf82a6064c11faedcd75c69e73a18e451b7b7553b5e81acb44ce9e714bab
title: Plan Your Data Connect Deployment
collection: tableau
version: current
locale: en-us
portal_url: https://docs.salesforce.com/tableau/current/en-us/online/data_connect_get_started.md
canonical_url: https://help.tableau.com/current/online/en-us/data_connect_get_started.htm
source_site: help.tableau.com
content_type: documentation
content_hash: 04f9866bb5e3476e413255b4d7137674ea309e6e6337d00a6218ae00090ec0b0
description: Plan a Data Connect deployment, covering infrastructure, networking, and capacity.
---
[Skip to main content](#main-content)

# Plan Your Data Connect Deployment

As of September 2025, Tableau Data Connect is no longer available for new deployments. We recommend that existing customers migrate their Data Connect deployment to [Private Connect](https://help.tableau.com/current/online/en-us/private_connect_migrate_from_bridge.htm) or [Tableau Bridge](https://help.tableau.com/current/online/en-us/data_fresh_sync_section.htm). Data Connect will be retired in the future.

Data Connect is a paid subscription service available to Tableau Cloud Enterprise and Tableau+ customers. After you have purchased Data Connect, the site admin will be able to configure the service in the settings page of Tableau Cloud.

### Infrastructure specifications

- **Compute**: A location for hosting Data Connect. This can be a bare-metal or VM, and can be located in a private network or in the cloud.
- **Operating System (OS)**: An up-to-date and patched installation of a supported Linux distribution.
- **Storage**: Allocated storage space to host the OS, Data Connect, and the extracts it creates when performing refreshes.
- **Network**: The compute must be able to connect to your data source and two locations on the public internet.

### Node specifications

<table style="width: 100%;" class="simple-table">
                    <colgroup><col style="width: 50%;">
                    <col style="width: 460px;">
                    </colgroup><tbody>
                        <tr>
                            <td>Number of nodes</td>
                            <td>
                                <p>Production workload minimum: three nodes per network</p>
                                <p> Development/test workload minimum: one node per network </p>
                            </td>
                        </tr>
                        <tr>
                            <td>vCPU</td>
                            <td>Minimum: 8 vCPU
<br>Recommended: 16 vCPU or more
</td>
                        </tr>
                        <tr>
                            <td>Memory</td>
                            <td>Minimum: 16 GB 
<br>Recommended: 64 GB or more
</td>
                        </tr>
                        <tr>
                            <td>Root volume</td>
                            <td>
                                <p>Minimum: 100 GB</p>
                                <p>Recommended: 200 GB</p>
                            </td>
                        </tr>
                        <tr>
                            <td>Variable volume</td>
                            <td>
                                <p>Minimum: 100 GB</p>
                                <p>Recommended: 200 GB</p>
                            </td>
                        </tr>
                        <tr>
                            <td>
                                <p>Storage (two disk)</p>
                                <p><b>Important</b>: The secondary disk must be raw and unformatted.</p>
                            </td>
                            <td>
                                <p>Root disk <br>Minimum:  200 GB disk space <br>Recommended: Greater than 300 GB</p>
                                <p>Secondary disk<br>Minimum: 200 GB<br>Recommended: Greater than 500 GB</p>
                            </td>
                        </tr>
                        <tr>
                            <td>Permission</td>
                            <td>Root access to host</td>
                        </tr>
                    </tbody>
                </table>

### Linux Operating System

<table style="width: 100%;" class="simple-table"><colgroup><col style="width: 50%;"> <col style="width: 50%;"></colgroup><tbody><tr><td>Supported distributions</td><td>RHEL-8<br>RHEL-9<br>Ubuntu-20.04<br>Ubuntu-22.04</td></tr></tbody></table>

### Networking specifications

For more information about Data Connect component relationships, see [Architecture](https://help.tableau.com/current/online/en-us/data_connect_about_overview.htm#Architec).

<table style="width: 100%;" class="simple-table">
                    <colgroup><col style="width: 50%;">
                    <col style="width: 50%;">
                    </colgroup><tbody>
                        <tr>
                            <td>Proxy filtering</td>
                            <td>See <a href="https://help.tableau.com/current/online/en-us/to_bridge_security.htm">Optional forward proxy filtering</a>.</td>
                        </tr>
                        <tr>
                            <td>Bi-directional communication with Tableau Cloud on port 443
(Application layer)
</td>
                            <td rowspan="2">IP&nbsp;address range is unique for each Tableau Cloud pod. To determine your IP&nbsp;address range, see <a href="https://help.tableau.com/current/pro/desktop/en-us/publish_tableau_online_ip_authorization.htm" target="_blank">Authorize Access to Cloud Data Published to Tableau Cloud</a>.</td>
                        </tr>
                        <tr>
                            <td>Outbound requests for certification validation on port 80
(Application layer)
</td>
                        </tr>
                        <tr>
                            <td>Outbound TLS client authentication on port 443 with mutual TLS authentication <br>(Orchestration layer)
</td>
                            <td>52.42.211.235<br>52.10.6.79 <br>35.167.70.143

</td>
                        </tr>
                        <tr>
                            <td>Outbound listing of Fully Qualified Domain Names (FQDN)<br>(Orchestration layer)
</td>
                            <td>tunnel.rafay-edge.net
<br>api.rafay.dev
<br>control.rafay.dev
<br>fluentd-aggr.rafay-edge.net
<br>influxdb01.core.rafay-edge.net
<br>debug.core.rafay-edge.net
<br>edge.core.rafay-edge.net
<br>registry.rafay-edge.net
<br>app.rafay.dev
<br>console.rafay.dev
<br>*.connector.kubeapi-proxy.rafay.dev<br>*.user.kubeapi-proxy.rafay.dev
<br>event.core.rafay-edge.net
<br>repo.rafay-edge.net
<br>*.connector.cdrelay.rafay.dev
<br>*.user.cdrelay.rafay.dev
<br>*.connector.infrarelay.rafay.dev
<br>*.user.infrarelay.rafay.dev
</td>
                        </tr>
                        <tr>
                            <td>
                                <p>Internal network</p>
                            </td>
                            <td>
                                <p>The cluster nodes will need the same network access to the data source as is required by <span class="mc-variable Variables.TabsProductDesktop variable">Tableau Desktop</span>.</p>
                            </td>
                        </tr>
                        <tr>
                            <td>
                                <p>Inbound network rules</p>
                                <p>To enable communication between the nodes within your environment, configure network rules on the nodes  for these ports.<br></p>
                            </td>
                            <td>
                                <p>Port ranges:
</p>
                                <ul>
                                    <li>53, TCP</li>
                                    <li>6443, TCP</li>
                                    <li>2379-2380, TCP </li>
                                    <li>10250, 10255, TCP </li>
                                    <li>10259, 10251, TCP </li>
                                    <li>10257, 10252, TCP </li>
                                    <li>30000-32767, TCP</li>
                                    <li>8285, 8472, UDP </li>
                                    <li>8500, TCP </li>
                                    <li>8600, UDP </li>
                                    <li>8301, TCP/UDP </li>
                                    <li>9099, TCP </li>
                                    <li>5656, TCP </li>
                                    <li>4789, UDP </li>
                                </ul>
                            </td>
                        </tr>
                        <tr>
                            <td>Tableau Cloud permissions</td>
                            <td>Site Admin role and the credentials to access the data source.</td>
                        </tr>
                        <tr>
                            <td>Data source</td>
                            <td>An authentication method for the data source that is currently supported by Data Connect and that is network accessible from the cluster.</td>
                        </tr>
                    </tbody>
                </table>

### Database access

Data Connect uses Tableau connectors to connect to different databases to maintain data freshness. Some of those connectors require drivers to communicate with the databases. To get drivers for connectors that the Data Connect supports, go to Tableau [Driver Download](http://www.tableau.com/support/drivers) and filter to Linux. Data Connect only supports Linux drivers. Make sure to use the instructions listed for each database.

### Database authentication

The underlying data that a data source, Prep Conductor flow, or virtual connection connects to often requires authentication. If authentication is required, the publisher or owner can configure how the database credentials are obtained.

#### Data sources

The authentication configuration options for data sources are _Prompt user_ or _Embedded password._

- If the data source is set to prompt users, database credentials are not stored with the connection. This means, a user who opens the data source (or workbook that uses the data source) must enter their own database credentials to access the data.
- If a data source is set up with the password embedded, database credentials are saved with the connection and used by anyone who accesses the data source (or refreshes the data source).

For more information, see [Set Credentials for Accessing Your Published Data](https://help.tableau.com/current/pro/desktop/en-us/publishing_sharing_authentication.htm).

#### Tableau Prep Conductor and virtual connections

Database credentials are stored in a Prep flow or a virtual connection. For Prep flows, the credentials are used when a Prep Conductor flow runs. For virtual connections, these credentials are used by anyone who accesses the virtual connection.

For more information on data source credential management, please refer to [Data Connect Security](https://help.tableau.com/current/online/en-us/data_connect_security.htm).

## Capacity planning

There are several tools available to administrators to manage capacity of their workloads on Data Connect.

![Compontents of Data Connect service include Private network, pools, clusters, and nodes.](/tableau/current/en-us/online/en-us/Img/data_connect_object_relationship.png)

### Cluster management

Data Connect clusters are a cluster of nodes that access data within a specified private network. Those nodes can access any databases within their network that they have been configured to access. All Bridge clients on all nodes of that cluster can handle workloads for any sites that have access to the cluster. To increase capacity of a cluster you can add nodes to the cluster to increase throughput or increase the size of the computer (CPU, memory, etc).

### Load balancing with pools

Each cluster uses a pool to load balance traffic across all Bridge clients in the cluster. Having multiple nodes within each cluster ensures that you have multiple Bridge clients available to handle traffic associated with the pool. For every domain added to a pool, all traffic to that domain is load balanced across the cluster. Domains cannot be added to more than one pool on a site. This design ensures traffic is routed appropriately.

### Site limits

There are site limits enforced on jobs delivered by Data Connect to ensure a good experience for all customers on Tableau Cloud. The limits that are enforced are the same as those enforced for Tableau Bridge because Data Connect is deploying Tableau Bridge on your behalf to service database queries. For more information on those limits, see[Bridge Site Capacity](https://help.tableau.com/current/online/en-us/to_bridge_site_capacity.htm).

For more information about capacity planning, download the whitepaper, [Accessing Your Private Network Data with Tableau Cloud](https://www.tableau.com/learn/whitepapers/tableau-bridge-data-connect-best-practices-guide).