Set up Openflow - Snowflake Deployment - Task overview¶
To setup an Openflow - Snowflake Deployment, perform the following tasks:
Gen 2 setup path
Gen 2 is recommended for new setups. The steps below cover both generations. New to gen 2? See the gen 2 Openflow quickstart for a streamlined SQL-first walkthrough.
| Order | Task | Description | Persona |
|---|---|---|---|
| 1 | Setup core Snowflake | Before creating a deployment, you must configure core Snowflake which include an Openflow admin role, required privileges, and network configuration. | Snowflake administrator |
| 2 | Optionally Set up PrivateLink UI access | Configure PrivateLink to access the Snowflake Openflow Runtime UI using private connectivity. | Snowflake administrator |
| 3 | Create deployment | After configuring core Snowflake, you then create an Openflow deployment.
Gen 2 uses Optionally, configure an Openflow-specific event table to store Openflow logs and metrics. | Deployment engineer, Snowflake administrator for event table configuration |
| 4 | Create the execute-as role and external access integrations | Create the role that connectors use to access Snowflake resources. This is called the execute-as role. Both require external access integrations for Snowflake deployments. | Data engineer |
| 5 | Create runtime | Create a runtime associated with the previously created role.
Gen 2 uses | Data engineer |
| 6 | Configure allowed domains for Openflow connectors | Configure access to external domains for Openflow connectors. | Data engineer |
| 7 | Connect your data sources using Openflow connectors | Configure one or more connectors in the Openflow - Snowflake Deployment. Gen 2 connectors can be created with SQL
( | Data engineer |
Note that step 3 (deployment creation) is typically done once. Steps 4 and 5 (role and runtime creation) are repeated for each runtime you add to the deployment.