canonical: https://jentic.com/apis/amazonaws.com/amazon-nimble-studio

# AWS Amazon Nimble Studio

Jentic publishes the only available OpenAPI specification for Amazon Nimble Studio, keeping it validated and agent-ready. Nimble Studio is AWS's managed virtual production studio for visual effects, animation, and game-development teams - it provisions cloud-based artist workstations and rendering capacity. The 49 endpoints cover Studios, StudioComponents (shared file systems, license servers, render farms), LaunchProfiles, StreamingImages, StreamingSessions and the streams that artists connect to, plus EulaAcceptances and StudioMembers for access control.

## For AI agents

Provision and manage cloud-based virtual studios for VFX, animation, and game artists - create studios, launch profiles, streaming sessions, and shared studio components.

## Scope

Does not handle final video transcoding, asset content review, or distribution to end viewers - use for studio, launch profile, and artist streaming session lifecycle only.

## Capabilities

- Provision a virtual Nimble Studio in a region with KMS encryption and admin/user IAM roles
- Define StudioComponents that wire studios to shared file systems, license servers, and render farms
- Create LaunchProfiles that bundle compute, storage, and software for an artist persona
- Manage versioned StreamingImages - base AMIs of artist workstations with pre-installed creative software
- Start, stop, and terminate StreamingSessions that give artists remote access to a workstation
- Issue and rotate stream URLs that artists use to connect via NICE DCV streaming
- Manage StudioMembers and accept the per-studio EULAs required by software vendors

## Use cases

### Stand Up a Cloud-Based VFX Studio

VFX and animation studios need to provision artist workstations on demand without buying hardware. Nimble Studio lets an agent provision a Studio, register StudioComponents for shared file systems and license servers, then create LaunchProfiles per artist persona. Artists request a StreamingSession against a profile and connect via NICE DCV, with all rendering and storage staying in the AWS region.

Example prompt: Call CreateStudio with a studioName and admin/user role ARNs, then CreateLaunchProfile referencing the studio's StudioComponents and a StreamingImage id

### Burst Render Capacity Through Studio Components

Render farms see spiky demand around shot delivery. Nimble Studio's StudioComponents abstract over render-management systems (Deadline, Tractor) so an agent can register a managed or customer-managed render farm component and reference it from launch profiles. Artists submitting render jobs through the workstation see the configured farm without each artist needing to set up their own connection.

Example prompt: Call CreateStudioComponent with Type=RENDER_FARM and a Configuration referencing the render manager's hostname, then list it in the LaunchProfile's StudioComponentIds

### Manage Artist Sessions for Cost and Access

Studios pay for compute by the hour and need tight control over which artists are running which workstations. The StreamingSessions sub-API lets an agent start, stop, and terminate sessions, list currently active sessions, and check ownership against StudioMembers. Combined with EULAs and IAM roles, this provides a complete access surface for the production environment.

Example prompt: Call ListStreamingSessions, identify sessions with State=READY and idle for >2 hours, then call StopStreamingSession to suspend them

### AI Agent Integration for Studio Operations

Through Jentic, a studio operations agent can drive Nimble Studio entirely from natural-language intents - create studios, register components, manage launch profiles, start and stop sessions. Jentic returns each operation's input schema and brokers AWS credentials, so production engineers can build studio automation as LLM tool calls instead of bespoke Lambda scripts.

Example prompt: Resolve the intent 'start a Nimble Studio session for an artist' via Jentic search, load CreateStreamingSession, and execute it with studioId, launchProfileId, ec2InstanceType and ownedBy

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /2020-08-01/studios | Create a new Nimble Studio |
| POST | /2020-08-01/studios/{studioId}/launch-profiles | Create a launch profile in a studio |
| POST | /2020-08-01/studios/{studioId}/streaming-sessions | Start an artist streaming session |
| POST | /2020-08-01/studios/{studioId}/streaming-sessions/{sessionId}/streams | Issue a stream URL for a session |
| POST | /2020-08-01/studios/{studioId}/streaming-images | Register a streaming image with creative software pre-installed |
| POST | /2020-08-01/studios/{studioId}/eula-acceptances | Accept the EULAs required by studio software |

## Key resources

