Skip to main content
Edit this page

RDS Postgres Source Setup Guide

Supported Postgres versions​

ClickPipes supports Postgres version 12 and later.

Enable Logical Replication​

You can skip this section if your RDS instance already has the following settings configured:

  • rds.logical_replication = 1
  • wal_sender_timeout = 0

These settings are typically pre-configured if you previously used another data replication tool.

Checking if logical replication is already enabled

If not already configured, follow these steps:

  1. Create a new parameter group for your Postgres version with the required settings:

    • Set rds.logical_replication to 1
    • Set wal_sender_timeout to 0

    Where to find Parameter groups in RDS?

    Changing rds.logical_replication

    Changing wal_sender_timeout

  2. Apply the new parameter group to your RDS Postgres database

    Modifying RDS Postgres with new parameter group

  3. Reboot your RDS instance to apply the changes

    Reboot RDS Postgres

Configure Database User​

Connect to your RDS Postgres instance as an admin user and execute the following commands:

  1. Create a dedicated user for ClickPipes:

    CREATE USER clickpipes_user PASSWORD 'some-password';

  2. Grant schema permissions. The following example shows permissions for the public schema. Repeat these commands for each schema you want to replicate:

    GRANT USAGE ON SCHEMA "public" TO clickpipes_user;
    GRANT SELECT ON ALL TABLES IN SCHEMA "public" TO clickpipes_user;
    ALTER DEFAULT PRIVILEGES IN SCHEMA "public" GRANT SELECT ON TABLES TO clickpipes_user;

  3. Grant replication privileges:

    GRANT rds_replication TO clickpipes_user;

  4. Create a publication for replication:

    CREATE PUBLICATION clickpipes_publication FOR ALL TABLES;

Configure Network Access​

IP-based Access Control​

If you want to restrict traffic to your RDS instance, please add the documented static NAT IPs to the Inbound rules of your RDS security group.

Where to find security group in RDS Postgres?

Edit inbound rules for the above security group

To connect to your RDS instance through a private network, you can use AWS PrivateLink. Follow our AWS PrivateLink setup guide for ClickPipes to set up the connection.

Workarounds for RDS Proxy​

RDS Proxy does not support logical replication connections. If you have dynamic IP addresses in RDS and cannot use DNS name or a lambda, here are some alternatives:

  1. Using a cron job, resolve the RDS endpoint’s IP periodically and update the NLB if it has changed.
  2. Using RDS Event Notifications with EventBridge/SNS: Trigger updates automatically using AWS RDS event notifications
  3. Stable EC2: Deploy an EC2 instance to act as a polling service or IP-based proxy
  4. Automate IP address management using tools like Terraform or CloudFormation.

What's next?​

You can now create your ClickPipe and start ingesting data from your Postgres instance into ClickHouse Cloud. Make sure to note down the connection details you used while setting up your Postgres instance as you will need them during the ClickPipe creation process.