This section describes how you create a new remote file server connection for staging (storing) your data in your external storage environment.
The following remote file server connection types are supported:
-
Amazon (AWS) S3 Storage. An Amazon S3 stage is an external S3 bucket location where data files are stored (staged) in batches before data is loaded into Snowflake tables. The storage location can be either private (protected) or public.
-
Snowflake Internal. If you do not plan to use Amazon S3 Storage for external staging, then you must instead configure your Snowflake DBMS server to use an internal (local) Snowflake staging location. For more information, see Create a new server for Snowflake.
-
Azure Storage. In addition to Amazon S3 Storage for external staging, you can configure your Azure Storage to use an external Snowflake staging location.
-
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 servers branch, 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.
- On the Cloud tab, enter information for each field.
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 AWS S3 from the dropdown 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 dropdown list and select one of the following
authentication methods:
|
Bucket url and encryption |
Specify the following bucket staging properties:
|
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. |