About Openflow: BYOC deployments¶
Openflow BYOC _is_ Openflow and contains all the benefits of Openflow, but within your existing cloud.
Typical BYOC workflow¶
User persona |
Task |
|---|---|
AWS cloud engineer/administrator |
Creates a set of deployments in their AWS cloud account. The Openflow UI is used to manage deployments and runtime creation and maintenance. The Openflow UI allows users to create, resize, upgrade, and delete runtimes in all deployments. Snowflake sign-ins are used to authenticate to Openflow, and roles and privileges are used to control access to Openflow deployments and runtimes. |
Data engineer (pipeline author, responsible for data ingestion) |
Uses the runtime canvas to build completely new flows or to configure deployed connectors. Creates a completely new flow or uses an existing connector as-is or as a starting point to customize. Populates data in the bronze layer within your Snowflake account (or other target system). Connectors are a simple way to solve for a specific integration use case, and less technical users can deploy them without necessarily needing a data engineer. |
Data engineer (pipeline operator) |
Configures the flow parameters and runs the flow. |
Data engineer (responsible for transformation to silver and gold layers) |
Responsible for transforming data from the bronze layer that was populated by the pipeline to silver and gold layers for analytics. |
Business user |
Makes use of gold layer objects for analytics. |
Limitations¶
Openflow - Snowflake Deployment is not supported in trial accounts.
Only a single|OFSFSPCS| is supported per account. However, an account can have many Openflow - Snowflake Deployment runtimes — each having a separate role and network access — which allows users to separate the workload.
Customers requiring private connectivity will need to configure outbound PrivateLink. Private Link is available to Business Critical Edition only.