Amundsen Connector | Collate Metadata Services

Connect Amundsen to Collate effortlessly with our comprehensive connector guide. Step-by-step setup, configuration tips, and metadata integration b…

Metadata Ingestion

Connection Details

1. Connection Details

   When using a Hybrid Ingestion Runner, any sensitive credential fields—such as passwords, API keys, or private keys—must reference secrets using the following format:

   password: secret:/my/database/password
   

   This applies only to fields marked as secrets in the connection form (these typically mask input and show a visibility toggle icon). For a complete guide on managing secrets in hybrid setups, see the Hybrid Ingestion Runner Secret Management Guide.

   • username: Enter the username of your Amundsen user in the Username field. The specified user should be authorized to read all databases you want to include in the metadata ingestion workflow.
   • password: Enter the password for your amundsen user in the Password field.
   • hostPort: Host and port of the Amundsen Neo4j Connection. This expect a URI format like: bolt://localhost:7687.
   • maxConnectionLifeTime (optional): Maximum connection lifetime for the Amundsen Neo4j Connection
   • validateSSL (optional): Enable SSL validation for the Amundsen Neo4j Connection.
   • encrypted (Optional): Enable encryption for the Amundsen Neo4j Connection.
2. Test the Connection

   Once the credentials have been added, click on Test Connection and Save the changes.

   
3. Configure Metadata Ingestion

   In this step we will configure the metadata ingestion pipeline, Please follow the instructions below

   
4. Schedule the Ingestion and Deploy

   Scheduling can be set up at an hourly, daily, weekly, or manual cadence. The timezone is in UTC. Select a Start Date to schedule for ingestion. It is optional to add an End Date.

   Review your configuration settings. If they match what you intended, click Deploy to create the service and schedule metadata ingestion.

   If something doesn’t look right, click the Back button to return to the appropriate step and change the settings as needed.

   After configuring the workflow, you can click on Deploy to create the pipeline.

   
5. View the Ingestion Pipeline

   Once the workflow has been successfully deployed, you can view the Ingestion Pipeline running from the Service Page.

   

   If AutoPilot is enabled, workflows like usage tracking, data lineage, and similar tasks will be handled automatically. Users don’t need to set up or manage them - AutoPilot takes care of everything in the system.