Create a new remote file server for Snowflake on Azure - Connect_CDC - connect_cdc_mimix_share - 6.x

Connect CDC Getting Started Guide

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (MIMIX Share)
Version
6.x
Language
English
Product name
Connect CDC
Title
Connect CDC Getting Started Guide
Copyright
2024
First publish date
2003
Last updated
2024-10-15
Published on
2024-10-15T20:38:41.117981

You can configure your Azure Storage to use an external Snowflake staging location. The following section describes how you create a new remote file server connection for staging (storing) your data on Azure Storage.

  1. To create a new remote file server connection:
    • From a Server Properties dialog for a Snowflake server, under Staging, click New.

    • Right-click a host or the Remote file serversbranch, and select New Remote File Server.

      The Remote File Server Properties dialog opens.

    • Right-click a host and select Properties.

      The Remote File Server Properties dialog opens.

  2. On the Cloud tab, enter information for each field.

Table 1. Remote File Server Properties for Snowflake

Parameter

Description

Name

Use alphanumeric characters to specify a unique remote file server name for use in the model.

Note: The slash (/), backslash (\), colon (:), left caret (<), right caret (>), and spaces cannot be used in a Server name.

Connection type

Select Azure Storage from the drop-down list. Based on your selection, you will get a different set of options in the Remote File Server Properties window.

Authentication method

Click the Authentication method drop-down list and select one of the following authentication methods:
  • SAS. When selected, specify the following:
    • SAS. Use a SAS (Shared Access Signature) to give secure access to resources in your storage account. (SAS) grants limited access to objects in your storage account for a specified period of time and with a specified set of permissions
    • Storage URL. Enter the Storage URL. This URL provides the endpoint address that enables access to the Azure Storage container. The URL must contain both the account name and the container name.
  • Shared Keys. Use the Shared Key authorization scheme to make requests against the Blob, Queue, and File services. When you select this option, you must specify the following:

    • Azure Shared key. Enter the Azure access key for Azure Shared Key Authorization. When creating a storage account, Azure generates two 512-bit access keys. You can use either of the two keys, however, the best practice is to use the first key and reserve the use of the second key for when you are rotating keys. See the Azure storage documentation for more information.
    • Storage URL. Enter the Storage URL. This URL provides the endpoint address that enables access to the Azure Storage container. The URL must contain both the account name and the container name.
  • Use Runtime Environment. This option can be specified when running Connect CDC on a Azure VM machine with an IAM role attached. In this case, no keys are required. When you select this option, you must specify the following:
    • Storage URL. Enter the Storage URL. This URL provides the endpoint address that enables access to the Azure Storage container. The URL must contain both the account name and the container name.
Azure shared key

Use the Shared Key authorization scheme to make requests against the Blob, Queue, and File services.

Enter the Azure access key for Azure Shared Key Authorization. When creating a storage account, Azure generates two 512-bit access keys. You can use either of the two keys, however, the best practice is to use the first key and reserve the use of the second key for when you are rotating keys. See the Azure storage documentation for more information

Verify

Click to test the remote file server connection. After a few seconds a message opens with information about whether the test was successful. If the test was unsuccessful, note the errors in the message, troubleshoot, and verify again.