Setting up an Amazon FSx Windows file system - Amazon Nimble Studio

Setting up an Amazon FSx Windows file system

There are several reasons why you might want to create additional file systems for your studio. For example, you might want to separate data for different projects, or have a separate drive for studio tools and scripts. Or you might need to store large datasets, such as rendered images or simulation data, without impacting performance on your other working drives.

This administrator tutorial will walk you through the process of creating a new file system with Amazon FSx for Windows File Server and attaching the file system to your studio as a new component. This new file system can be mounted to Windows or Linux workstations, and to render workers.

Estimated time: 45 minutes


  • To complete this tutorial, you need an active Nimble Studio cloud studio deployed in your AWS account. If you don’t have a cloud studio already deployed, see the Deploying a new studio with StudioBuilder tutorial.

Step 1: Create a new file system

  1. Sign in to the AWS Management Console and open the Amazon FSx console.

  2. Make sure you're in the same Region that you deployed your studio in.

  3. Choose Create File System in the upper right-hand corner.

  4. Choose Amazon FSx for Windows File Server and choose Next.

                  FSx System Type
  5. In the File system details section, complete the fields as follows:

    1. Give the file system a name. For example, you might call it prod or tools, depending on the purpose of the file system.

    2. For Deployment type, choose Single-AZ.

    3. For Storage type, choose SSD.

    4. Decide how much Storage capacity you want. This will depend on how much data you think your studio will be storing on this particular file system. You can choose an amount between 32 GB and 65,536 GB.

      1. If you don’t know how much storage capacity your studio will need, you can start with 100 GB.

      2. This can be adjusted later if you need to increase your storage capacity.

      3. For more information, check out Managing storage capacity.

  6. In the Network & Security section, complete the fields as follows:

    1. Choose your studio’s Virtual Private Cloud (VPC). The Name tag for your studio’s VPC has been set to your studio name by default.

    2. Under VPC Security Groups, search for FSX in the dropdown menu, and select it. Example: <your-studio-name>Data-FSxFileSystems

      1. Important

        Be careful to choose the correct security group here, as there are many security groups for your studio, and choosing the incorrect one will prevent your new storage from being mounted.

      2. If you see a “default” security group selected already, remove it by choosing the “X” to the right of its name.

    3. For Subnet, choose the one called Filesystems.

    4. In the Windows authentication section, choose your studio’s AWS Managed Microsoft AD name from the dropdown menu. This will be the same name that you chose during deployment. Example: <name>.nimble.<region>.aws

    5. For the Encryption key, choose the key called <your-studio-name>-Key.

  7. Choose Next.

  8. Choose Create File System.

    1. This process can take some time. For example, it takes around 30 minutes to create a 500 GB filesystem.

Step 2: Attach the file system to the studio

This part of the process will allow you to use your new file system in your Nimble Studio cloud studio.

  1. Sign in to the AWS Management Console and open the Nimble Studio console.

  2. Choose Studio resources in the left navigation pane.

  3. Choose Add under File Storage.

  4. Provide the following information in the specified fields.

    1. Name the storage. This name can match the name that you gave to the Amazon FSx file system that you just created.

    2. File storage description (optional): Give your file storage a description.

    3. Storage type: Choose Amazon FSx for Windows File Server.

    4. Available AWS file systems: Choose the file system that you just created.

    5. Linux mount point: Enter /mnt/<filesystem_name>. For example, enter /mnt/prod.

    6. Windows mount point: Enter a drive letter on your Windows system where your new Amazon FSx file system will be mounted. For example, enter X

    7. Share name: Enter share.

    8. Security Groups: Choose the security group that starts with <your-studio-name>-WorkstationEgress.

  5. (Optional) Add tags if you're using tags to track your AWS resources.

  6. Read the terms and conditions at the bottom of the page and if you agree:

    1. Select the check box next to I understand that Nimble Studio will access my existing file storage.

  7. Choose Save connection parameters.

Step 3: Update launch profiles

To mount your new Amazon FSx file system on your render workers, you will need to update the render worker launch profile (RenderWorker-Default). You will also need to update the workstation launch profile (Workstation-Default) or other custom launch profiles that you’ve created in your studio.

  1. Go to the Launch profiles page for your studio from Nimble Studio.

  2. Select the launch profile that you want to edit.

    1. For example: RenderWorker-Default or Workstation-Default.

  3. Choose, Action. Then choose Edit.

  4. Scroll down to Launch profile studio components and select the Amazon FSx storage component that you attached in the previous section.

                  Launch Profile Studio Components
  5. Choose Update launch profile.

  6. Repeat these steps to make the new Amazon FSx file system available to your artists on any other launch profiles that you set up for your artists to use to launch workstations.

    1. Once the launch profiles are updated, artists can launch with them and will have access to the new file system.


If you will be using your new file system, a Windows workstation, and Linux farm workers, set up Path Mapping in the Deadline monitor so that Linux workers can find the submitted file, even though it was sent from a Windows workstation. See Configuring AWS Thinkbox Deadline to configure Deadline to handle paths properly.