Amazon Aurora PostgreSQL

Specify Amazon Aurora PostgreSQL Connection Settings

Perform the following steps to configure Amazon Aurora PostgreSQL as a Source in Hevo:

1. Click PIPELINES in the Navigation Bar.

2. Click + CREATE PIPELINE in the Pipelines List View.

3. On the Select Source Type page, select Amazon Aurora PostgreSQL.

4. On the Configure your Amazon Aurora PostgreSQL Source page, specify the following:

   

   • Pipeline Name: A unique name for your Pipeline, not exceeding 255 characters.

   • Database Host: The Amazon Aurora PostgreSQL host’s IP address or DNS.

   • Database Port: The port on which your Amazon Aurora PostgreSQL server listens for connections. Default value: 5432.

   • Database User: The read-only user who has the permissions to read tables in your database.

   • Database Password: The password for the read-only user.

   • Select an Ingestion Mode: The desired mode by which you want to ingest data from the Source. This section is expanded by default. However, you can collapse the section by clicking SEE LESS. Default value: Logical Replication.

     The available ingestion modes are Logical Replication, Table, and Custom SQL. Additionally, the XMIN ingestion mode is available for Early Access. Logical Replication is the recommended ingestion mode and selected by default.

     

     Depending on the ingestion mode you select, you must configure the objects to be replicated. Refer to section, Object and Query Mode Settings for the steps to do this.

     Note:

     • PostgreSQL versions 15.7 and below do not support logical replication on read replicas. This feature is available starting from version 16.

     • For Custom SQL ingestion mode, all Events loaded to the Destination are billable.

   • Database Name: The database that you wish to replicate.

   • Connection Settings:

     • Connect through SSH: Enable this option to connect to Hevo using an SSH tunnel, instead of directly connecting your PostgreSQL database host to Hevo. This provides an additional level of security to your database by not exposing your PostgreSQL setup to the public. Read Connecting Through SSH.

       If this option is disabled, you must whitelist Hevo’s IP addresses. Refer to the content for your PostgreSQL variant for steps to do this.

     • Use SSL: Enable it to use SSL encrypted connection. You should also enable this if you are using Heroku PostgreSQL databases. To enable this, specify the following:

       • CA File: The file containing the SSL server certificate authority (CA).

         • Load all CA Certificates: If selected, Hevo loads all CA certificates (up to 50) from the uploaded CA file, else it loads only the first certificate.

           Note: Select this check box if you have more than one certificate in your CA file.

       • Client Certificate: The client public key certificate file.

       • Client Key: The client private key file.

   • Advanced Settings

     • Load Historical Data: Applicable for Pipelines with Logical Replication mode. If this option is enabled, the entire table data is fetched during the first run of the Pipeline. If disabled, Hevo loads only the data that was written in your database after the time of creation of the Pipeline.

     • Merge Tables: Applicable for Pipelines with Logical Replication mode. If this option is enabled, Hevo merges tables with the same name from different databases while loading the data to the warehouse. Hevo loads the Database Name field with each record. If disabled, the database name is prefixed to each table name. Read How does the Merge Tables feature work?.

     • Include New Tables in the Pipeline: Applicable for all ingestion modes except Custom SQL. If enabled, Hevo automatically ingests data from tables created in the Source after the Pipeline has been built. These may include completely new tables or previously deleted tables that have been re-created in the Source. If disabled, new and re-created tables are not ingested automatically. They are added in SKIPPED state in the objects list, on the Pipeline Overview page. You can update their status to INCLUDED to ingest data. You can change this setting later. You can include these objects post-Pipeline creation to ingest data.

5. Click TEST CONNECTION. This button is enabled once you specify all the mandatory fields. Hevo’s underlying connectivity checker validates the connection settings you provide.

6. Click TEST & CONTINUE to proceed for setting up the Destination. This button is enabled once you specify all the mandatory fields.

Object and Query Mode Settings

Once you have specified the Source connection settings in Step 4 above, do one of the following:

• For Pipelines configured with the Table or Logical Replication mode:

  1. On the Select Objects page, select the objects you want to replicate and click CONTINUE.

     

     Note:

     • Each object represents a table in your database.

     • From Release 2.19 onwards, for log-based Pipelines, you can keep the objects listed in the Select Objects page deselected by default. In this case, when you skip object selection, all objects are skipped for ingestion, and the Pipeline is created in the Active state. You can include the required objects post-Pipeline creation. Contact Hevo Support to enable this option for your team.

  2. On the Configure Objects page, specify the query mode you want to use for each selected object.

     

     Note: In Full Load mode, Hevo attempts to replicate the full table in a single run of the Pipeline, with an ingestion limit of 25 Million rows.

• For Pipelines configured with the XMIN mode:

  1. On the Select Objects page, select the objects you want to replicate.

     

     Note:

     • Each object represents a table in your database.

     • For the selected objects, only new and updated records are ingested using the XMIN column.

     • The Edit Config option is unavailable for the objects selected for XMIN-based ingestion. You cannot change the ingestion mode for these objects post-Pipeline creation.

  2. Click CONTINUE.

• For Pipelines configured with the Custom SQL mode:

  1. On the Provide Query Settings page, enter the custom SQL query to fetch data from the Source.

  2. In the Query Mode drop-down, select the query mode, and click CONTINUE.

     

Data Replication

Note: The custom frequency must be set in hours as an integer value. For example, 1, 2, or 3 but not 1.5 or 1.75.

• Historical Data: In the first run of the Pipeline, Hevo ingests all available data for the selected objects from your Source database.

• Incremental Data: Once the historical load is complete, data is ingested as per the ingestion frequency.