Concepts and terminology for Amazon Nimble Studio - Amazon Nimble Studio

Concepts and terminology for Amazon Nimble Studio

To help you get started with Amazon Nimble Studio, and understand how it works, you can refer to the key concepts and terminology in this guide.

Key features

Amazon Nimble Studio

Amazon Nimble Studio is an AWS service that enables creative studios to produce visual effects, animation, and interactive content entirely in the cloud, from storyboard sketch to final deliverable.

Amazon Nimble Studio console

The Nimble Studio console is a portion of the AWS Management Console that is devoted to our admin IT customers. This console is where admins create their cloud studio and manage many settings. For instance, the Studio manager page allows you to add or remove resources, add applications, and grant permissions to users and groups.

Amazon Nimble Studio portal

The Nimble Studio portal provides a user interface for day-to-day interactions with Nimble Studio applications and services. Users sign in directly to the portal with their user name and password without having to interact with the AWS Management Console.

Nimble Studio File Transfer

File Transfer accelerates media asset transfers of digital media assets to and from Amazon Simple Storage Service (Amazon S3). File Transfer provides a graphical user interface, which you can use to quickly move thousands of large media files. For more information, see the What is Nimble Studio File Transfer page.

AWS Thinkbox

Thinkbox software includes the render farm manager Thinkbox Deadline, and the 3D plugin, Thinkbox Krakatoa. You can use Thinkbox software to help you increase your studio's creative output on premises, in the cloud with Amazon EC2, or a combination of both. For more information, see AWS Thinkbox Products.

Key concepts and terminology

AWS managed policies

An AWS managed policy is a standalone policy that is created and administered by AWS. Standalone policy means that the policy has its own Amazon Resource Name (ARN) that includes the policy name. For example, arn:aws:iam::aws:policy/IAMReadOnlyAccess is an AWS managed policy. For more information about ARNs, see IAM ARNs.

AWS managed policies are used for granting permissions to common job functions. Job function policies are maintained and updated by AWS when new services and API operations are introduced. For example, the AdministratorAccess job function provides full access and permissions delegation to every service and resource in AWS. Whereas, partial-access AWS managed policies such as AmazonMobileAnalyticsWriteOnlyAccess and AmazonEC2ReadOnlyAccess can provide specific levels of access to AWS services without allowing full access. For learn more about access policies, see Understanding access level summaries within policy summaries.

AWS Management Console

The AWS Management Console is a web application that provides access to a broad collection of service consoles for managing AWS services.

Each service also includes its own console. These consoles offer a wide range of tools for cloud computing. There’s even a service that helps with billing and cost management.

AWS IAM Identity Center (IAM Identity Center)

IAM Identity Center is an AWS service that makes it easy to centrally manage access to multiple AWS accounts and business applications. With IAM Identity Center, you can provide users with single sign-on access to all their assigned accounts and applications from one place. You can also centrally manage multi-account access and user permissions to all of your accounts in AWS Organizations. For more information, visit AWS IAM Identity Center FAQs.

AWS PrivateLink

AWS PrivateLink provides private connectivity between VPCs, AWS services, and your on-premises networks, without exposing your traffic to the public internet. AWS PrivateLink makes it easy to connect services across different accounts and VPCs. AWS PrivateLink is available for a monthly fee that is billed to your AWS account.

Digital Content Creation (DCC)

Digital Content Creation (DCC) refers to the category of applications that are used to produce creative content, including Blender, Nuke, Maya, and Houdini.


Nimble Studio offers eleven AWS Regions from which to choose deploy your studio. Regions are where essential studio infrastructure exists, such as your data and applications.

The Region should be located closest to your studio users. This reduces lag and improves data transfer speeds.


A studio is the top-level container for other Nimble Studio-related resources. Your cloud studio manages the Nimble Studio web portal and the connections to essential resources in your AWS account such as your VPC, user directory, and storage encryption keys.

Studio applications

Studio components are configurations within a customer’s Nimble Studio that tell the service how to access resources like file systems, license servers, and render farms in your AWS account.

Nimble Studio contains a number of subtypes of studio components including a shared file system, compute farm, Active Directory, and license component. These subtypes describe resources that you would like your studio to use.

Studio resources

Studio resources is a term that encapsulates the things a studio needs in their daily operations. When describing how resources fit into the infrastructure of a cloud studio, they might be also referred to as studio components.


A tag is a label that you assign to an AWS resource. Each tag consists of a key and an optional value that you define.

Tags enable you to categorize your AWS resources in different ways. For example, you could define a set of tags for your account’s Amazon Elastic Compute Cloud (Amazon EC2) instances that help you track each instance’s owner and stack level. Tags also enable you to integrate your organization’s shared file systems and render farms with Nimble Studio, to keep your workflows uninterrupted while you move your workforce to the cloud.

With tags, you can categorize your AWS resources by purpose, owner, or environment. This is useful when you have many resources of the same type—you can quickly identify a specific resource based on the tags that you’ve assigned to it.