Objects that Use Connections

When you export objects that use connections or objects with dependent objects that use connections, Control Hub exports the connection metadata only. The metadata includes the connection ID, name, and type. Control Hub does not export the connection credentials or other configured values.

For example, when you export a pipeline that uses a connection, Control Hub exports the connection ID, name, and type used by that pipeline. When you export a job with multiple pipelines that use connections, Control Hub exports the connection ID, name, and type of all connections used by each pipeline.

To import objects that use connections, the connections must already exist in the target organization. During the import, Control Hub first attempts to find matching connections by ID, and then by name and type. If any connections do not exist, then pipelines using those missing connections fail to import. Pipelines using existing connections import successfully.

For example, if you export a pipeline that uses an Amazon S3 connection named SourceData, you can import the pipeline only when the target organization also includes an Amazon S3 connection named SourceData.

Tip: When migrating objects from one organization to another organization, create connections with the same name and type in the target organization before you import the objects.