Configure bridge for Snowflake

Snowflake Bridge is a first-class integration that leverages secure data sharing to enable bi-directional data access between Amperity and Snowflake without copying data or scheduling ETL workloads.

What is Secure Data Sharing?

Secure Data Sharing enables data sharing between Snowflake accounts without copying or transferring data and instead relies on the services layer and metadata store within Snowflake. Your brand controls what data will be made available to Amperity directly from within your brand’s Snowflake account.

Tip

Amperity Bridge shares data directly with Snowflake. A bridge does not require a courier or a database export to be configured. A bridge can be configured to run automatically as part of any scheduled workflow.

If your brand is currently using BI Connect to make data available in Snowflake your brand should consider moving the BI Connect workflow to Amperity Bridge. This will increase the speed at which This will allow your brand to self-service the data that is shared between Amperity and Snowflake directly from within your Snowflake account.

From Snowflake

A sync from Snowflake to Amperity requires configuration steps to be made in both Amperity and Snowflake.

1. Get details

2. Configure Snowflake

3. Add inbound bridge

Get details

Before you can create inbound sharing between Snowflake and Amperity you will need to collect the following information.

	The organization name and account name for your brand’s Snowflake account. An organization is a first-class object in Snowflake that links accounts and allows the use of secure data sharing. The unique name of an account that exists within your brand’s Snowflake organization. Tip To find your organization name and account name use Snowsight. Open the account selector and browse to the account for which Amperity Bridge will be configured. Hover over the account name to view additional details, and then copy the account identifier. The copied identifier contains both organization and account name in the format organization-name.account-name.
	The region in which your Snowflake account is hosted. Use the CURRENT_REGION argument in Snowflake to return the value for your region.
	Before you can configure Amperity Bridge for data sharing with Snowflake you must create a share in Snowflake <bridge-snowflake-sync-amperity-configure-snowflake-create-share>, add a secure share identifier to that share, identify the region for your Snowflake account, and add the locator ID for the Amperity account in the same region as your Snowflake account and stack as your Amperity tenant. Use the CURRENT_REGION function to return the name of the region for the account where the current user is logged in. Use the CURRENT_ACCOUNT argument in Snowflake to return the locator ID for your Snowflake account. Important When using secure data sharing to share views, Snowflake strongly recommends only sharing secure views. It is not recommended to share non-secured views .
	A secure share identifier in Snowflake is a unique string—A-Z, 0-9, $, and _ (underscores)—that is added when creating a share. This string must configured in Amperity to enable the bridge. Copy the secure share identifier from the Snowflake user interface, and then share the identifier with the individual who will configure Amperity for secure data sharing with Snowflake.

Configure Snowflake

Before you can configure Amperity Bridge for data sharing with Snowflake you must create a share in Snowflake, add a secure share identifier to that share, and then identify and add the correct account locator.

Create share

To enable data sharing between Snowflake and Amperity a share must be created in Snowflake . You may use Snowsight (the Snowflake user interace) to create the share , as described in this topic, or you may use Snowflake SQL, starting with the CREATE SHARE command.

To create a share in Snowflake

1. Log in to Snowsight.

2. Select Data Products, and then Private Sharing.

3. Select Share, and then Create a Direct Share.

4. For the share, select a source database, along with one or more target objects within the source database.

5. A Secure Share Identifier is required for data sharing with Amperity.

   A secure share identifier in Snowflake is a unique string—A-Z, 0-9, $, and _ (underscores)—that is added when creating a share. This string must be configured in Amperity to enable the bridge.

6. Find the Amperity account locator ID, and then add it to the configuration for the Secure Share Identifier.

7. Copy the secure share identifier from the Snowflake user interface, and then save the share.

8. Click Add consumer, and then configure the share to use the Amperity account locator ID in the same region as the consumer.

Configure secure views

When using secure data sharing to share views, Snowflake strongly recommends only sharing secure views . It is not recommended to share non-secured views with Amperity.

Amperity account locator IDs

Snowflake must be configured for the correct account locator IDs used by Amperity. Account locator IDs are specific to the stack in which your Amperity tenant is provisioned and the region ID in which your Snowflake account resides.

Amperity stack	Snowflake region	Account locator
aws-prod	aws_us_west_2	GUB98973
aws-prod	aws_us_east_1	MVB61607
aws-prod	azure_westus2	PZ39828
az-prod	aws_us_west_2	BCB42530
az-prod	azure_eastus2	DSA38111
aws-prod-cc1	aws_us_west_2	EXB14788
az-prod-en1	aws_us_west_2	WKB77434

Important

If the account ID / region ID pair does ot exist in your stack please contact Amperity Support.

Add inbound bridge

Configure an inbound bridge to sync data from Snowflake to Amperity. To add an inbound bridge

	Open the Sources page. Under Inbound shares click Add bridge. Choose Snowflake. This opens the Add bridge dialog box. Add a name and description for the bridge or select an existing bridge, and then click Confirm.
	Configure the organization, account name, and region. An organization is a first-class object in Snowflake that links accounts and allows the use of secure data sharing. The unique name of an account that exists within your brand’s Snowflake organization. The region in which your Snowflake account is hosted. Use the CURRENT_REGION argument in Snowflake to return the value for your region.
	Add the Secure Share Identifier. When finished, click Continue. This will open the Select tables dialog box.
	Use the Select tables dialog box to select any combination of schemas and tables to be synced to Amperity. If you select a schema, all tables in that schema will be synced. Any new tables added later will need to be manually added to the sync. When finished, click Next. This will open the Domain table mapping dialog box.
	Map the tables that are synced from Snowflake to domain tables in Amperity. Tables that are synced with Amperity are added as domain tables. The names of synced tables must be unique among all domain tables. Primary keys are not assigned. Semantic tags are not applied. Tip Use a custom domain table to assign primary keys, apply semantic tags, and shape data within synced tables to support any of your Amperity workflows. When finished, click Save and sync. This will start a workflow that synchronizes data from Snowflake to Amperity and will create the mapped domain table names. You can manually sync tables that are synced with Amperity using the Sync option from the Actions menu for the inbound bridge.