Connecting to a File Store

When the Anzo Server is initially installed, the default file store (typically an NFS mount) is configured. This topic provides instructions for connecting to an additional file storage system. The supported systems are local file systems (such as a mounted NFS), Hadoop Distributed File Systems (HDFS), File Transfer Protocol (FTP or FTPS) systems, Google Cloud Platform (GCP) storage, and Amazon Simple Cloud Storage Service (S3).

Connecting to File Storage
Connection Settings Reference

Connecting to File Storage

In the Administration application, expand the Connections menu and click File Store. Anzo displays the File Store screen, which lists existing file store connections. For example:
Click the Add File Connection button and select the type of file connection that you want to create. For the local disk or mounted NFS, choose Local File Connection. Anzo displays the create connection screen for the type of connection you chose.
On the connection screen, provide the file system details. The settings that display depend on the type of file connection that you chose. See Connection Settings Reference below for details.
Click Save to save the configuration. The file store connection that you specified becomes available as a choice when you create Anzo Data Stores or select source files to onboard, etc.

Local File Connection

Setting	Description
Name	The name to use for this file connection.
Base Folder	The base or root folder on the file system where you want Anzo to read or write files. Each time Anzo generates new files it creates a new subdirectory under this base location.
Globally accessible filesystem	Select this option if this file store is accessible by all of the servers in an AnzoGraph cluster. If only the leader server can access this system, leave this option blank.

HDFS File Connection

If you use Kerberos Authentication with HDFS, you must also configure the AnzoGraph cluster to authenticate with Kerberos. For instructions, see Configuring AnzoGraph for Kerberos Authentication.

Setting	Description
Name	The name to use for this file connection.
Nameservice IP or Name	The IP address or host name for the storage system.
Port	The RPC port to access the server on. The default RPC port is 8020.
Base Folder	The base or root folder on the file system where you want Anzo to read or write files. Each time Anzo generates new files it creates a new subdirectory under this base location.
HDFS Configuration Path	The full path to the configuration files.
Keytab Path	The full path to the keytab file.
Password Confirm Password	The password for the account used to access the server.
Nameservice Rest IP or Name	The HTTP REST IP address or host name. Typically this value is the same as the `Nameservice IP or Name`.
Nameservice Rest Port	The HTTP port. AnzoGraph uses this port to access HDFS and load the FLDS. The default HTTP port for the namenode is 9870.
Nameservice Rest Protocol	The protocol to use for requests. Choose one of the following values: hdfs: Specify `hdfs` for non-secure HTTP protocol. shdfs: Specify `shdfs` for secure HTTPS protocol. khdfs: Specify `khdfs` for non-secure HTTP protocol with Kerberos authentication. kshdfs: Specify `kshdfs` for secure HTTPS protocol with Kerberos authentication.
Globally accessible filesystem	Select this option if this file store is accessible by all of the servers in an AnzoGraph cluster. If only the leader server can access this system, leave this option blank.

FTP or FTPS File Connection

Setting	Description
Name	The name to use for this file connection.
Server IP or Name	The IP address or host name for the storage system.
Port	The port to access the server on.
Base Folder	The base or root folder on the file system where you want Anzo to read or write files. Each time Anzo generates new files it creates a new subdirectory under this base location.
Username	The user name for the account used to access the server.
Password Confirm Password	The password for the account used to access the server.
Keystore Path	For FTPS connections, the full path to the keystore file.
Globally accessible filesystem	Select this option if this file store is accessible by all of the servers in an AnzoGraph cluster. If only the leader server can access this system, leave this option blank.

Google Cloud Platform File Connection

Setting	Description
Name	The name to use for this file connection.
Bucket Name	The name of the bucket to store files in.
Base Folder	The base or root folder on the file system where you want Anzo to read or write files. Each time Anzo generates new files it creates a new subdirectory under this base location.
Account Email	The email address for the account used to access the storage.
Key File Location	The full path to the keystore password file.
Globally accessible filesystem	Select this option if this file store is accessible by all of the servers in an AnzoGraph cluster. If only the leader server can access this system, leave this option blank.

S3 File Connection

When using Amazon S3 for file storage, do not use client-side encryption, where data is encrypted before it is sent to S3. Anzo cannot read files on S3 if the object store uses client-side encryption.

Setting	Description
Name	The name to use for this file connection.
Bucket Name	The name of the bucket to store files in.
Base Folder	The base or root folder on the file system where you want Anzo to read or write files. Each time Anzo generates new files it creates a new subdirectory under this base location.
Access Key	The Access Key ID to use for accessing the S3 location.
Secret Key Confirm Secret Key	The Secret Key ID for the Access Key.
S3 URI Scheme	Specifies whether the URI scheme is S3, S3 Native, or S3A.
Globally accessible filesystem	Select this option if this file store is accessible by all of the servers in an AnzoGraph cluster. If only the leader server can access this system, leave this option blank.