关于 Openflow：BYOC 部署¶
Openflow BYOC 就是 Openflow，包含 Openflow 的所有优势，但运行在您现有的云环境中。
典型的 BYOC 工作流程¶
| User persona | Task |
|---|---|
| AWS cloud engineer/administrator | 在他们的 AWS 云账户中创建一组部署。 The Openflow UI is used to manage deployments and runtime creation and maintenance. The Openflow UI allows users to create, upgrade, and delete runtimes in all deployments. Snowflake 登录名用于向 Openflow 进行身份验证，角色和权限用于对 Openflow 部署和运行时的访问权限进行控制。 |
| Data engineer (pipeline author, responsible for data ingestion) | 使用运行时画布构建全新数据流或配置已部署的连接器。 可以创建全新数据流，也可以直接使用现有连接器，或以其为起点进行自定义。在 Snowflake 账户（或其他目标系统）的 Bronze 层中填充数据。 连接器是一种简便的集成方式，可用于解决特定的数据集成场景。即使是不具备技术背景的用户，也可以直接部署连接器，无需依赖数据工程师的协助。 |
| 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. |
限制
- As described in the Snowflake Openflow BYOC terms, securing Openflow BYOC is a shared responsibility model.
- Openflow authorization uses roles and their associated privileges that are directly granted to the user. Currently, Openflow does not support authorization when the role is attached to another role within the user’s role hierarchy.