# Vendor Submission Transfer Methods The [Vendor Submission](/artist-anywhere/vendor-workflows/vendor-submission.md) tool supports several methods for transferring files from the Vendor to the Production. Each transfer method has different input fields in the Transfer dialog. Select the transfer method according to the instructions provided by Production. ## Cyclone Vendor Submission supports direct uploading to Amazon S3 via **\[RE]DESIGN’s Cyclone** tool, which is part of the **Artist Anywhere** toolset. This transfer method requires no user configuration and will auto-ingest by the Ingest Queue. In addition to being a transfer option for Vendor Submission, Cyclone is the required transfer method for the [Delivery To Vendor Service](/artist-anywhere/i-o-tools/delivery-to-vendor-service.md).

To select Cyclone as your transfer method, simply choose it in the Method dropdown. {% hint style="success" %} Use the Validate Credentials button to troubleshoot access issues. {% endhint %} ## Aspera on Cloud Files **Vendor Submission** supports direct upload of Submissions to **Aspera on Cloud Files**, from which **Ingest Delivery** can auto-ingest them. This process requires additional configuration to support Aspera Files’ security requirements. When you select Aspera Files as your Transfer Method, there will be several extra steps in setting it up.

First, enter your Aspera username in the **Account** field. Note that this is distinct from the ShotGrid username. To authenticate, Aspera uses a combination of a public and private Key (RSA, PEM format, 2048 bit). If you already have a public key in your Aspera account, enter the path to your private key file in the **Private Key File** field. If you don’t have a private key, the tool can generate one. Click the **Create New Private Key File** link and save the file to a location that is secure and accessible to users who have access to the Aspera account.

In the resulting **Instructions** window, click the **Copy to clipboard** button to copy the Public Key to your system clipboard. From there, you’ll need to **log into your Aspera website** in the browser, click on your profile icon in the upper right corner, and select **Account Settings**.

Paste the copied key text into the **Public Key (PEM Format)** field. Your Production may either share a folder with you or invite you to access their workspace. If they have invited you to their workspace, set the **Default workspace (Defaults tab)** dropdown to the workspace your Production has invited you to.

If your Aspera account has access to a different workspace and you do not see the Production in the Default workspace list, you may have issues uploading files. In that case, we recommend creating a new Aspera account for the purpose of uploading to this production to avoid any workspace ambiguity. {% hint style="info" %} If you do not see a **Default Workspace** section, then no change is necessary. {% endhint %} Click the **Save** button. If there is an issue with the key, there will be a warning here. If not, Aspera accepted the key. Return to the Vendor Submission tool and close the Key Generator window. Click the **Client ID and Secret** link.

In the resulting window, fill in the Client ID and the Client Secret with values provided to you by \[RE]DESIGN or the Production. {% hint style="danger" %} The client ID and secret must be kept secure. Do not share them without authorization from the Production. {% endhint %}

First, enter your Aspera username in the **Email** field. Note that this is distinct from the ShotGrid username. To authenticate, Aspera uses a combination of a public and private Key (RSA, PEM format, 2048 bit). If you already have a public key in your Aspera account, enter the path to your private key file in the **Private Key File** field. If you don’t have a private key, the tool can generate one. Click the **Create New Private Key File** link and save the file to a location that is secure and accessible to users who have access to the Aspera account.

Paste the copied key text into the **Public Key (PEM Format)** field. Click the **Save** button. If there is an issue with the key, there will be a warning here. If not, Aspera accepted the key. Return to the Vendor Submission tool and fill in the **Client ID and Secret**. This will be provided by your Production. {% hint style="danger" %} The client ID and secret must be kept secure. Do not share them without authorization from the Production. {% endhint %}

Finally, click the **Validate Credentials** button. If all the settings are correct, you will receive a notice that the credentials look valid. If you receive any other message, reach out to \[RE]DESIGN so we can help sort out the issue. ## Aspera Faspex (v5) **Vendor Submission** can submit files directly through **Aspera's Faspex** offering. The Production will set up the username and password, which will be different from the ShotGrid user and password. Packages will be uploaded to Faspex and addressed to the production. {% hint style="success" %} **Using an older version of Aspera Faspex?** Faspex v5 adopts OAuth2 as its authorization mechanism, so the setup for legacy versions differs considerably. For setup instructions for legacy Faspex versions, see the [**Aspera Faspex (v4.0.x Legacy)**](#h_01hdstsf2dyjmfnaemppbk8bvv) section below. {% endhint %} This process requires additional configuration to support Aspera security requirements. When you select **Aspera Faspex v5** as your Transfer Method, there will be several extra steps in setting it up. {% hint style="danger" %} The \[RE]DESIGN apps require **minimum version v1.8.0 of ShotGrid Desktop** minimum version to work with Aspera. For ShotGrid Desktop installation instructions, click here(link). {% endhint %} You will need the following items to authenticate your Aspera connection: * Aspera Account Email Address * Client ID * Public Key * Private Key (PEM file)

First, enter your **Aspera Account Email Address** in the **Email** field. Note that this is distinct from the ShotGrid username. Enter the **Client ID** that was provided to you either by the production in the Client ID field. To authenticate, Aspera uses a combination of a public and private Key (RSA, PEM format, 2048 bit). If you already have a public key in your Aspera account, enter the path to your private key file in the **Private Key File** field. If you don’t have a private key, the tool can generate one. Click the **Create New Private Key File** link and save the file to a location that is secure and accessible to users who have access to the Aspera account. {% hint style="danger" %} The Client ID, Public, and Private keys must be kept secure. Do not share them without authorization from the Production. {% endhint %}

In the resulting Instructions window, click the **Copy to clipboard** button to copy the Public Key to your system clipboard. From there, you’ll need to **log into your Aspera website** in the browser, click on your profile icon in the upper right corner, and select **Account Settings**.

Paste the copied public key text from the previous step into the **Public Key (PEM Format)** field. Click the **Save** button. If there is an issue with the key, there will be a warning here. If not, Aspera accepted the public key.

Finally, back in Vendor Submission, click the **Validate Credentials** button. If all the settings are correct, you will receive a notice that the credentials look valid. If you receive any other message, reach out to \[RE]DESIGN so we can help sort out the issue. ## Aspera Faspex (v4.0 Legacy) IBM is no longer supporting Faspex v4.0.x and older, but our tools still have the option to interface with it. The authentication for Faspex v4 differs from Faspex v5+.

Vendors using this setup should choose **Aspera Faspex v4** from the **Method** dropdown and enter their Aspera username and password. After adding your credentials, click the **Validate Credentials** to confirm the settings. ## Offline The **Offline** option is for cases where the transfer of the Submission will take place outside of the **Artist Anywhere** tools. **Offline** simply creates a local copy of all files in the Submission. The user needs only to input the path where the Delivery package will be stored before transfer. From there, the Vendor can transfer the Submission package manually, using Aspera, DropBox, a hard drive, or whatever method the Production requests.

Checking the **Zip Files** checkbox packages the files into a ZIP file, but this is a convenience function which is generally unnecessary and adds additional time to compress. If you are concerned about upload size, a better option may be to simply split your Submission into smaller uploads, which may save time. Note also that uncompressed EXRs are very slow to package; we recommend using a compressed format like EXR/ZIP or EXR/PIZ. {% hint style="danger" %} The user must have enough space on their local or mounted servers to store all the files in the Submission. {% endhint %} --- # 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://artist-anywhere.gitbook.io/artist-anywhere/vendor-workflows/vendor-submission-transfer-methods.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.