> ## Documentation Index
> Fetch the complete documentation index at: https://docs.domino.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect a Data Source

Model monitoring ingests and processes a model’s training, prediction, and ground truth data to monitor the model. You must set up the data source from which the data is read. After you set up the data source, it is available to all users and can be used in any model.

You can have multiple data sources linked to the model monitor, and multiple instances for each data source type.

<Note>
  Enable **read** and **list** access for each data source.
</Note>

The Model Monitor supports data from the following sources:

* Amazon S3

* Generic S3

* Azure Blob

* Azure Data Lake Gen 1

* Azure Data Lake Gen 2

* Google Cloud Storage

* HDFS

* Snowflake

## Connect a Data Source

1. If you haven’t set up a data source, go to the **Data** page (from the navigation pane, go to **Model Monitor > Monitoring Data Sources**).

2. Click **Add Data Source**.

3. Complete the details as needed. The following describes source-specific configurations:

   <table>
     <thead>
       <tr>
         <th>Data source</th>
         <th>Required fields</th>
         <th>Authentication</th>
       </tr>
     </thead>

     <tbody>
       <tr>
         <td><p>Amazon S3</p></td>
         <td><p>Data Source Name</p> <p>S3 Bucket Name</p> <p>S3 Region</p></td>
         <td><p>If the S3 buckets can be authenticated to using IAM roles, select the <strong>Load Credentials from IAM Role</strong> attached to the instance checkbox.</p> <p>Enter an <strong>AWS Access Key</strong> and an <strong>AWS Secret Key</strong>.</p></td>
       </tr>

       <tr>
         <td><p>Generic S3</p></td>
         <td><p>Data Source Name</p> <p>S3 Bucket Name</p> <p>S3 Endpoint</p></td>
         <td><p>Enter an <strong>Access Key</strong> and a <strong>Secret Key</strong>.</p></td>
       </tr>

       <tr>
         <td><p>Azure Blob Store</p></td>
         <td><p>Data Source Name</p> <p>Account name</p> <p>Container</p></td>
         <td><p>Access Key</p> <p>Saas Token</p></td>
       </tr>

       <tr>
         <td><p>Azure Data Lake Gen 1</p></td>
         <td><p>Data Source name</p> <p>Container</p></td>
         <td><p>Select the <strong>Authentication Type</strong>:</p> <ol> <li><p>If you select <strong>Client Credentials</strong>, enter:</p> <ul> <li><p>Token Endpoint</p></li> <li><p>Application ID</p></li> <li><p>Secret Key</p></li> </ul></li> <li><p>If you select <strong>Managed Identity</strong> , you can enter an optional <strong>Port Number</strong>.</p></li> </ol> <p>This method applies when the Model Monitor is deployed on Azure VMs configured with service identities that can access Azure Data Lake.</p></td>
       </tr>

       <tr>
         <td><p>Azure Data Lake Gen 2</p></td>
         <td><p>Data Source name</p> <p>Account Name</p> <p>Container</p></td>
         <td><p>Select the <strong>Authentication Type</strong>:</p> <ol> <li><p><strong>Shared Key</strong>.</p></li> <li><p><strong>Client Credentials</strong>. Then, enter:</p> <ul> <li><p><strong>Endpoint</strong></p></li> <li><p><strong>Client ID</strong></p></li> <li><p><strong>Client Secret</strong></p></li> </ul></li> <li><p><strong>Username Password</strong>. Then, enter:</p> <ul> <li><p><strong>Endpoint</strong></p></li> <li><p><strong>Username</strong></p></li> <li><p><strong>Password</strong></p></li> </ul></li> <li><p><strong>Refresh Token</strong>. Then, enter:</p> <ul> <li><p><strong>Refresh Token</strong></p></li> <li><p><strong>Client ID</strong></p></li> </ul></li> <li><p><strong>Managed Identity</strong>. This method applies when the Model Monitor has been deployed on Azure VMs configured with service identities that can access Azure Data Lake Gen2. Then, you can enter the following optional information:</p> <ul> <li><p><strong>Tenant ID</strong></p></li> <li><p><strong>Client ID</strong></p></li> </ul></li> </ol></td>
       </tr>

       <tr>
         <td><p>Google Cloud Storage</p></td>
         <td><p>Data Source Name</p> <p>Bucket</p></td>
         <td><p>JSON Key File</p></td>
       </tr>

       <tr>
         <td><p>HDFS</p></td>
         <td><p>Data Source Name</p> <p>Host</p> <p>Port (optional)</p></td>

         <td />
       </tr>

       <tr>
         <td><p>Snowflake</p></td>
         <td><p>All fields</p></td>
         <td><p>Enter the following:</p> <ol> <li><p><strong>Account URL</strong> which uniquely identifies the Snowflake account in your organization.</p></li> <li><p>Enter your <strong>Username</strong> and <strong>Password</strong>.</p></li> <li><p>In <strong>Database</strong>, enter the name of the Snowflake database that contains the data.</p></li> <li><p>In <strong>Schema</strong>, enter the name of the active schema for the session.</p></li> <li><p>In <strong>Warehouse</strong>, enter the name of a compute resource cluster that provides the resources in Snowflake.</p></li> <li><p>Select a <strong>Role</strong>.</p>&#x20;
         &#x20;<p>All fields must match Snowflake’s requirements for <a href="https://docs.snowflake.com/en/sql-reference/identifiers-syntax.html">object identifiers</a>.</p> </li> </ol></td>
       </tr>
     </tbody>
   </table>

4. Click **Add**.