Creating launch profiles - Amazon Nimble Studio

Creating launch profiles

This admin tutorial shows you how to create launch profiles. If you want to learn how to update launch profiles, see the Modifying launch profiles tutorial.

Launch profiles control access to resources in your studio such as compute farms, shared file systems, instance types, and Amazon Machine Images (AMIs). StudioBuilder creates two default launch profiles for you, the first time that it runs: Workstation-Default and RenderWorker-Default. The Workstation-Default launch profile is what your artists will use to launch virtual workstations. You can use the RenderWorker-Default launch profile to manage rendering resources and their access to storage.

If you want to customize your team’s access to studio resources, this tutorial shows you how to create your own launch profiles.

Estimated time: 20 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.

  • Optionally, you can complete the steps in the Adding studio users tutorial before starting this one. By adding users first, you can assign your new launch profile to specific users at the end of this tutorial. However, if you prefer to create your launch profiles first, you can return to the end of this tutorial after adding users.

Step 1: Create a launch profile by copying an existing one

The easiest way to create a new launch profile is to copy an existing one. From there, you can make edits, so that the new profile is configured in the way that you want. The added benefit of copying an existing launch profile is that you can start with default settings for each element of the launch profile.

To copy an existing launch profile

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

  2. Choose Launch profiles in the left navigation pane.

  3. Select the launch profile that you want to copy.

    1. If this is your first new launch profile, you will be copying the Workstation-Default launch profile that was created by StudioBuilder.

  4. Choose Actions. Then choose Copy to new.

  5. Give your launch profile a name.

    1. To keep track of your launch profiles, you can give them version numbers, include the date in the name, or refer to the department they’re being created for.

      1. Example: animation-2021-03-08, studio-v003

  6. Give your launch profile a description.

    1. Describe what makes this launch profile unique in your description.

    2. Example: “Added Adobe Photoshop and Yeti; added X: drive; increased instance size to XLarge (g4dn.16xlarge).”

  7. In the Amazon Machine Images (AMI) section, choose the Amazon Machine Images that you want to be available to artists when they launch workstations with your new launch profile.

    1. If you haven’t created any new AMIs yet, choose either the Windows or Linux default AMI.

    2. If you have created a new workstation AMI, choose the new one that you made.

    3. You can select multiple AMIs for your launch profile, which will give the artist a choice when launching.

      1. This is particularly useful if you want to allow artists to choose their operating system (Linux vs Windows).

  8. In the Launch profile components section, select the components that you want to make available to artists who are launching workstations with your new launch profile.

    1. If you haven’t created any new storage or farm components, leave these as default.

  9. In the Subnet IDs section, don't modify the subnets, unless you want to launch workstations in a different Availability Zone than the one you chose during StudioBuilder deployment.

  10. In the Streaming preferences section, choose which instance type that you want your artists to have access to when using this launch profile. Enter the maximum consecutive hours that instances can be in the Running and Stopped states. The default values are 11.5 hours and 168 hours.

    1. To learn about various instance sizes, such as how many vCPUs, GPUs, and how much memory they have, see the Product Details section of the Amazon EC2 G4 Instances page.

    2. To learn more about Running, Stopped, and Terminated states for workstations, see Starting and stopping workstations - Admins (Preview).

    3. To use G5 instances, increase your quota limit for G5 streaming sessions per studio. Ensure that your GRID version is 13.1 or later by upgrading your NVIDIA drivers. For instructions about how to increase your quota limit, see (Optional) Request a quota increase for G5 streaming sessions. For instructions about how to upgrade your NVIDIA drivers, see NVIDIA.

    4. For information about pricing, see Amazon Nimble Studio Pricing.

                  The Streaming preferences section. A note states that to select G5
                     instances, increase your quota.
  11. (Optional) Add tags if you're using tags to track your AWS resources.

  12. Select Create launch profile. This creates a launch profile and checks that it can be launched.

    1. Validating the launch profile doesn’t mean that the launch profile will work, but it can detect known failures that would prevent it from launching.

    2. If the validation succeeds, the launch profile goes into the Ready state. However, if the validation fails, the launch profile goes into the Impaired state. Regardless of the validation state, the launch profile is created.

    3. If your validation failed, you will see an error banner at the top of the page. If the failure is due to a dependent service with an outage, the validation is aborted and your launch profile isn't marked as impaired.

    4. You can view the details of your launch profile validation in the Launch profile details section of your launch profile.

                        The Launch profile details page with Launch profile status. Shows
                           the date and time of the most recent successful validation.

