# Create a VFS connection Perform the following steps to create a VFS connection in PDI: 1. Start the [PDI client (Spoon)](https://github.com/pentaho/documentation/blob/main/PDIA/9.3/PDI/Get%20started%20with%20the%20PDI%20client/Get%20Started%20with%20the%20PDI%20client=GUID-369AD278-A72E-426E-B5A7-488D3A4F722B=2=en=.md) and create a new [transformation](https://github.com/pentaho/documentation/blob/main/PDIA/9.3/PDI/Data%20Integration%20Perspective/Data%20Integration%20perspective%20in%20the%20PDI%20client/Work%20with%20transformations%20cp=GUID-1B9C8573-4C71-47FD-AF03-E9A0A43EDCD4=4=en=.md) or [job](/pdia-data-integration/9.3-data-integration/data-integration-perspective-in-the-pdi-client/work-with-jobs.md). 2. In the **View** tab of the Explorer pane, right-click on the **VFS Connections** folder, and then click **New**. The New VFS connection dialog box opens. ![VFS connection dialog box](/files/ODbH6V8l0UZamEzHRqJB) 3. In the **Connection name** field, enter a name that uniquely describes this connection. The name can contain spaces, but it cannot include special characters, such as `#`, `$`, and `%`. 4. In the **Connection type** field, select from one of the following types: * **Google Cloud Storage:** The Google Cloud Storage file system. See [Google Cloud Storage](https://cloud.google.com/storage/docs) for more information on this protocol. * **Snowflake Staging:** A staging area used by Snowflake to load files. See [Snowflake staging area](https://docs.snowflake.net/) for more information on this protocol. * **Amazon S3 / MinIO:** * Simple Storage Service (S3) accesses the resources on Amazon Web Services. See [Working with AWS Credentials](https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html) for Amazon S3 setup instructions. * MinIO accesses data objects on an Amazon compatible storage server. See the [MinIO Quickstart Guide](https://docs.min.io/docs/) for MinIO setup instructions. * **HCP:** The Hitachi Content Platform. You must configure HCP and PDI before accessing the platform. You must also configure object versioning in HCP Namespaces. See [Access to HCP](/pdia-data-integration/9.3-data-integration/data-integration-perspective-in-the-pdi-client/virtual-file-system-browser.md) for more information. * **Catalog:** The Pentaho Data Catalog. You must configure your Data Catalog connection before accessing the platform. Enter the authentication type, connection URL and account credentials. To access data resources from Data Catalog, an S3 or HDFS connection is also required. See [Access to Pentaho Data Catalog](/pdia-data-integration/9.3-data-integration/data-integration-perspective-in-the-pdi-client/virtual-file-system-browser/before-you-begin-vfs-connections/access-to-lumada-data-catalog.md) for details. * **Azure Data Lake/Blob Storage Gen2** The Microsoft Azure Storage services. You must create an Azure account and configure Azure Data Lake Storage Gen2 and Blob Storage. See [Access to Microsoft Azure](/pdia-data-integration/9.3-data-integration/data-integration-perspective-in-the-pdi-client/virtual-file-system-browser/before-you-begin-vfs-connections/access-to-microsoft-azure.md) for more information. 5. (Optional) Enter a description for your connection in the **Description** field. 6. Click **Next**. 7. On the **Connection Details** page, enter the information according to your selected **Connection type**. If you selected **Amazon S3 / MinIO** on the previous page, choose one of the following options: * For **Amazon**: Select the **Default S3 connection** check box to enable use of Amazon S3. * For **MinIO**: Select the **Default S3 connection** check box to enable use of MinIO. Also, select the **PathStyle Access** check box to enable path-style access. Otherwise, S3 bucket-style access is used.\ If you selected **Azure Data Lake/Blob Storage Gen2** on the previous page, choose one of the following options: * For **Account Shared Key**: Enter your shared account key credential in the **Account Shared Key** field. * For **Azure Active Directory**: Enter your Azure Active Directory credentials in the **Application (client) ID**, **Client Secret**, and **Directory (tenant) ID** fields. * For **Shared Access Signature**: Enter your SAS token in the **Shared Access Signature** field.**Note:** For all three Azure options, you must also specify your Azure account name in the **Service Account Name** field, the **Block Size**, the **Buffer Count**, the **Max Block Upload Size**, and your **Access Tier**. 8. (Optional) Click **Test** to verify your connection. 9. Click **Next** to view the connection summary, then **Finish** to complete the setup. You can now use your connection to specify VFS information in your transformation steps or job entries, such as the Snowflake entries or HCP steps. See [PDI and Snowflake](https://github.com/pentaho/documentation/blob/main/PDIA/9.3/PDI/Advanced%20Pentaho%20Data%20Integration%20topics/Advanced%20topics%20\(Pentaho%20Data%20Integration%20overview\)/PDI%20and%20Snowflake%20cp=GUID-75EACA27-8EEE-4543-BD57-99A2697F1839=4=en=.md) and [PDI and Hitachi Content Platform (HCP)](/pdia-data-integration/9.3-data-integration/advanced-topics-pentaho-data-integration-overview/pdi-and-hitachi-content-platform-hcp.md) for more information about these entries and steps. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/data-integration-perspective-in-the-pdi-client/virtual-file-system-browser/create-a-vfs-connection-in-pdi.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.