Managing Cross-Cloud Auto-Fulfillment in Snowflake Data Clean Rooms¶

Account administrators¶

To enable Cross-Cloud Auto-Fulfillment for an account using the API, administrators in both the provider and consumer accounts must run the following example code using the ACCOUNTADMIN role. You need to run this only once per account.

USE ROLE ACCOUNTADMIN;
-- Optionally check first to see if cross-cloud is enabled on the account.
CALL samooha_by_snowflake_local_db.library.is_laf_enabled_on_account();

-- If not, enable it.
CALL samooha_by_snowflake_local_db.library.enable_laf_on_account();

Providers and consumers¶

After Cross-Cloud Auto-Fulfillment is enabled for an account, here is how to enable Cross-Cloud Auto-Fulfillment when creating or installing a clean room:

1. The provider publishes the clean room in the normal way by calling provider.create_or_update_cleanroom_listing.

2. The consumer installs the clean room by calling consumer.install_cleanroom. If the consumer is in a different cloud region from the provider, consumer.install_cleanroom fails with a message that Cross-Cloud Auto-Fulfillment replication is being installed.

3. The consumer continues to call consumer.install_cleanroom until it returns success. Installation takes several minutes.

At this point, the consumer has basic clean room functionality. If the consumer wants support for client template requests, provider-run analyses, and provider activation, follow these additional steps:

1. The provider calls provider.mount_request_logs_for_all_consumers to enable communication from the consumer to the provider.

Full setup code example:

1. Provider: The provider creates, shares, and publishes a clean room in the standard way.

   USE WAREHOUSE APP_WH;
   USE ROLE SAMOOHA_APP_ROLE;
   
   SET cleanroom_name = 'LAF example';
   SET consumer_locator = '<CONSUMER_LOCATOR>';
   SET consumer_account_name = '<CONSUMER_DATA_SHARING_ACCOUNT_ID>';
   
   CALL SAMOOHA_BY_SNOWFLAKE_LOCAL_DB.provider.cleanroom_init($cleanroom_name);
   
   CALL SAMOOHA_BY_SNOWFLAKE_LOCAL_DB.provider.set_default_release_directive(
     $cleanroom_name,
     'V1_0', '0');
   
   CALL SAMOOHA_BY_SNOWFLAKE_LOCAL_DB.provider.add_consumers(
     $cleanroom_name,
     $consumer_locator,
     $consumer_account_name);
   
   CALL SAMOOHA_BY_SNOWFLAKE_LOCAL_DB.provider.create_or_update_cleanroom_listing($cleanroom_name);
   

   Copy

2. Consumer: The consumer installs the clean room.

   USE WAREHOUSE APP_WH;
   USE ROLE samooha_app_role;
   
   SET cleanroom_name = 'LAF example';
   SET provider_locator = '<PROVIDER_LOCATOR>';
   
   -- Initial call starts the process and returns a cross-cloud/region replication failure.
   -- Continue to call this procedure until it returns a success message.
   CALL SAMOOHA_BY_SNOWFLAKE_LOCAL_DB.consumer.install_cleanroom(
     $cleanroom_name,
     $provider_locator);
   
   -- Continue with standard clean room configuration and use.
   -- Consumer can run analyses, but requests to submit a template aren't
   -- supported until the provider calls provider.mount_laf_cleanroom_requests_share.
   ...
   

   Copy

3. Provider: After the consumer installs the clean room, the provider must mount the requests share if they want to enable request-based actions between the provider and consumer. Request-based actions include provider requests to run an analysis and consumer requests to add a template to the clean room.

   -- Call mount_request_logs_for_all_consumers until it reports success.
   provider.mount_request_logs_for_all_consumers($cleanroom_name);
   

   Copy

   Full provider/consumer functionality is now available.