> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/concepts/resources/depot/supported-sources/snowflake.md). # Snowflake To create a Snowflake Depot you must have the following details: ## Pre-requisites specific to DataOS To create a Depot, you need the Data Admin role. Contact the DataOS Operator or Tenant Admin to get it. Run this command to see your assigned roles. ```bash dataos-ctl user get #Expected Output: time="2026-03-30T17:49:18+05:30" level=info msg="😃 user get..." time="2026-03-30T17:49:19+05:30" level=info msg="😃 user get...complete" NAME │ ID │ TYPE │ EMAIL │ TAGS ──────────────┼───────────────────┼────────┼──────────────────────┼──────────────────────────────────────── I Am Groot │ iamgroottmdcio │ person │ iam.groot@tmdc.io │ roles:id:ct-onboarding-data-developer, │ │ │ │ roles:id:data-dev, │ │ │ │ roles:id:system-dev, │ │ │ │ roles:id:user, │ │ │ │ users:id:iamgroottmdcio ``` ## Pre-requisites specific to the source system * **Snowflake Account URL**: The unique URL used to access your Snowflake account, typically in the format `https://.snowflakecomputing.com`. You can retrieve this from your Snowflake admin or find it in your Snowflake login credentials email. * **Snowflake Account Identifier**: The unique identifier assigned to the Snowflake account, usually consisting of letters and numbers. Obtain this information from the Snowflake admin or check it in the Snowflake account details. * **Warehouse**: The name of the warehouse in Snowflake that you require access to. Locate this information in the Snowflake console under Warehouses or consult the team responsible for managing the Snowflake environment. * **Database**: The name of the database in Snowflake that you need to connect to. You can find this in the Snowflake console under the Databases section or by consulting the team managing the Snowflake environment. * **Schema (optional)**: The specific schema within the Snowflake database where your required table resides. This can also be found in the Snowflake console under the relevant database or provided by the team managing the database structure. * **Snowflake Role**: The role that defines the privileges and access control for the Snowflake user. While this attribute is optional in the Depot manifest, it is highly recommended to specify it to ensure proper access permissions and security. If no role is defined, the system will take "PUBLIC" as the default role. ## Create a Snowflake Depot A Depot reads data from Snowflake tables without copying the data into DataOS. Snowflake is a SaaS cloud data warehouse with a SQL engine built for cloud infrastructure. To create a Depot of type `snowflake`, follow these steps: ### **Step 1: Create a Secret for securing Snowflake credentials** Create a Secret Resource using the [Snowflake](/concepts/resources/secret/data-sources/snowflake.md) guide. ### **Step 2: Create a Snowflake Depot manifest file** Create a manifest file for your Snowflake Depot. Reference the Secret by name in the Depot manifest as shown in the template below. {% tabs %} {% tab title="Manifest file" %} ```yaml name: ${{snowflake-name}} version: v2alpha type: depot tags: - Snowflake - depot - warehouse description: "Snowflake cloud data warehouse depot for data storage and analytics" spec: type: snowflake spec: url: ${{snowflake-url}} database: ${{snowflake-database}} warehouse: ${{snowflake-warehouse}} secrets: - id: "${{tenant-id}}:${{snowflake-secret-name}}" purpose: scan ``` {% endtab %} {% tab title="Example" %} ```yaml name: ${{snowflake-name}} version: v2alpha type: depot tags: - Snowflake - depot - warehouse description: "Snowflake cloud data warehouse depot for data storage and analytics" spec: type: snowflake spec: url: ${{snowflake-url}} database: ${{snowflake-database}} warehouse: ${{snowflake-warehouse}} secrets: - id: "${{tenant-id}}:${{snowflake-secret-name}}" purpose: scan ``` {% endtab %} {% endtabs %} ### **Step 3: Apply the Depot manifest file** Apply the manifest with the DataOS CLI: ```bash dataos-ctl resource apply -f ${{manifest-file-path}} ``` ## Verify the Depot creation Verify the Depot in two ways: * List Depots where you are the owner: ```bash dataos-ctl resource get -t depot ``` * List all Depots in the current Tenant: ```bash dataos-ctl resource get -t depot -a ``` ## Delete a Depot {% hint style="warning" %} Best practice: Delete Resources that are no longer in use to save time and reduce costs. {% endhint %} To delete a Depot, use the DataOS CLI: {% tabs %} {% tab title="Command 1" %} ```bash dataos-ctl resource delete -t depot -n ${{name}} ``` {% endtab %} {% tab title="Command 2 " %} ```bash dataos-ctl resource delete -i "${{resource-name}}|v2alpha|depot" ``` {% endtab %} {% tab title="Command 3" %} ```bash dataos-ctl resource delete -f ${{manifest-file-path}} ``` {% endtab %} {% endtabs %} Specify the Resource type and Depot name in the `delete` command. **Example:** {% tabs %} {% tab title="Command 1" %} ```bash dataos-ctl resource delete -t depot -n testdepot #output time="2026-03-25T15:53:55+05:30" level=info msg="🗑 delete..." time="2026-03-25T15:53:55+05:30" level=info msg="🗑 deleting testdepot:v2alpha:depot..." time="2026-03-25T15:53:56+05:30" level=info msg="🗑 deleting testdepot:v2alpha:depot...deleted" time="2026-03-25T15:53:56+05:30" level=info msg="🗑 delete...complete" time="2026-03-25T15:53:56+05:30" level=info msg="🗑 delete...complete" ``` {% endtab %} {% tab title="Command 2" %} ```bash dataos-ctl resource delete -i "testdepot|v2alpha|depot" #output time="2026-03-25T15:55:37+05:30" level=info msg="🗑 delete..." time="2026-03-25T15:55:37+05:30" level=info msg="🗑 deleting testdepot:v2alpha:depot..." time="2026-03-25T15:55:37+05:30" level=info msg="🗑 deleting testdepot:v2alpha:depot...deleted" time="2026-03-25T15:55:37+05:30" level=info msg="🗑 delete...complete" ``` {% endtab %} {% tab title="Command 3" %} ```bash dataos-ctl resource delete -f /path/to/depot.yaml #output time="2026-03-25T15:53:55+05:30" level=info msg="🗑 delete..." time="2026-03-25T15:53:55+05:30" level=info msg="🗑 deleting testdepot:v2alpha:depot..." time="2026-03-25T15:53:56+05:30" level=info msg="🗑 deleting testdepot:v2alpha:depot...deleted" time="2026-03-25T15:53:56+05:30" level=info msg="🗑 delete...complete" ``` {% endtab %} {% endtabs %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://v2.dataos.info/concepts/resources/depot/supported-sources/snowflake.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.