- **Studios** — Provision and configure top-level virtual studios
- **Studio Components** — Register shared file systems, license servers, and render farms used by launch profiles
- **Launch Profiles** — Bundle compute, storage, and software per artist persona
- **Streaming Images** — Manage versioned workstation AMIs with pre-installed creative software
- **Streaming Sessions** — Start, stop, terminate and list artist remote workstations
- **Streaming Session Streams** — Issue and rotate the NICE DCV stream URLs artists connect to
- **Studio Members** — Add, list, and remove studio members and admins
- **EULAs** — List required EULAs and record per-studio acceptances

## Why Jentic

- **Setup:** Wiring Nimble Studio by hand means implementing AWS SigV4 signing, targeting the regional host such as nimble.eu-west-1.amazonaws.com, and polling DescribeStreamingSession through CREATE_IN_PROGRESS states plus wiring EULA acceptances. Through Jentic you install once, import Amazon Nimble Studio from the API Directory, store the AWS access key once, and your agent calls it.
- **Permission scoping:** Nimble Studio puts the studio id in the URL path (/2020-08-01/studios/{studioId}/...), so a rule can pin your agent to one studio: it can manage launch profiles and streaming sessions for that studio and nothing else. You choose the operations it may call, so destructive ones like studio or session deletion are not included unless you add them.
- **Credential handling:** Your AWS access key is stored once, encrypted, by your own Jentic One instance and used to sign each Nimble Studio request with SigV4 at execution time. The raw secret never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'start a Nimble Studio streaming session' or 'create a launch profile', and Jentic returns the matching Nimble Studio operation such as CreateStreamingSession with its input schema so the agent calls the right endpoint without browsing the AWS reference.

## Related APIs

- **Amazon AppStream 2.0** — AppStream 2.0 streams general-purpose Windows applications over a managed NICE DCV pipeline
- **Amazon EC2** — EC2 underpins the streaming instances and render workers that Nimble Studio orchestrates
- **AWS Elemental MediaStore** — MediaStore stores and serves the rendered media output by a Nimble Studio production

## FAQ

### Why is there no official OpenAPI spec for Amazon Nimble Studio?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon Nimble Studio via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Amazon Nimble Studio API use?

Nimble Studio is signed with AWS Signature Version 4 using IAM access keys. Studios additionally have admin and user role ARNs that gate which members can manage versus consume studio resources. Through Jentic, AWS credentials live in your Jentic One instance and are used to sign requests on the agent's behalf.

### Can I run third-party creative software on a Nimble Studio workstation?

Yes. StreamingImages are AMIs that you build with the required creative software (Maya, Houdini, Nuke, etc.) and register against a studio. Each StreamingImage tracks owner, encryption configuration and software-specific EULAs that members must accept before starting a session.

### What are the rate limits for the Nimble Studio API?

AWS applies per-account control-plane throttling to Nimble Studio. Session start operations are not instantaneous - DescribeStreamingSession returns a State of CREATE_IN_PROGRESS, READY, STOPPED, etc. and should be polled rather than retrying the create call.

### How do I start an artist session through Jentic?

Use the Jentic search query 'start a Nimble Studio session', load CreateStreamingSession, and execute it with studioId, launchProfileId, ec2InstanceType, ownedBy and a streamingImageId. Jentic signs the call with SigV4 against your stored AWS credentials and returns the sessionId so the agent can then issue a stream URL.

### Is Amazon Nimble Studio free?

There is no charge for the Nimble Studio control plane itself, but the underlying compute (EC2 streaming instances), storage and any third-party software licences are billed separately. Costs are heavily driven by streaming session run time, so an agent that stops idle sessions is one of the highest-leverage automations on this API.

### Can I limit what my agent is allowed to do with the Amazon Nimble Studio API?

Yes. Because you run Jentic One yourself, your own rules decide which Nimble Studio operations and AWS credentials the agent may use. Since the studio id sits in the URL path (/2020-08-01/studios/{studioId}/...), a rule can pin the agent to a single studio so it manages only that studio's launch profiles and streaming sessions. You also choose the specific operations it can call, so destructive actions like studio or session deletion stay out of reach unless you explicitly grant them.