Immuta-Snowflake warehouse utilization at-a-glance

• Standard Immuta-Snowflake integration, warehouse used for onboarding and integration activities can be the same warehouse or different.

• Enhanced-Onboarding Immuta-Snowflake integration uses the same warehouse for both onboarding and integration activities. A Snowflake 'role' is needed to access data that would be ingested to Immuta.

• IMMUTA_SYSTEM(if the integration database is IMMUTA) role and <db name>.SYSTEM_ ACOUNT user are created in Snowflake to manage the integration.

• Recommend to scale-up vertically with cluster size or scale-out horizontally to handle heavy loads:

  • lots of data sources ingestion activities

  • lots of policy push and sync activities to many data sources in Snowflake.

• General rule - start with smaller number of datasources with policy changes, and start with few datasources ingestions, then review query history to decide on scaling needs.

Enhanced-Onboarding Immuta - Snowflake integration:

• Both onboarding and integration activities use the same warehouse.

• A data accessing role is require, a Immuta system role will be created with the integration database name, and the service_account_user needs to be granted with both roles.

Standard Immuta - Snowflake integration:

• warehouse information are entered separately, though both onboarding and integration warehouse can be the same.