Configure source and target connectors

Configure connectors while creating or editing a pipeline. The Control Plane calls the running connector process an agent; most users only need to choose the technology and enter its connection settings.

Before you start

Open the guide for the connector you plan to use. Source connectors often need CDC permissions, transaction-log settings, or database objects prepared before the Control Plane can test the connection.

You also need:

  • Network connectivity from the agent host to the database or service.

  • A dedicated database account with the permissions listed by the connector guide.

  • Access to Modules Manager when the connector must be deployed from the Control Plane.

Configure a connector

  1. Create a pipeline, or open an existing pipeline and choose Edit pipeline.

  2. Open Setup source or Setup target(s).

  3. Select the connector technology.

  4. If the technology has several capture methods, select the required flavor.

  5. Choose an available agent or deploy a new one.

  6. Enter the connection fields under Base settings.

  7. Use Advanced settings only when the connector guide requires a non-default value.

  8. Select Test and continue.

The test verifies that the process is reachable and that its connection configuration is accepted. It cannot prove that every CDC permission or future target write will succeed, so complete the connector-specific validation too.

Name agents clearly

The name appears in pipeline configuration, Query Studio, metrics, logs, and support bundles. Include the technology, environment, and role:

  • postgres-orders-prod-source

  • snowflake-analytics-prod-target

  • mongodb-catalog-staging-source

Avoid names such as agent-1 or database, which make incidents harder to diagnose.

Replace a connector

  1. Take a configuration backup.

  2. Put the pipeline in maintenance mode.

  3. Choose Edit source or Edit target from the pipeline menu.

  4. Select or deploy the replacement agent.

  5. Configure and test it.

  6. Save the pipeline, exit maintenance mode, and verify the affected entities.

Replacing a connector does not automatically prove checkpoint compatibility. Review the source connector’s CDC and recovery guidance before resuming an existing stream.

If deployment is unavailable

The Control Plane can deploy connectors only when Modules Manager and its supporting service are connected and your role permits the action. Otherwise, ask the platform administrator to deploy the required agent, then return to the wizard and select it.

See Modules Manager for component deployment and updates.

Troubleshoot

Connector missing

Confirm that it supports the required source or target role and that your license includes it.

Deployment does not start

Check Modules Manager health, registry connectivity, and available host resources.

Connection test fails

Verify hostnames from the agent’s network, not from your browser. In a container deployment, localhost points to the agent container.

Test passes but CDC fails

Recheck the source preparation, database permissions, and logs in the connector-specific guide.