Step 2: (Optional) Perform a test launch

Before you launch a virtual workstation with the new launch profile, you can test if the launch profile can create a streaming session.


A test launch is the same as a regular launch, so the charges are the same for both.

  1. Choose the launch profile that you just created.

  2. Select Actions. Then choose Perform test launch.

    1. You can only run a test launch on a launch profile that has the status Ready or Impaired.

                        Nimble Studio console, Launch profiles page. The Actions dropdown shows the
                           Perform test launch option.
  3. Choose Perform test launch.

                  The Test launch confirmation message with Perform test launch button and
                     Cancel button.
  4. The status of your launch profile will change to Performing test launch.

                  The Launch profiles section. An information bar points to the status of
                     the launch profile.
    1. The amount of time it takes to finish the launch test depends on the AMI. After one hour, the request times out (expires) and the test launch fails.

  5. If the test launch is successful, the launch profile goes into the Ready state. However, if the test launch fails, the launch profile goes into the Impaired state.

    1. To troubleshoot a failed test launch, select the status of the failed launch. When the Impaired: Streaming session launch failed bubble appears, select the View errors link.

                        The message that displays for impaired launch profiles.
    2. Alternatively, choose the launch profile that you just created and select Actions. Then choose View errors.

                        The View errors page showing Launch profile status as
  6. In the View errors section, you can either choose Edit launch profile to adjust the settings, or Perform test launch to retry the test launch with the unmodified launch profile.

  7. You can view the details of your test launch in the Launch profile details section of your launch profile.

                  A screenshot of the Launch profile details page. Below the launch profile
                     ID is the Launch profile most recent launch.

Step 3: Share launch profiles with studio users

By default, studio admins can use all launch profiles. However, for other users to access launch profiles, admins must share these in the Nimble Studio portal. The following instructions show you how.

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

  2. On the Studio manager page, choose Go to Nimble Studio portal.

  3. Log in to the Nimble Studio portal using your AWS Managed Microsoft AD administrator credentials.

    1. Enter Admin as the user name. Use the password that you set up during StudioBuilder deployment.

                        Nimble Studio portal sign in screen.
    2. If you forgot your password, do the following:

      1. Sign in to the AWS Management Console and open the AWS Directory Service console.

      2. In the AWS Region selector (top-right navigation bar), make sure that the Region for your studio is selected.

                  The AWS Region selector in the menu bar of an AWS service console.
      3. Choose the Directory ID for your studio’s Active Directory.

      4. Choose Reset user password.

                              A screenshot of the Directory Service console. Directories is
                                 chosen in the left navigation pane
  4. In the upper-right corner of the Nimble Studio portal, choose your user name.

  5. Choose Settings from the dropdown menu.

                  Launch profile settings in the Nimble Studio portal.
  6. Choose Launch profiles in the left navigation pane.

                  Launch profile dashboard
  7. Locate the launch profile that you want to share.

  8. Choose the share icon next to it.

                  Launch profile share icon in the Nimble Studio portal.
  9. Select the user or users who should have access to the launch profile.

    1. You can search for user names in the search field to help you find users.

  10. Choose Share to grant the user access to the launch profile.

  11. Choose Save changes.

                  Launch profile save changes in the Nimble Studio portal.
  12. When the user reloads their page, they will see the launch profile that you shared with them.

Now that you’ve created launch profiles, you can also add new studio components to them, make updates, and customize your studio setup.


Error when trying to create a new launch profile.

The default quota value for the number of launch profiles is 50. Therefore, if you got an error when choosing Create launch profile, you might have exceeded your studio’s limit.

To correct this error, you can either Remove launch profile that you no longer need, or request a quota increase for more launch profiles. To request a quota increase, see Request a quota increase in the Setting up to use Nimble Studio tutorial.