Connection Options

Last updated on May 30, 2023

Hevo offers you different ways to connect to your Source account for ingesting the data. These include:

  • Direct Connection: You can use database login credentials, API Keys, or OAuth to directly connect to your database or SaaS application. Refer to the respective Source documents for the steps to configure such Sources.

  • Secure Shell (SSH) Connection: Hevo allows for both SSH and Reverse SSH connections to database Sources. To connect to an SSH tunnel server, you must whitelist Hevo’s IP address of the region where your account is created. However, this type of connection introduces a latency in the Pipeline due to encryption and tunneling. Read Connecting Through SSH and Connecting Through Reverse SSH Tunnel for the steps to set up the SSH and Reverse SSH connections, respectively.

  • Virtual Private Cloud (VPC) Connection: You can use VPC connections to ingest data from database Sources hosted in a different VPC than Hevo. Contact the Hevo Sales team for the steps to implement this. VPC connections are feasible only if your Source database is present in Amazon Web Services (AWS).

Note: SSH and VPC connections are available for database Sources only.

Selecting the Optimal Connection Option for Database Sources

In the case of database Sources, you can consider the following parameters while deciding the connection type:

  • Data Sensitivity: If your database does not contain any sensitive data, you can establish a direct connection between Hevo and the database for optimal data replication. However, for sensitive data, an SSH or VPC connection is recommended due to its enhanced encryption and tunneling.

  • Database accessibility: If your database is:

    • Hosted on-premise or on a public cloud network, you can directly connect it to Hevo.

    • Not publicly accessible over the internet, you can set up an SSH connection.

    • Hosted in a VPC different from Hevo, you can set up a VPC connection.

Optimizing the Data Replication for Database Sources

To optimize the Pipeline performance and data replication efficiency for your SaaS or database Source, you can verify that the location of your Source database or application is the same or closest geographically to the region where you create the Pipeline. For example, create your Pipeline in the US region if your database or application is present in the US region.

Note: Since the data ingestion takes longer than loading, the account is usually set up where your data lies. However, you can optimize on the Source or Destination location, or select a different region altogether.

Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Apr-14-2023 NA New document.

Tell us what went wrong