Setting up to use Nimble Studio - Amazon Nimble Studio

Setting up to use Nimble Studio

This tutorial is for admin users who want to set up an Amazon Nimble Studio. If you are an artist who is just beginning to use Nimble Studio, go to the Artist getting started section.

The following sections will guide you through the steps that you must complete before deploying a studio in Nimble Studio.


Set up IAM


For StudioBuilder to work, you can’t use an AWS account that is associated with an AWS Organization. First, log out of that AWS account. Then create a new AWS account.

Review the following Identity and Access Management (IAM) documentation before you start:

Log in to your AWS account as an admin user to complete the remaining setup.

Check service quotas

You can use the AWS Service Quotas console to view and request increases for most AWS quotas. If you are using an existing AWS account for deployment, for instance, it’s important that you are not already reaching your limit.

Most service quotas are Region-specific, so be sure to select the AWS Region where the quota increase is required.

Check your Spot Instance quota

Increasing your Spot Instance quota will allow you to scale your farm up to the size required by your team to handle the workload for your projects.

  1. Sign in to the AWS Management Console.

  2. Go to Services → Service Quotas .

  3. Check that your Region is set to the region in which you want to deploy your studio.

  4. In the left navigation pane, choose AWS services.

  5. Search for Amazon Elastic Compute Cloud (Amazon EC2).

  6. Choose All Standard (A, C, D, H, I, M, R, T, Z) Spot Instance Requests from the list.

  7. Choose Request quota increase.

  8. In the window that appears, enter a new quota value in the field under Change quota value.

    1. To figure out what to change your quota value to, multiply the number of render workers that you want to run concurrently with the number of vCPUs you want each render worker to have.

    2. For example, if you have 20 workers and want each worker to have 16 vCPUs, you would request to change your quota value to 320.

  9. Choose Request.

For information about the specs of different instances, see Amazon EC2 Instance Types.


The default quota for Amazon Simple Storage Service (Amazon S3) buckets is 100 per AWS account. StudioBuilder will fail whenever you reach 4 buckets below your limit. To request a quota increase up to 1,000 buckets, open the AWS Service Quotas console, choose AWS services from the left navigation pane, and search Amazon S3.

Request a quota increase

Your AWS account is subject to quotas that might impact how many Nimble Studio virtual workstations, render workers, and EC2 G4 instances that you are able to launch.

You can request increases to all of your studio quotas. After your request for a service quota increase is approved, your studio will have access to the resources that your team needs to do their work. For more information, see AWS service quotas.

Request a quota increase for Amazon Nimble Studio streaming sessions

A streaming session is how artists connect to their virtual workstations so that they can access the files, settings, and applications that they need to work on an asset. By default, your AWS account is limited to two streaming sessions per studio. If you are planning on having more than two artists working at a time, you will want to request a quota increase for Nimble Studio streaming sessions.

  1. Go to the Service Quotas console.

  2. Check that your Region is set to the region in which you want to deploy your studio.

  3. In the left navigation pane, choose AWS services.

  4. Search for Amazon Nimble Studio.

  5. Choose Amazon Nimble Studio from the list.

  6. Select Streaming sessions per studio by choosing the dot next to the item.

  7. Choose Request quota increase.

                     service quotas request
  8. Enter the desired number of concurrent streaming sessions into the Change quota value field.

    1. Each artist will require their own streaming session. Therefore, choose the number of artists that you anticipate working in your studio at any given time.

Request a quota increase for VPC security groups per network interface

  1. In the left navigation pane choose AWS services.

  2. Search for VPC.

  3. Choose Amazon Virtual Private Cloud (Amazon VPC) in the list.

  4. Select the dot next to Security groups per network interface.

  5. Choose Request quota increase.

  6. In the Change quota value field, enter the desired number of security groups per network interface.

    1. This number will depend on how many studio components you anticipate adding to your launch profiles and how many security groups are being used by those components. If you are not sure, 10 is a good starting point. You can always increase this quota later.

Request a quota increase for On-Demand “G and VT” Instances

When updating the AMIs that your team uses to launch virtual workstations, you will need to launch GPU instances so that you can install and test the software that you are adding to the AMI.

  1. In the left navigation pane, choose Dashboard

  2. Choose Amazon Elastic Compute Cloud (Amazon EC2) from the list of dashboard cards.

  3. Select Running On-Demand G instances from the list and choose Request quota increase. G stands for graphic-intensive instances.

  4. In the window that appears, enter a new quota value in the field under Change quota value.

    1. You should enter a minimum value of 4, but we recommend entering at least 16 just to be safe.

    2. The minimum value of 4 will allow you to run one g4dn.xlarge instance at a time for AMI creation, because it has 4 vCPUs. If you want to run more than one instance at a time to create AMIS or a g4 instance with more vCPUs, you will need a higher quota value. A value of 16 would allow you to run 4 g4dn.xlarge instances at a time or one g4dn.4xlarge instance, which has 16 vCPUs.

  5. Choose Request quota increase.

  6. You can check on the status of a quota request by choosing Quota request history in the navigation pane of the Service Quotas console. It can take anywhere from 12 to 48 hours for a request to be resolved.

(Optional) Opt in to the LA Local Zone

If you want to create a studio in the us-west-2 Region, you can create workstations and file systems in the LA Local Zone. We recommend this for lower latency interactions, if you and your artists are located closer to California than Oregon. For more information about Local Zones, see the AWS Local Zones FAQs.

To use the LA Local Zone, you must manually opt in from the console. If you don’t, the Local Zone won’t appear in the list of Availability Zones in the StudioBuilder deploy tool.

  1. Go to Services → VPC.

  2. Select Settings.

  3. Scroll down to US West (Los Angeles) / us-west-2-lax-1 and select Manage.

                  US West Local Zones
  4. Select Opted in.

                  Opt in to Local Zones
  5. Select Update zones.

You can now create resources in the LA Local Zone.