- About Hevo
- Hevo Features
- Hevo System Architecture
- Core Concepts
- Free Trials
- Regulatory Compliance
- Hevo Support
- Getting Started
- Creating an Account in Hevo
- Connection Options
- Familiarizing with the UI
- Creating your First Pipeline
- Data Loss Prevention and Recovery
- Activity Log
- Data Ingestion
- Ingestion Modes and Query Modes
- Ingestion Modes
- Types of Data Synchronization
- Ingestion and Loading Frequency
- Ingestion Frequency and Data Synchronization
- Data Ingestion Statuses
- Deferred Data Ingestion
- Query Modes for Ingesting Data
- Handling of Primary Keys
- Handling of Updates
- Handling of Deletes
- Hevo-generated Metadata
- Data Loading
- Loading Data in a Database Destination
- Loading Data to a Data Warehouse
- Optimizing Data Loading for a Destination Warehouse
- Manually Triggering the Loading of Events
- Scheduling Data Load for a Destination
- Loading Events in Batches
- Data Loading Statuses
- Name Sanitization
- Table and Column Name Compression
- Parsing Nested JSON Fields in Events
- Data Flow in a Pipeline
- Familiarizing with the Pipelines UI
- Pipeline Objects
Working with Pipelines
- Best Practices for Creating Database Pipelines
- Creating a Pipeline
- Scheduling a Pipeline
- Modifying a Pipeline
- Prioritizing a Pipeline
- Viewing Pipeline Progress
- Troubleshooting Data Replication Errors
- Pausing and Deleting a Pipeline
- Log-based Pipelines
- Python Code-Based Transformations
- Drag and Drop Transformations
- Effect of Transformations on the Destination Table Structure
- Transformation Reference
- Using Schema Mapper
- Mapping Statuses
- Auto Mapping Event Types
- Mapping a Source Event Type with a Destination Table
- Mapping a Source Event Type Field with a Destination Table Column
- Schema Mapper Actions
- Fixing Unmapped Fields
- Resolving Incompatible Schema Mappings
- Resizing String Columns in the Destination
- Schema Mapper Compatibility Table
- Troubleshooting Failed Events in a Pipeline
- Pipeline FAQs
- Events Usage
- Free Sources
Databases and File Systems
- Data Warehouses
- Connecting to a Local Database
- Amazon DocumentDB
- Amazon DynamoDB
- Generic MongoDB
- MongoDB Atlas
- Support for Multiple Data Types for the _id Field
- Example - Merge Collections Feature
- Errors During Pipeline Creation
- Troubleshooting MongoDB Change Streams Connection
- Troubleshooting MongoDB OpLog Connection
- SQL Server
- Amazon Aurora MySQL
- Amazon RDS MySQL
- Azure MySQL
- Google Cloud MySQL
- Generic MySQL
- MariaDB MySQL
Errors During Pipeline Creation
- Error 1003 - Connection to host failed
- Error 1006 - Connection to host failed
- Error 1007 - SSH connection failed
- Error 1011 - Access denied
- Error 1012 - Replication access denied
- Error 1017 - Connection to host failed
- Error 1026 - Failed to connect to database
- Error 1027 - Unsupported BinLog format
- Failed to determine binlog filename/position
- Schema 'xyz' is not tracked via bin logs
- Errors Post-Pipeline Creation
- Errors During Pipeline Creation
- MySQL FAQs
- Amazon Aurora PostgreSQL
- Amazon RDS PostgreSQL
- Azure PostgreSQL
- Google Cloud PostgreSQL
- Heroku PostgreSQL
- Generic PostgreSQL
Errors during Pipeline creation
- Error 1003 - Authentication failure
- Error 1006 - Connection settings errors
- Error 1011 - Access role issue for logical replication
- Error 1012 - Access role issue for logical replication
- Error 1014 - Database does not exist
- Error 1017 - Connection settings errors
- Error 1023 - No pg_hba.conf entry
- Error 1024 - Number of requested standby connections
- Errors Post-Pipeline Creation
- Errors during Pipeline creation
- PostgreSQL FAQs
- File Storage
- Engineering Analytics
- Finance & Accounting Analytics
- Apple Search Ads
- Facebook Ads
- Facebook Page Insights
- Google Campaign Manager
- Google Ads
- Google Analytics
- Google Analytics 4
- Google Analytics 360
- Google Play Console
- Google Search Console
- Instagram Business
- LinkedIn Ads
- Microsoft Advertising
- Pinterest Ads
- SendGrid Webhook
- Salesforce Marketing Cloud
- Snapchat Ads
- TikTok Ads
- Twitter Ads
- YouTube Analytics
- Product Analytics
- Sales & Support Analytics
- Source FAQs
- Familiarizing with the Destinations UI
- Amazon Redshift
- Hevo Managed Google BigQuery
- Google BigQuery
- Destination FAQs
- Activate Concepts
- Familiarizing with the Activate UI
- Working with Activate
- Activate Warehouses
- Activate Targets
- Account Management
- Personal Settings
- Team Settings
- Account Suspension and Restoration
- General FAQs
- Release Notes
- Release Version 1.98
- Release Version 1.97
- Release Version 1.96
- Release Version 1.95
- Release Version 1.93 & 1.94
- Release Version 1.92
- Release Version 1.91
- Release Version 1.90
- Release Version 1.89
- Release Version 1.88
- Release Version 1.87
- Release Version 1.86
- Release Version 1.84 & 1.85
- Release Version 1.83
- Release Version 1.82
- Release Version 1.81
- Release Version 1.80 (Jan-24-2022)
- Release Version 1.79 (Jan-03-2022)
- Release Version 1.78 (Dec-20-2021)
- Release Version 1.77 (Dec-06-2021)
- Release Version 1.76 (Nov-22-2021)
- Release Version 1.75 (Nov-09-2021)
- Release Version 1.74 (Oct-25-2021)
- Release Version 1.73 (Oct-04-2021)
- Release Version 1.72 (Sep-20-2021)
- Release Version 1.71 (Sep-09-2021)
- Release Version 1.70 (Aug-23-2021)
- Release Version 1.69 (Aug-09-2021)
- Release Version 1.68 (Jul-26-2021)
- Release Version 1.67 (Jul-12-2021)
- Release Version 1.66 (Jun-28-2021)
- Release Version 1.65 (Jun-14-2021)
- Release Version 1.64 (Jun-01-2021)
- Release Version 1.63 (May-19-2021)
- Release Version 1.62 (May-05-2021)
- Release Version 1.61 (Apr-20-2021)
- Release Version 1.60 (Apr-06-2021)
- Release Version 1.59 (Mar-23-2021)
- Release Version 1.58 (Mar-09-2021)
- Release Version 1.57 (Feb-22-2021)
- Release Version 1.56 (Feb-09-2021)
- Release Version 1.55 (Jan-25-2021)
- Release Version 1.54 (Jan-12-2021)
- Release Version 1.53 (Dec-22-2020)
- Release Version 1.52 (Dec-03-2020)
- Release Version 1.51 (Nov-10-2020)
- Release Version 1.50 (Oct-19-2020)
- Release Version 1.49 (Sep-28-2020)
- Release Version 1.48 (Sep-01-2020)
- Release Version 1.47 (Aug-06-2020)
- Release Version 1.46 (Jul-21-2020)
- Release Version 1.45 (Jul-02-2020)
- Release Version 1.44 (Jun-11-2020)
- Release Version 1.43 (May-15-2020)
- Release Version 1.42 (Apr-30-2020)
- Release Version 1.41 (Apr-2020)
- Release Version 1.40 (Mar-2020)
- Release Version 1.39 (Feb-2020)
- Release Version 1.38 (Jan-2020)
- Upcoming Features
Amazon Aurora PostgreSQL
On This Page
- Set up Log-based Incremental Replication
- Whitelist Hevo’s IP Addresses
- Grant Privileges to the User
- Specify Amazon Aurora PostgreSQL Connection Settings
- Object Settings
- Source Considerations
- Revision History
Amazon Aurora PostgreSQL is a fully managed, PostgreSQL-compatible relational database engine that combines the speed and reliability of high-end commercial databases with the simplicity and cost-effectiveness of open-source databases. Its enterprise database capabilities combined with compatibility with PostgreSQL helps deliver throughput that is much higher compared to the standard PostgreSQL running on the same hardware.
You can ingest data from your Amazon Aurora PostgreSQL database using Hevo Pipelines and replicate it to a Destination of your choice.
IP address or host name of your PostgreSQL server is available.
The PostgreSQL version is 9.6 or higher.
If ingestion mode is Logical Replication:
The database that you are connecting is a master instance. Amazon Aurora PostgreSQL does not support logical replication on read replicas.
Perform the following steps to configure your Amazon Aurora PostgreSQL Source:
Set up Log-based Incremental Replication
1. Create a parameter group
Open the Amazon RDS console.
In the left navigation pane, select Parameter groups.
Click Create parameter group.
Select the instance with Type as DB cluster parameter group.
Example: postgresql cluster parameter group
Specify the required fields and click Create.
2. Configure the parameters
For the parameter group you just created:
Click Edit parameters in the top right.
Search and update the following parameters:
Parameter Value Description
5 The number of clients that can connect to the server. Default value: 10. RDS recommends to set this value to at least 5 so that internal replication by RDS is not affected.
1 The setting to enable or disable logical replication. The value of 1 is required to enable write-ahead logging (WAL) at the logical level.
0 The time, in seconds, after which PostgreSQL terminates the replication connections due to inactivity. Default value: 60 seconds. You must set the value to 0 so that the connections are never terminated and your Pipeline does not fail.
You can use the following query to check the value configured for the parameter:
3. Apply the parameter group to your PostgreSQL database
In your Amazon RDS console, click Databases in the left navigation pane.
In the Databases page, click the DB identifier for your database, and the, Modify.
Select the DB cluster parameter group you just created.
Set the backup retention period to at least 3 days. This setting defines the number of days for which automated backups are retained.
For your settings to take affect, reboot the DB instance.
Whitelist Hevo’s IP Addresses
You need to whitelist the Hevo IP addresses for your region to enable Hevo to connect to your PostgreSQL database.
To do this:
1. Add inbound rules
Open the Amazon RDS console.
In the left navigation pane, click Databases (or Instances if you’re using an older version).
In the Databases section on the right, click the DB identifier of the Amazon Aurora instance to configure a security group on.
In the Connectivity & security tab, click the link text under Security, VPC security groups.
In the Actions drop-down on the top right, click Edit inbound rules.
In the Edit inbound rules page:
Click Add rule.
Add a new rule with Hevo’s IP addresses for your region to give access to the PostgreSQL instance.
Click Save rules.
2. Configure Virtual Private Cloud (VPC)
In the Amazon RDS console, click the VPC link text.
In the Your VPCs page, click on the VPC ID, and then, the Network ACL link.
Click the Inbound Rules tab and ensure that the IP addresses you added have a setting of ALLOW.
Grant Privileges to the User
Grant privileges to the database user connecting to the PostgreSQL database as follows:
Log into your Amazon Aurora PostgreSQL database as a user with
Enter the following commands to give accesses to the database user:
GRANT CONNECT ON DATABASE <database_name> TO <database_username>; GRANT USAGE ON SCHEMA <schema_name> TO <database_username>; GRANT SELECT ON DATABASE <database_name> TO <database_username>;
Alter the schema’s default privileges to grant
SELECTprivileges on tables to the database user:
ALTER DEFAULT PRIVILEGES IN SCHEMA <schema_name>; GRANT SELECT ON TABLES TO <database_username>;
Note: If you want to use Log-based Incremental Replication, grant the
rds_replicationrole to the database user. Log in to the database as a user with the
rds_superuserrole and run the following command:
GRANT rds_replication TO <database_username>;
Specify Amazon Aurora PostgreSQL Connection Settings
In the Configure your Amazon Aurora PostgreSQL Source page, specify the following:
Pipeline Name: A unique name for your Pipeline.
Database Host: The Amazon Aurora PostgreSQL host’s IP address or DNS.
Database Port: The port on which your PostgreSQL server is listening 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.
For Ingestion mode as Table, Refer to section, Object Settings for steps to configure the objects to be replicated.
For Ingestion mode as Logical Replication, follow the steps provided in each PostgreSQL variant document to set up logical replication.
Note: PostgreSQL does not support logical replication for the read replica.
Database Name: The database that you wish to replicate.
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).
Client Certificate: The client public key certificate file.
Client Key: The client private key file.
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, in the Pipeline Overview page. You can update their status to INCLUDED to ingest data. You can change this setting later.
Click TEST & CONTINUE to proceed for setting up the Destination.
Object settings must be configured if the Ingestion mode is Table.
To do this:
Once your respective Source connection settings are specified as per section Specify Amazon Aurora PostgreSQL Connection Settings above, select the objects to be replicated in the SELECT the Objects you want to replicate page, and then click CONTINUE.
Note: Each object represents a table in your database.
In the CONFIGURE SOURCE OBJECTS page, specify the query mode to be used for each selected object.
- Amazon Aurora PostgreSQL does not support Logical Replication on read replicas. To enable log-based replication, select a master database instance.
- The data type Array in the Source is automatically mapped to Varchar at the Destination. No other mapping is currently supported.
Refer to the following table for the list of key updates made to this page:
|Date||Release||Description of Change|
|Jul-04-2022||NA||- Added sections, Specify Amazon Aurora PostgreSQL Connection Settings and Object Settings.|
|Apr-25-2022||NA||- Added section, Source Considerations.
- Added a prerequisite for connecting to a master database if logical replication is required.
|Feb-07-2022||1.81||Updated section, Whitelist Hevo’s IP Address to remove details about Outbound rules as they are not required.|
|Jan-24-2022||1.80||Removed from Limitations that Hevo does not support UUID datatype as primary key.|
|Dec-20-2021||1.78||Updated section, Configure the parameters.|
|Sep-09-2021||1.71||Updated the section, Limitations to include information about columns with the UUID data type not being supported as a primary key.|
|Jun-14-2021||1.65||Updated the Grant Privileges to the User section to include latest commands.|