AWS Aurora PostgreSQL Guide

Use this page when DBConvert Streams connects to an Aurora PostgreSQL cluster.

This guide focuses on the Aurora-specific parts of the setup:

• cluster endpoint and network access
• cluster parameter-group changes for logical replication
• TLS certificate handling

For the core workflow split, use:

• PostgreSQL Server Configuration
• PostgreSQL CDC Source Configuration

Base setup

1. Open the AWS RDS console.
2. Select the Aurora PostgreSQL cluster and note the endpoint you intend to use.
3. Confirm the DBConvert Streams deployment can reach the cluster on port 5432.
4. Confirm the selected user has the minimum privileges required for the workflow.

Network and TLS

Typical checks:

• the Aurora security group allows inbound traffic from the DBConvert Streams host or VPC path
• the selected endpoint is reachable from the deployment network
• TLS certificate validation is configured if your environment requires it

To validate TLS with the public RDS CA bundle:

wget https://truststore.pki.rds.amazonaws.com/global/global-bundle.pem -O rds-ca.pem

Then use that CA in the DBConvert Streams connection if certificate verification is enabled.

CDC source preparation

Aurora PostgreSQL CDC uses logical replication, with the Aurora-specific control living in the cluster parameter group.

Required Aurora setting:

Typical flow:

1. Create or edit the Aurora cluster parameter group.
2. Set rds.logical_replication = 1.
3. Attach the parameter group to the cluster if needed.
4. Reboot the cluster when AWS marks the change as pending reboot.

After reboot, verify:

SHOW wal_level;

SELECT name, setting
FROM pg_settings
WHERE name IN (
  'wal_level',
  'max_replication_slots',
  'max_wal_senders',
  'rds.logical_replication'
);

Then finish the DBConvert Streams side of the CDC setup with PostgreSQL CDC Source Configuration.

Validation checklist

1. Test the Aurora PostgreSQL connection from the Data Explorer sidebar (right-click → Test connection) or from the connection editor.
2. Open it in Data Explorer to confirm visible schemas and tables.
3. If the workflow uses CDC, run SHOW wal_level and confirm it returns logical. If it still shows replica, the cluster parameter group change has not propagated — reboot the cluster.
4. Verify max_replication_slots is greater than zero to confirm the cluster can accept replication connections.

Related docs

• PostgreSQL Server Configuration
• PostgreSQL CDC Source Configuration