DBT Core

OvalEdge uses an S3 Bucket or NFS Path to connect to the data source, which allows users to crawl manifest files and build lineage.

Overview

Connector Details

Connector Category	ETL System
OvalEdge Release Current Connector Version	6.3.4
Connectivity [How OvalEdge connects to DBT Core]	S3 Bucket/NFS
OvalEdge Releases Supported (Available from)	Release6.x Onwards

Connector Features

Crawling of Metadata Objects	Supported
Metadata Preview	Supported
Lineage	Supported
Lineage	Lineage Levels Supported
Lineage	Table Lineage Column Lineage
Authentication via Credential Manager	Supported
Data Quality	Not Supported
DAM (Data Access Management)	Not Supported
Bridge	Supported

Getting Ready to Establish a Connection

Prerequisites

The following are the prerequisites required for establishing a connection:

Service Account User Permissions

Important: We recommend having a separate service account to establish a connection from OvalEdge to the data source with minimal permissions.

Operations	Minimum Permissions
Connection Validation	Read Only Access
Crawl Objects	Read Only Access

Setup a Connection

Important: You must have the Connector Creator role to set up a connection in OvalEdge.

1. Log into OvalEdge, go to Administration > Connectors, click + (New Connector), search for DBT Core, and complete the specific parameters.

Note: Fields marked with an asterisk (*) are mandatory for establishing a connection.

Field Name	Description
Connector Type	By default, "DBT Core" is displayed as the selected connector type.
Connector Settings
Credential Manager*	Select the desired credentials manager from the dropdown list. Relevant parameters will be displayed based on your selection. Supported Credential Managers: OE Credential Manager HashiCorp Vault AWS Secrets Manager Azure Key Vault
License Add Ons	OvalEdge connectors have a default license add-on for data crawling and profiling. Select the checkbox for Auto Lineage Add-On to build data lineage automatically.
Connector Environment	Select the environment (Example: PROD, STG) configured for the connector.
Connector Name*	Enter a unique name for the DBT Core connection. (Example: "DBTCore_Prod").
DBT Core Repository type*	Choose the appropriate option from the drop-down list. NFS S3 If you select NFS from the drop-down list, enter the following: Path*: Enter the path where the DBT Project resides. If you select S3 from the drop-down list, enter the following: Authentication*: IAM user authentication in Amazon S3 securely controls access to AWS services using AWS Identity and Access Management (IAM). Role-based authentication (RBAC) in Amazon S3 grants access to an S3 bucket using an AWS role instead of access/secret keys. Note: Role-based Authentication is not supported in DBT Core for S3. S3 Bucket name*: Enter the name of the S3 bucket where DBT resides. S3 zip pathname name: Enter the path name where the zip file was extracted from the manifest file in the project folder. Access key*: Enter a unique identifier that is part of the credential pair, like a username. Note: This Field is available when the Authentication mechanism is selected as "IAM User Authentication." Secret key*: A secret, like a password, is used to sign requests to AWS. Note: This Field is available when the Authentication mechanism is selected as "IAM User Authentication." Filter by tags: Specify tags as filters to limit the scope of objects the connector will interact with. Example: ovaledge=9,region=ohio,region=oregon Region: The Region refers to the specific geographical location where your Amazon S3 bucket resides. Example: us-east-1 SSO Connection Id: The SSO connection ID is used to authenticate and authorize access to Amazon S3. SSO Application Id: This specific application ID within the SSO system connects to Amazon S3. SSO Role Prefix: Specifies the roles in the SSO system that have access to Amazon S3 and manage permissions. RDAM Policy Folder Path: Enter the Bucket/Folder path in the S3 to write the policies.
Default Governance Roles
Default Governance Roles*	Select the appropriate users or teams for each governance role from the dropdown list. All users and teams configured in OvalEdge Security are displayed for selection.
Admin Roles
Admin Roles*	Select one or more users from the dropdown list for Integration Admin and Security and Governance Admin. All users configured in OvalEdge Security are available for selection.
No Of Archive Objects*	It indicates the number of recent metadata changes to a dataset at the source. By default, it is off. You can enable it by toggling the Archive button and specifying the number of objects to archive. Example: Setting it to 4 retrieves the last four changes, shown in the 'version' column of the 'Metadata Changes' module.
Bridge
Select Bridge*	If applicable, select the bridge from the drop-down list. The drop-down list displays all active bridges configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without altering firewall rules.

1. After entering all connection details, you can perform the following actions:

   1. Click Validate to verify the connection.

   2. Click Save to store the connection for future use.

   3. Click Save & Configure to apply additional settings before saving.

2. The saved connection will appear on the Connectors home page.

Connectivity Troubleshooting

If incorrect parameters are provided, you may encounter error messages. To resolve these issues, ensure all input is correct. If problems persist, contact your assigned OvalEdge support team.

S. No.	Error Description	Resolution
1	Failed to establish a connection, Please check the credentials	Provide valid credentials or ensure proper access.
2	An error occurred while validating the DBT Core connection.	403: Access denied [Provide appropriate access to user or role using in connection] 404: No such key [The object does not exist in the remote.]

Manage Connector Operations

Crawl/Profile

Important: You must have the Integration Admin role in OvalEdge for crawl/profile operations.

Crawl and Profile operations allow you to choose one or more schemas from a list of all available schemas within a specific database. This customization enables you to tailor the selection of crawling operations to meet your needs. Additionally, it offers the option to schedule crawls.

Other Operations

The Connectors page in OvalEdge provides a centralized view of all configured connectors, including their health status. You can view, edit, validate, build lineage, and delete connectors using the Nine Dots menu.

Managing connectors includes:

• Connectors Health: Displays performance with a green (active) or red (inactive) icon, helping monitor data flow and address issues early.

• Viewing: Shows connector details (e.g., Databases, Tables, Table Columns, and Codes) via the View icon.

Nine Dots Menu Options:

• Edit Connector: Update and revalidate the data source.

• Validate Connector: Check the connection's integrity.

• Settings: Modify connector settings.

  • Lineage: The lineage settings are enabled by default, allowing you to select multiple sources for lineage building. Choose server dialects for parsing source codes, ensuring at least one is selected. Configure table priority to specify the order in which tables with the same name or signature are considered for lineage.

• Build Lineage: Automatically build data lineage using SQL logs and source code parsing.

• Delete Connector: Remove connectors or schemas with confirmation.

Additional Information

NFS Configuration

• If the DBT Core Repository type is set to NFS, the NFS path is required.

• The parent folder (dbt_artifactory) must contain only DBT folders.

S3 Configuration

• The S3 bucket name must not include slashes (/ or \). Only the bucket name is required.

• The manifest.json file must exist in the target folder.

---

Copyright © 2025, OvalEdge LLC, Peachtree Corners GA USA