{"id":285,"date":"2026-04-13T12:11:39","date_gmt":"2026-04-13T12:11:39","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/aws-amazon-nimble-studio-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-media\/"},"modified":"2026-04-13T12:11:39","modified_gmt":"2026-04-13T12:11:39","slug":"aws-amazon-nimble-studio-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-media","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/tutorials\/aws-amazon-nimble-studio-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-media\/","title":{"rendered":"AWS Amazon Nimble Studio Tutorial: Architecture, Pricing, Use Cases, and Hands-On Guide for Media"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Category<\/h2>\n\n\n\n<p>Media<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Introduction<\/h2>\n\n\n\n<p>Amazon Nimble Studio is an AWS service designed to help teams build a cloud-based digital content creation (DCC) studio for Media and entertainment work\u2014think 3D animation, VFX, game cinematics, and design\u2014without having to assemble every infrastructure component from scratch.<\/p>\n\n\n\n<p>In simple terms: Amazon Nimble Studio lets artists and creative teams securely log into powerful cloud workstations (streaming sessions), access shared project storage, and collaborate using familiar creative software\u2014while the underlying AWS networking, identity, and compute building blocks are managed and integrated in a \u201cstudio\u201d experience.<\/p>\n\n\n\n<p>Technically, Amazon Nimble Studio orchestrates identity integration, network access, and workstation streaming on AWS, typically using Amazon EC2 for GPU\/CPU compute, shared storage (commonly Amazon FSx and\/or Amazon S3 depending on your studio design), and secure remote display technology (NICE DCV is commonly used in AWS virtual workstation solutions). Nimble Studio adds a studio-centric control plane: you define who can access the studio, what workstation configurations they can launch, what storage they can mount, and what network routes they can reach.<\/p>\n\n\n\n<p>The problem it solves: building secure, scalable cloud creative workstations and shared studio environments is hard. You must connect identity, permissions, networks, images, storage, and remote access while keeping performance and costs predictable. Amazon Nimble Studio reduces that integration burden and provides a studio-level abstraction for operating creative pipelines on AWS.<\/p>\n\n\n\n<blockquote>\n<p>Service status note: Amazon Nimble Studio is an official AWS service name. Always verify current availability, supported Regions, and any lifecycle announcements on the AWS product page and documentation before implementing in production:\n&#8211; https:\/\/aws.amazon.com\/nimble-studio\/\n&#8211; https:\/\/docs.aws.amazon.com\/nimble-studio\/<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">2. What is Amazon Nimble Studio?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Official purpose<\/h3>\n\n\n\n<p>Amazon Nimble Studio helps customers create a cloud-based studio environment on AWS so creative teams can produce digital content faster by spinning up on-demand workstations, collaborating through shared storage, and operating within a centrally managed studio.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Core capabilities (high level)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Provision and manage a \u201cstudio\u201d environment with integrated AWS resources.<\/li>\n<li>Provide secure remote access to cloud workstations (streaming sessions).<\/li>\n<li>Centralize administration of users, permissions, and workstation \u201claunch profiles.\u201d<\/li>\n<li>Integrate shared storage and data access patterns needed for Media pipelines.<\/li>\n<li>Support studio operations like image management and controlled access to software environments (exact mechanisms vary\u2014verify in official docs for your use case).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Major components (conceptual)<\/h3>\n\n\n\n<p>While exact terminology and features can evolve, the Nimble Studio experience generally revolves around:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Studio<\/strong>: The top-level environment representing your cloud studio boundary.<\/li>\n<li><strong>Identity integration<\/strong>: Authentication\/authorization for artists and administrators. Commonly involves AWS IAM Identity Center and\/or AWS Directory Service integration (verify current supported options).<\/li>\n<li><strong>Launch profiles<\/strong>: Admin-defined profiles that control what users can launch (workstation types, permissions, and configuration).<\/li>\n<li><strong>Streaming sessions \/ Workstations<\/strong>: Remote desktop sessions backed by Amazon EC2 instances (often GPU-enabled for DCC).<\/li>\n<li><strong>Storage integration<\/strong>: Shared filesystems and\/or object storage used by projects (commonly Amazon FSx and Amazon S3, depending on design).<\/li>\n<li><strong>Networking<\/strong>: VPC, subnets, security groups, routing, and connectivity to on-premises if needed.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Service type<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Managed service \/ control plane<\/strong> that orchestrates and integrates AWS infrastructure components into a studio workflow.<\/li>\n<li>The data plane (compute, storage, network traffic) is typically standard AWS resources in your account.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scope: regional\/account\/project<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Account-scoped<\/strong>: Studios are created within an AWS account.<\/li>\n<li><strong>Regional<\/strong>: Studio resources are deployed into a specific AWS Region. Region availability varies\u2014verify via:<\/li>\n<li>AWS Regional Services List \/ endpoints: https:\/\/aws.amazon.com\/about-aws\/global-infrastructure\/regional-product-services\/<\/li>\n<li>Nimble Studio docs and console Region selector.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How it fits into the AWS ecosystem<\/h3>\n\n\n\n<p>Amazon Nimble Studio sits in the AWS <strong>Media<\/strong> and creative compute space alongside (and sometimes overlapping with) services such as:\n&#8211; <strong>Amazon EC2<\/strong> (GPU instances for workstations and render)\n&#8211; <strong>Amazon FSx<\/strong> (shared storage)\n&#8211; <strong>Amazon S3<\/strong> (asset storage, transfer, archiving)\n&#8211; <strong>AWS IAM \/ IAM Identity Center<\/strong> (identity and access control)\n&#8211; <strong>Amazon VPC<\/strong> (networking)\n&#8211; <strong>Amazon CloudWatch \/ AWS CloudTrail<\/strong> (monitoring and auditing)<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">3. Why use Amazon Nimble Studio?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Business reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Faster time to studio<\/strong>: Stand up a functional cloud studio without months of bespoke infrastructure work.<\/li>\n<li><strong>Elastic capacity<\/strong>: Scale workstations up\/down based on production cycles, deadlines, and staffing changes.<\/li>\n<li><strong>Remote\/hybrid enablement<\/strong>: Support distributed teams without shipping high-end hardware everywhere.<\/li>\n<li><strong>Global collaboration<\/strong>: Run in AWS Regions closer to artists or data (subject to service availability and latency constraints).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Technical reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Integrated building blocks<\/strong>: Networking, identity, and workstation access are connected through a studio-centric model.<\/li>\n<li><strong>Standard AWS primitives<\/strong>: Under the hood, you can still use EC2, FSx, S3, IAM, CloudWatch\u2014reducing lock-in risk versus proprietary stacks (though there is still service-specific configuration).<\/li>\n<li><strong>Repeatable configuration<\/strong>: Launch profiles and studio configuration help standardize environments.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operational reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Centralized governance<\/strong>: Admins can manage access and workstation types without granting broad AWS console access to artists.<\/li>\n<li><strong>Simplified onboarding<\/strong>: Add users\/groups to the studio rather than hand-assembling permissions per pipeline component.<\/li>\n<li><strong>Observability integration<\/strong>: Leverage CloudWatch metrics\/logs and CloudTrail events for operations.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security\/compliance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Private networking options<\/strong>: Studio components can be deployed into private subnets; access can be routed through controlled egress and\/or VPN\/Direct Connect (architecture-dependent).<\/li>\n<li><strong>Fine-grained access<\/strong>: Use IAM and integrated identity to enforce least privilege.<\/li>\n<li><strong>Auditing<\/strong>: CloudTrail provides API-level auditing of AWS actions.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scalability\/performance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Right-size compute<\/strong>: Choose GPU\/CPU instances per workload; scale to many concurrent artists.<\/li>\n<li><strong>Storage performance<\/strong>: Use AWS storage designed for high throughput and shared access patterns (design carefully to meet pipeline needs).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should choose it<\/h3>\n\n\n\n<p>Choose Amazon Nimble Studio when you need:\n&#8211; A managed path to <strong>cloud-based creative workstations<\/strong>\n&#8211; <strong>Shared project storage<\/strong> integrated with workstations\n&#8211; Central management of <strong>who can launch what<\/strong>, without exposing raw AWS infrastructure to every end user\n&#8211; A studio boundary that can grow from a small pilot to production<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should not choose it<\/h3>\n\n\n\n<p>Consider alternatives when:\n&#8211; You only need a few generic desktops (e.g., office productivity) \u2192 <strong>Amazon WorkSpaces<\/strong> might fit better.\n&#8211; You already operate a mature VDI\/remote workstation stack and only need EC2 + storage \u2192 consider <strong>EC2 + NICE DCV<\/strong> or your existing VDI platform.\n&#8211; You need application streaming rather than full desktop sessions \u2192 <strong>Amazon AppStream 2.0<\/strong> can be simpler.\n&#8211; Your workloads are extremely latency sensitive and you can\u2019t place artists near a supported AWS Region.\n&#8211; Your software licensing model forbids cloud execution, or you cannot meet compliance requirements in AWS Regions available to Nimble Studio.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">4. Where is Amazon Nimble Studio used?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Industries<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Film and TV (VFX, animation)<\/li>\n<li>Game development (cinematics, asset creation)<\/li>\n<li>Advertising and marketing (3D product renders)<\/li>\n<li>Architecture\/engineering visualization<\/li>\n<li>Education and training (DCC labs)<\/li>\n<li>XR\/VR content production (where tooling supports cloud execution)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Team types<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Creative studios with artists, animators, modelers<\/li>\n<li>Media pipeline engineering teams<\/li>\n<li>IT\/platform teams supporting creative applications<\/li>\n<li>Security and compliance teams managing access to IP<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Workloads<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Interactive DCC work: modeling, rigging, animation, look-dev<\/li>\n<li>Texture painting and compositing<\/li>\n<li>Shot work with shared assets<\/li>\n<li>Review and iteration workflows (when integrated with collaboration\/review tooling)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Architectures<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud-first studio (all assets and compute in AWS)<\/li>\n<li>Hybrid studio (on-prem storage + AWS burst compute)<\/li>\n<li>Remote work enablement (artists connect from home to cloud workstations)<\/li>\n<li>Multi-account setups (shared services + production accounts) with careful IAM and network design<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Real-world deployment contexts<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Production<\/strong>: standardized images, controlled egress, central storage, consistent naming\/tagging, monitoring, and cost controls<\/li>\n<li><strong>Dev\/test<\/strong>: small pilot studios, experimentation with GPU types, validating identity integration, testing storage throughput and latency<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">5. Top Use Cases and Scenarios<\/h2>\n\n\n\n<p>Below are realistic scenarios where Amazon Nimble Studio is commonly considered. Each includes the problem, why it fits, and a short example.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Rapid cloud studio pilot for a small art team<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Need to test cloud workstations and shared storage quickly without building everything from scratch.<\/li>\n<li><strong>Why this fits<\/strong>: Studio setup and launch profiles provide a structured pilot path.<\/li>\n<li><strong>Example<\/strong>: A 10-person animation team runs a 2-week proof of concept using a preconfigured studio and a small shared filesystem.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Elastic burst capacity for peak production<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: On-prem GPU workstations are fully utilized during crunch time.<\/li>\n<li><strong>Why this fits<\/strong>: Add cloud workstations only when needed; shut them down after deadlines.<\/li>\n<li><strong>Example<\/strong>: A VFX studio bursts to 50 additional GPU sessions for final compositing.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Secure remote workstations for distributed artists<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Artists need access to licensed tools and IP securely from home.<\/li>\n<li><strong>Why this fits<\/strong>: Centralized access control, private networking, auditable activity, and no need to store assets locally on endpoints (architecture-dependent).<\/li>\n<li><strong>Example<\/strong>: Contractors access only the shot folder they are assigned, from streaming sessions in a locked-down subnet.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Standardized workstation environments via curated images<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Inconsistent software versions and plugins cause pipeline issues.<\/li>\n<li><strong>Why this fits<\/strong>: Studio admins define approved workstation images and launch profiles.<\/li>\n<li><strong>Example<\/strong>: All artists run the same DCC build and plugin set for a show.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Multi-project separation with shared platform<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Multiple shows\/projects share IT but must isolate data and access.<\/li>\n<li><strong>Why this fits<\/strong>: Use separate studios, separate storage, or separate launch profiles and directory groups.<\/li>\n<li><strong>Example<\/strong>: Two productions share the same AWS account baseline but use distinct studios and storage paths.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Hybrid integration with on-premises services<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Some services remain on-prem (license servers, render management, legacy storage).<\/li>\n<li><strong>Why this fits<\/strong>: VPC connectivity (VPN\/Direct Connect) can extend studio access to on-prem resources.<\/li>\n<li><strong>Example<\/strong>: Workstations in AWS reach a floating license server over a site-to-site VPN.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Training lab for a DCC classroom<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: A school needs a temporary lab with expensive GPU workstations for a course.<\/li>\n<li><strong>Why this fits<\/strong>: Spin up standardized sessions per student; shut down after the semester.<\/li>\n<li><strong>Example<\/strong>: 30 students receive identical cloud workstations for Maya\/Blender-based assignments.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Controlled vendor access for outsourcing<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: External vendors need to contribute without receiving full copies of assets.<\/li>\n<li><strong>Why this fits<\/strong>: Limit access via profiles\/groups; keep assets in controlled storage.<\/li>\n<li><strong>Example<\/strong>: A vendor logs into a workstation that only sees a subset of S3\/FSx paths.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) Disaster recovery \/ continuity for creative operations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: On-prem workstation floor is unavailable (office outage).<\/li>\n<li><strong>Why this fits<\/strong>: Cloud workstations can act as a fallback environment if assets are accessible.<\/li>\n<li><strong>Example<\/strong>: Artists resume critical work from home using AWS-based sessions.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Regional expansion without building new facilities<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Opening a new studio location takes time and capital.<\/li>\n<li><strong>Why this fits<\/strong>: Launch a studio in an AWS Region closer to the new team (subject to availability).<\/li>\n<li><strong>Example<\/strong>: A company expands to a new country and uses cloud workstations for the first year.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">11) Temporary render\/look-dev sandbox (interactive)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Need temporary high-end machines for look-dev exploration.<\/li>\n<li><strong>Why this fits<\/strong>: Short-lived sessions and right-sized instances.<\/li>\n<li><strong>Example<\/strong>: A lighting artist spins up a larger GPU instance for a day, then goes back to standard.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">12) Secure, audited environment for sensitive IP<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: A project requires strict audit trails and minimal endpoint exposure.<\/li>\n<li><strong>Why this fits<\/strong>: Use IAM, CloudTrail, encrypted storage, and restricted networks to reduce risk.<\/li>\n<li><strong>Example<\/strong>: A pre-release game cinematic is produced in a studio with tightly controlled egress.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">6. Core Features<\/h2>\n\n\n\n<blockquote>\n<p>Note: Feature names and exact configuration steps can evolve. Validate in the official documentation for your Region and console experience: https:\/\/docs.aws.amazon.com\/nimble-studio\/<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Studio provisioning and management<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Creates a studio environment that coordinates identity, networking, storage, and workstation access.<\/li>\n<li><strong>Why it matters<\/strong>: Provides a consistent \u201cstudio boundary\u201d rather than ad hoc EC2 instances.<\/li>\n<li><strong>Practical benefit<\/strong>: Faster onboarding and standardized operations.<\/li>\n<li><strong>Caveats<\/strong>: Some underlying resources remain your responsibility to manage (patching strategies, image maintenance, storage lifecycle, etc.).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Identity integration for studio users<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Lets you control which users can access the studio and what they can do, usually through integration with AWS identity services.<\/li>\n<li><strong>Why it matters<\/strong>: Artists generally should not need AWS console access.<\/li>\n<li><strong>Practical benefit<\/strong>: Central user lifecycle (joiners\/movers\/leavers).<\/li>\n<li><strong>Caveats<\/strong>: Directory design (Managed AD vs connector\/federation) affects cost, complexity, and security. Verify current identity options supported by Nimble Studio.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Launch profiles (role-based workstation access)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Defines what a user can launch (e.g., allowed workstation types, permissions, storage mounts, and possibly software environment policies).<\/li>\n<li><strong>Why it matters<\/strong>: Enforces guardrails and standardization.<\/li>\n<li><strong>Practical benefit<\/strong>: \u201cAnimators get profile A; compositors get profile B.\u201d<\/li>\n<li><strong>Caveats<\/strong>: Poor profile design can create cost overruns (too-large instances) or productivity hits (too-small instances).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Streaming sessions \/ virtual workstations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Lets users start remote desktop sessions backed by cloud compute.<\/li>\n<li><strong>Why it matters<\/strong>: This is the core day-to-day interactive experience for artists.<\/li>\n<li><strong>Practical benefit<\/strong>: Fast provisioning and scale-out capacity.<\/li>\n<li><strong>Caveats<\/strong>: User experience depends on latency to the Region, instance type (GPU), storage performance, and display protocol configuration.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Image management (workstation images)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Supports using standardized machine images for workstation sessions.<\/li>\n<li><strong>Why it matters<\/strong>: Consistency across the team.<\/li>\n<li><strong>Practical benefit<\/strong>: Reproducible environments and easier support.<\/li>\n<li><strong>Caveats<\/strong>: Image updates must be managed carefully (patch windows, plugin\/version control, testing). Verify Nimble Studio\u2019s recommended image pipeline.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Shared storage integration<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Provides shared access to assets and project data via integrated storage.<\/li>\n<li><strong>Why it matters<\/strong>: Media workflows rely on shared datasets and consistent paths.<\/li>\n<li><strong>Practical benefit<\/strong>: Multiple artists can work from the same source assets and caches (when designed properly).<\/li>\n<li><strong>Caveats<\/strong>: Performance and cost depend heavily on storage type and access pattern. Some DCC workflows are extremely IOPS-heavy.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Networking and connectivity controls<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Deploys studio resources into a VPC and controls access through subnets, security groups, and routing.<\/li>\n<li><strong>Why it matters<\/strong>: Security posture depends on tight network design.<\/li>\n<li><strong>Practical benefit<\/strong>: Private subnets, controlled egress, optional on-prem connectivity.<\/li>\n<li><strong>Caveats<\/strong>: Misconfigured egress can leak IP; misconfigured routing can break license server connectivity.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Monitoring and audit integration (via AWS)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Supports operational visibility through CloudWatch and auditing through CloudTrail at the AWS API level.<\/li>\n<li><strong>Why it matters<\/strong>: Production requires troubleshooting, auditing, and governance.<\/li>\n<li><strong>Practical benefit<\/strong>: Detect unusual activity, session behavior, and infrastructure drift.<\/li>\n<li><strong>Caveats<\/strong>: You must decide what to log, where to store it, and how long to retain it.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">7. Architecture and How It Works<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">High-level architecture<\/h3>\n\n\n\n<p>Amazon Nimble Studio provides a control plane to:\n1. Define studio configuration (identity, network, storage, session policies).\n2. Define user access and launch profiles.\n3. Let users launch streaming sessions (workstations) that run in your AWS account.<\/p>\n\n\n\n<p>The data plane involves:\n&#8211; Remote display traffic between user endpoints and workstation instances.\n&#8211; Asset reads\/writes between workstations and shared storage (FSx\/S3).\n&#8211; Optional connectivity from workstations to license servers or other tools.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Request\/data\/control flow (typical)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Admin<\/strong> creates a studio and configures identity integration, networking, and storage.<\/li>\n<li><strong>Admin<\/strong> defines launch profiles (allowed instance types\/images, permissions).<\/li>\n<li><strong>User<\/strong> authenticates (via configured identity provider).<\/li>\n<li><strong>User<\/strong> launches a workstation session using an approved launch profile.<\/li>\n<li><strong>Workstation<\/strong> mounts\/uses shared storage and accesses required services.<\/li>\n<li><strong>User<\/strong> works interactively via streaming protocol; assets remain in AWS storage (unless downloaded intentionally\/accidentally).<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Integrations with related AWS services (common)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Amazon EC2<\/strong>: workstation instances (often GPU).<\/li>\n<li><strong>Amazon VPC<\/strong>: subnets, routing, security groups, endpoints.<\/li>\n<li><strong>AWS IAM<\/strong>: service permissions and roles.<\/li>\n<li><strong>AWS IAM Identity Center<\/strong> (or other identity integration): user access management (verify exact supported flow).<\/li>\n<li><strong>AWS Directory Service<\/strong>: managed directory services (Managed Microsoft AD or connectors; verify).<\/li>\n<li><strong>Amazon FSx<\/strong>: shared filesystem for studio data (verify which FSx types are supported\/recommended for your design).<\/li>\n<li><strong>Amazon S3<\/strong>: asset storage, ingest\/export, backups\/archives.<\/li>\n<li><strong>AWS KMS<\/strong>: encryption keys for storage and secrets where applicable.<\/li>\n<li><strong>Amazon CloudWatch<\/strong>: metrics\/logs for instances and components.<\/li>\n<li><strong>AWS CloudTrail<\/strong>: audit logs for API actions.<\/li>\n<li><strong>AWS Systems Manager<\/strong>: patching\/automation for workstation images and instances (often recommended).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Dependency services<\/h3>\n\n\n\n<p>Even though Nimble Studio is the \u201cservice,\u201d your actual spend and operations depend on:\n&#8211; EC2 instance hours (and EBS)\n&#8211; Storage (FSx\/S3\/EBS snapshots)\n&#8211; Networking (NAT gateways, VPN, data transfer)\n&#8211; Directory services (if used)\n&#8211; Logging\/monitoring retention<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Security\/authentication model (conceptual)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Users authenticate through the configured identity mechanism.<\/li>\n<li>Authorization is enforced by Nimble Studio constructs (e.g., launch profiles) and IAM roles\/policies backing those constructs.<\/li>\n<li>Workstations typically assume roles for accessing storage and required AWS APIs (least privilege required).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Networking model (conceptual)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Studio resources live in a VPC.<\/li>\n<li>Workstations typically run in private subnets; access is delivered through streaming connectivity rather than open inbound RDP\/SSH.<\/li>\n<li>Outbound internet access may be controlled via NAT gateway, egress firewall, VPC endpoints, and explicit allow lists.<\/li>\n<li>On-prem connectivity typically uses AWS Site-to-Site VPN or AWS Direct Connect.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Monitoring\/logging\/governance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Enable <strong>CloudTrail<\/strong> for auditing.<\/li>\n<li>Use <strong>CloudWatch<\/strong> for instance metrics; consider <strong>CloudWatch Logs<\/strong> for system\/application logs.<\/li>\n<li>Use <strong>AWS Config<\/strong> for drift detection and compliance checks (where applicable).<\/li>\n<li>Tag everything consistently to support chargeback\/showback.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Simple architecture diagram (Mermaid)<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart LR\n  U[Artist laptop\/desktop] --&gt;|Authenticate| ID[Identity Provider\\n(IAM Identity Center \/ Directory)\\nVerify supported options]\n  U --&gt;|Streaming display| WS[Cloud Workstation\\n(EC2 GPU\/CPU)]\n  WS --&gt; STG[Shared Storage\\n(FSx\/S3 - depends on design)]\n  ADM[Studio Admin] --&gt; NS[Amazon Nimble Studio\\nControl Plane]\n  NS --&gt; WS\n  NS --&gt; STG\n  NS --&gt; VPC[VPC\/Subnets\/Security Groups]\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Production-style architecture diagram (Mermaid)<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart TB\n  subgraph OnPrem[On-Prem \/ Remote Users]\n    User[Artist Endpoint]\n    Lic[License Server \/ Pipeline Services\\n(Optional)]\n  end\n\n  subgraph AWS[AWS Account - Region]\n    subgraph Net[VPC]\n      subgraph Priv[Private Subnets]\n        WS1[Workstations (EC2)\\nGPU\/CPU]\n        WS2[Workstations (EC2)\\nGPU\/CPU]\n        FSx[(Shared FSx Filesystem\\n(optional \/ common))]\n      end\n\n      subgraph Endpoints[VPC Endpoints (optional)]\n        S3EP[S3 Gateway\/Interface Endpoint]\n        SSMEP[SSM\/EC2Messages Endpoint]\n      end\n\n      NAT[NAT Gateway\\n(optional)]\n      VPN[Site-to-Site VPN \/ Direct Connect\\n(optional)]\n    end\n\n    S3[(Amazon S3\\nAssets\/Backups\/Exchange)]\n    CW[CloudWatch\\nMetrics\/Logs]\n    CT[CloudTrail\\nAudit]\n    KMS[AWS KMS\\nKeys]\n    NS[Amazon Nimble Studio\\nControl Plane]\n    IAM[IAM \/ IAM Identity Center]\n  end\n\n  User --&gt;|Auth| IAM\n  IAM --&gt; NS\n  User --&gt;|Streaming| WS1\n  User --&gt;|Streaming| WS2\n\n  WS1 --&gt; FSx\n  WS2 --&gt; FSx\n  WS1 --&gt; S3\n  WS2 --&gt; S3\n\n  WS1 --&gt; CW\n  WS2 --&gt; CW\n  NS --&gt; CT\n\n  WS1 --&gt;|Optional| VPN\n  VPN --&gt; Lic\n\n  Priv --&gt; NAT\n  NAT --&gt; S3\n  Endpoints --&gt; S3\n  KMS --&gt; S3\n  KMS --&gt; FSx\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">8. Prerequisites<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">AWS account requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An AWS account with billing enabled.<\/li>\n<li>Permission to create IAM roles\/policies and provision resources used by the studio (VPC, EC2, storage, directory services).<\/li>\n<li>If operating in an AWS Organization, ensure SCPs (Service Control Policies) do not block required actions.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Permissions \/ IAM roles<\/h3>\n\n\n\n<p>At minimum, you need a principal (role\/user) that can:\n&#8211; Create\/manage a Nimble Studio studio and related resources.\n&#8211; Create VPC networking components (if using the setup wizard).\n&#8211; Create EC2 instances, security groups, EBS volumes, and possibly image-related resources.\n&#8211; Create\/configure storage (FSx, S3) and encryption (KMS) if used.\n&#8211; Create\/configure directory\/identity integration (AWS Directory Service, IAM Identity Center) if required.<\/p>\n\n\n\n<p><strong>Best practice<\/strong>: Use a dedicated admin role for studio provisioning, and separate roles for day-to-day operations.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Tools<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>AWS Management Console (required for many Nimble Studio setup flows).<\/li>\n<li>AWS CLI v2 (optional but useful). Install: https:\/\/docs.aws.amazon.com\/cli\/latest\/userguide\/getting-started-install.html<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Region availability<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Nimble Studio is <strong>not<\/strong> available in every Region. Confirm in:<\/li>\n<li>AWS console Region selector (service appears only in supported Regions)<\/li>\n<li>Official docs: https:\/\/docs.aws.amazon.com\/nimble-studio\/<\/li>\n<li>Regional services list: https:\/\/aws.amazon.com\/about-aws\/global-infrastructure\/regional-product-services\/<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quotas \/ limits<\/h3>\n\n\n\n<p>Expect limits around:\n&#8211; Number of studios per account\/Region\n&#8211; Number of streaming sessions \/ concurrent workstations\n&#8211; EC2 instance limits (especially GPU families)\n&#8211; Storage quotas (FSx throughput configurations, file systems, etc.)<\/p>\n\n\n\n<p>Check:\n&#8211; AWS Service Quotas: https:\/\/console.aws.amazon.com\/servicequotas\/\n&#8211; EC2 limits: https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/ec2-resource-limits.html<br\/>\nAlso verify Nimble Studio-specific quotas in the docs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisite services (commonly used)<\/h3>\n\n\n\n<p>Depending on your setup:\n&#8211; Amazon VPC\n&#8211; Amazon EC2\n&#8211; Amazon FSx and\/or Amazon S3\n&#8211; AWS Directory Service and\/or IAM Identity Center (verify current supported identity model)\n&#8211; AWS KMS\n&#8211; CloudWatch and CloudTrail<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">9. Pricing \/ Cost<\/h2>\n\n\n\n<blockquote>\n<p>Important: Do not rely on blog posts or third-party summaries for pricing. Always confirm current pricing on the official page and in the AWS Pricing Calculator.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Official pricing references<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Amazon Nimble Studio pricing page: https:\/\/aws.amazon.com\/nimble-studio\/pricing\/<\/li>\n<li>AWS Pricing Calculator: https:\/\/calculator.aws\/#\/<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Pricing dimensions (what you pay for)<\/h3>\n\n\n\n<p>In most Nimble Studio deployments, costs typically come from a combination of:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Nimble Studio service charges<\/strong> (if applicable)<br\/>\n   Some AWS managed \u201corchestration\u201d services have their own pricing dimension (e.g., per user, per studio, per streaming hour). The exact model can change\u2014<strong>verify on the official pricing page<\/strong>.<\/p>\n<\/li>\n<li>\n<p><strong>Workstation compute (Amazon EC2)<\/strong>\n   &#8211; GPU\/CPU instance hours (On-Demand, Savings Plans, Spot where appropriate)\n   &#8211; EBS volumes (size, type, IOPS, snapshots)\n   &#8211; Windows licensing implications if using Windows instances (usually included in EC2 Windows pricing)<\/p>\n<\/li>\n<li>\n<p><strong>Storage<\/strong>\n   &#8211; Amazon FSx (capacity, throughput, backups)\n   &#8211; Amazon S3 (storage class, requests, lifecycle transitions)\n   &#8211; EBS snapshots (for image\/versioning workflows)<\/p>\n<\/li>\n<li>\n<p><strong>Networking<\/strong>\n   &#8211; NAT Gateway hourly + per-GB processing fees (often a major hidden cost)\n   &#8211; Data transfer out of AWS (internet egress)\n   &#8211; Cross-AZ traffic (depending on design)\n   &#8211; VPN\/Direct Connect charges if used<\/p>\n<\/li>\n<li>\n<p><strong>Identity\/Directory services<\/strong>\n   &#8211; AWS Directory Service (Managed Microsoft AD) hourly charges + per-AD size, if used (pricing varies by edition\/size\/Region)\n   &#8211; IAM Identity Center itself is often no additional charge, but verify and consider downstream costs.<\/p>\n<\/li>\n<li>\n<p><strong>Monitoring\/logging<\/strong>\n   &#8211; CloudWatch logs ingestion\/retention\n   &#8211; CloudTrail data events (if enabled for S3 object-level logging)<\/p>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Cost drivers (most common)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>GPU instance hours<\/strong>: the biggest line item in many Media workstation deployments.<\/li>\n<li><strong>Always-on components<\/strong>: directories, file systems, NAT gateways, and persistent storage can accrue cost even when no one is working.<\/li>\n<li><strong>Data egress<\/strong>: transferring large EXR sequences out of AWS is expensive.<\/li>\n<li><strong>Overprovisioned storage throughput<\/strong>: FSx performance settings can materially change cost.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Hidden or indirect costs to plan for<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>NAT Gateway for private subnet egress (hourly + per-GB).<\/li>\n<li>Backup retention (FSx backups, EBS snapshots).<\/li>\n<li>Data transfer between AZs if storage and compute are not placed carefully.<\/li>\n<li>Licensing costs for DCC applications (vendor licensing may require dedicated license servers, cloud-specific terms, or additional fees).<\/li>\n<li>Operational time: image maintenance, patching, and pipeline support.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Network\/data transfer implications<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Prefer <strong>keeping assets and rendering outputs in AWS<\/strong> when possible.<\/li>\n<li>Use <strong>S3 lifecycle<\/strong> to move cold assets to cheaper storage classes.<\/li>\n<li>Use <strong>VPC endpoints<\/strong> (S3\/SSM) to reduce NAT reliance where feasible.<\/li>\n<li>Avoid cross-Region transfers unless you have a strong reason.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How to optimize cost<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Right-size launch profiles: provide multiple tiers (standard, heavy, review-only).<\/li>\n<li>Use schedules\/automation to stop idle workstations.<\/li>\n<li>Consider Spot for non-interactive workloads (interactive artist desktops are usually not ideal for Spot interruptions).<\/li>\n<li>Use VPC endpoints to reduce NAT costs.<\/li>\n<li>Tag by project\/show, department, and environment to enable chargeback\/showback.<\/li>\n<li>Set budgets and alerts: https:\/\/docs.aws.amazon.com\/cost-management\/latest\/userguide\/budgets-managing-costs.html<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Example low-cost starter estimate (model, not numbers)<\/h3>\n\n\n\n<p>A small pilot typically includes:\n&#8211; 1 studio\n&#8211; A small number of users\n&#8211; 1\u20133 intermittent workstations (EC2) during working hours\n&#8211; Small shared storage (FSx\/S3)\n&#8211; Basic logging<\/p>\n\n\n\n<p>Your largest pilot variables:\n&#8211; Workstation instance type (GPU vs CPU)\n&#8211; Hours used per day\n&#8211; Whether directory services and NAT gateways run 24\/7<\/p>\n\n\n\n<p>Use the AWS Pricing Calculator with:\n&#8211; EC2 instance type + hours\/month\n&#8211; FSx capacity\/throughput + backups\n&#8211; S3 storage amount + requests\n&#8211; NAT gateway hours + estimated GB processed\n&#8211; Directory service monthly cost (if used)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Example production cost considerations (what changes)<\/h3>\n\n\n\n<p>In production, add:\n&#8211; Many concurrent workstations with predictable baseline usage\n&#8211; Multiple launch profiles and curated images\n&#8211; Higher performance shared storage\n&#8211; Backup\/DR strategy (snapshots, replication, archival)\n&#8211; Multi-Region considerations (if applicable)\n&#8211; Stronger logging and longer retention<\/p>\n\n\n\n<p>A realistic production estimate requires measurement:\n&#8211; Average and peak concurrent sessions\n&#8211; Storage IOPS\/throughput requirements\n&#8211; Data egress patterns (review, client delivery, outsourcing)<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">10. Step-by-Step Hands-On Tutorial<\/h2>\n\n\n\n<p>This lab walks through creating a basic Amazon Nimble Studio environment and launching a test streaming session. It focuses on a safe, beginner-friendly path using the AWS Console and the Nimble Studio setup experience.<\/p>\n\n\n\n<blockquote>\n<p>Important constraints:\n&#8211; The exact console wizard steps can evolve. Follow the current UI and cross-check with the official \u201cGetting started\u201d guide.\n&#8211; This lab can incur costs (directory services, NAT gateway, EC2, FSx). Use a dedicated sandbox account if possible and clean up afterward.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Objective<\/h3>\n\n\n\n<p>Create an Amazon Nimble Studio studio in a supported AWS Region, set up a minimal user access path, create or use a launch profile, and start a test workstation streaming session.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Lab Overview<\/h3>\n\n\n\n<p>You will:\n1. Choose a supported Region and confirm prerequisites.\n2. Create a studio using the Nimble Studio console setup.\n3. Configure user access (identity integration) and assign a test user.\n4. Create or review a launch profile and streaming configuration.\n5. Launch a workstation session and validate connectivity.\n6. Clean up all resources to stop charges.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Choose a supported Region and prepare your admin role<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Sign in to the <strong>AWS Management Console<\/strong> with an admin role suitable for provisioning (in a sandbox account if possible).<\/li>\n<li>In the Region selector, choose a Region where <strong>Amazon Nimble Studio is available<\/strong>.<\/li>\n<li>Confirm you can open the service console:\n   &#8211; https:\/\/console.aws.amazon.com\/nimble-studio\/<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; The Nimble Studio console loads and allows you to start creating a studio.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; If the service is not available in the selected Region, the console may redirect or show an error. Switch Regions and try again.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Start \u201cCreate studio\u201d and select a setup option<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In the Nimble Studio console, choose <strong>Create studio<\/strong>.<\/li>\n<li>Select the setup approach offered by the console (commonly a guided setup that provisions required AWS resources).<\/li>\n<li>Provide:\n   &#8211; <strong>Studio name<\/strong> (e.g., <code>nimble-lab-studio<\/code>)\n   &#8211; <strong>Display name<\/strong> (optional)\n   &#8211; Any required <strong>networking<\/strong> choices (create new VPC vs use existing)<\/li>\n<\/ol>\n\n\n\n<p><strong>Design guidance (beginner-friendly)<\/strong>\n&#8211; For a lab, using the guided option to create a new VPC is usually simplest.\n&#8211; For production, you often use an existing network baseline with standardized routing, endpoints, and security controls.<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; The wizard proceeds to configure identity, networking, and storage options.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; The wizard shows a summary of resources it will create (review carefully to avoid surprises like always-on NAT gateways or directories).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Configure identity and user access<\/h3>\n\n\n\n<p>Identity configuration is one of the most important parts of Nimble Studio. The console may offer options involving AWS identity services.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Follow the wizard to configure <strong>authentication<\/strong> for studio users.<\/li>\n<li>If the wizard requires directory services, choose the option appropriate for a lab:\n   &#8211; A managed directory can be easiest for quick testing, but it may be <strong>always-on cost<\/strong>.<\/li>\n<li>Create or select a <strong>test user<\/strong> (or group) who will be allowed to access the studio.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You have a way to sign in as a studio user (artist) separate from the admin.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; The studio\u2019s \u201cUsers\u201d or \u201cDirectory\/Identity\u201d section shows your user\/group mapped to the studio.<\/p>\n\n\n\n<p><strong>Common pitfall<\/strong>\n&#8211; Getting locked out due to group membership not applied yet. Some directory changes take time to propagate.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Review or create studio storage<\/h3>\n\n\n\n<p>Most creative workflows require shared storage.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In the wizard (or after studio creation), review the storage configuration.<\/li>\n<li>Confirm:\n   &#8211; Which storage is created\/attached (for example, shared filesystem and\/or S3 locations).\n   &#8211; Encryption settings (SSE-KMS for S3, KMS for filesystem where supported).<\/li>\n<li>Note the storage paths that the workstation sessions will mount\/use.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; The studio has at least one shared storage location for data exchange.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; The studio configuration lists the storage resources and indicates they are \u201cReady\/Active.\u201d<\/p>\n\n\n\n<p><strong>Cost note<\/strong>\n&#8211; Filesystems and backups may cost money even when no one is logged in. Plan cleanup.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Create or validate a launch profile<\/h3>\n\n\n\n<p>Launch profiles define what users can start.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In Nimble Studio console, locate <strong>Launch profiles<\/strong>.<\/li>\n<li>Create a new launch profile (or use an existing default one created by the setup).<\/li>\n<li>Configure:\n   &#8211; The user\/group assignment\n   &#8211; Allowed workstation configurations (instance types)\n   &#8211; Any storage mounts or environment settings required by the profile<\/li>\n<\/ol>\n\n\n\n<p><strong>Beginner-friendly recommendation<\/strong>\n&#8211; Provide a small\/medium profile tier for testing. GPU instances are often required for DCC, but they are more expensive.<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; A launch profile is available and assigned to your test user.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; From the user view (or user portal), the profile appears as an option to launch a workstation.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 6: Launch a workstation streaming session<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Sign in as the <strong>test user<\/strong> using the configured identity method.<\/li>\n<li>Open the studio portal\/user access point provided by Nimble Studio (console typically provides a link).<\/li>\n<li>Choose the launch profile and start a <strong>streaming session<\/strong> (workstation).<\/li>\n<li>Wait for the session to provision and become available, then connect.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You see a remote desktop session running in AWS.<\/p>\n\n\n\n<p><strong>Verification checklist<\/strong>\n&#8211; The desktop loads and is responsive.\n&#8211; You can access the shared storage location from within the session (mapped drive or mounted filesystem, depending on OS\/config).\n&#8211; Network access aligns with your expectations (e.g., you cannot arbitrarily reach the public internet if you intended a restricted egress design).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 7 (Optional): Validate via AWS CLI (if your account enables Nimble Studio API access)<\/h3>\n\n\n\n<p>If the AWS CLI supports Nimble Studio in your environment, you can try:<\/p>\n\n\n\n<pre><code class=\"language-bash\">aws --version\naws nimble list-studios --region &lt;your-region&gt;\n<\/code><\/pre>\n\n\n\n<p>To get details (example pattern\u2014verify exact command names in the AWS CLI reference):<\/p>\n\n\n\n<pre><code class=\"language-bash\">aws nimble get-studio --studio-id &lt;studio-id&gt; --region &lt;your-region&gt;\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You can list and describe studio resources programmatically.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Output includes your studio name and status.<\/p>\n\n\n\n<p><strong>Note<\/strong>\n&#8211; If commands fail, confirm your AWS CLI version and whether Nimble Studio is available in your Region\/account. Use official CLI docs:\n  &#8211; https:\/\/docs.aws.amazon.com\/cli\/latest\/reference\/<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Validation<\/h3>\n\n\n\n<p>Use this checklist to confirm the lab succeeded:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>[ ] Studio status shows <strong>Ready\/Active<\/strong> in the Nimble Studio console.<\/li>\n<li>[ ] A test user can authenticate and see the studio portal.<\/li>\n<li>[ ] The test user can launch a streaming session from an allowed launch profile.<\/li>\n<li>[ ] The workstation can access the intended storage.<\/li>\n<li>[ ] CloudTrail is recording management events in the Region.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Troubleshooting<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\">Issue: \u201cService not available in this Region\u201d<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Switch to a Region where Amazon Nimble Studio is supported.<\/li>\n<li>Confirm via AWS regional services list and the Nimble Studio documentation.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Issue: Streaming session fails to start<\/h4>\n\n\n\n<p>Common causes:\n&#8211; EC2 GPU instance capacity unavailable in the selected AZ\n&#8211; EC2 quota limits for the chosen instance family\n&#8211; Misconfigured networking (no route to required endpoints, blocked security groups)\n&#8211; Missing IAM permissions for session roles<\/p>\n\n\n\n<p>Fixes:\n&#8211; Try a different instance type or AZ (if configurable).\n&#8211; Request quota increases in <strong>Service Quotas<\/strong>.\n&#8211; Add required VPC endpoints or allow controlled egress temporarily to test.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Issue: User can sign in but cannot see launch profile<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Confirm the user\/group is assigned to the launch profile.<\/li>\n<li>Confirm directory group membership has propagated.<\/li>\n<li>Verify identity mapping settings in the studio.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Issue: Storage not accessible from workstation<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Confirm mount configuration in launch profile.<\/li>\n<li>Confirm security group rules between workstation and storage.<\/li>\n<li>Confirm DNS and directory integration are correct (especially for Windows shares).<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Cleanup<\/h3>\n\n\n\n<p>To avoid ongoing charges, clean up in this order:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Terminate streaming sessions\/workstations<\/strong> from the Nimble Studio user portal or console.<\/li>\n<li>In the Nimble Studio console, <strong>delete the studio<\/strong> (if the console provides a delete workflow).<\/li>\n<li>Identify and delete underlying resources created by the wizard (as applicable):\n   &#8211; EC2 instances (including image builders)\n   &#8211; EBS volumes and snapshots not needed\n   &#8211; FSx filesystems and backups\n   &#8211; S3 buckets (after emptying them)\n   &#8211; Directory Service directories (be cautious\u2014deleting directories can affect other systems)\n   &#8211; NAT gateways and related Elastic IPs\n   &#8211; VPC endpoints\n   &#8211; VPC (only if dedicated to this lab and safe to remove)<\/li>\n<li>Verify in <strong>Billing and Cost Management<\/strong> that no always-on resources remain.<\/li>\n<\/ol>\n\n\n\n<p><strong>Best practice<\/strong>\n&#8211; Use a dedicated \u201clab\u201d tag (e.g., <code>Project=nimble-lab<\/code>) and search the Resource Groups Tag Editor to find everything:\n  &#8211; https:\/\/console.aws.amazon.com\/resource-groups\/tag-editor<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">11. Best Practices<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Architecture best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Start with a reference design<\/strong>: define identity, networking, storage, and image strategy before onboarding artists.<\/li>\n<li><strong>Separate environments<\/strong>: dev\/test studios should not share the same storage and credentials as production.<\/li>\n<li><strong>Plan for pipeline dependencies<\/strong>: license servers, asset management, render orchestration, and review tools need connectivity and security review.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">IAM\/security best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Least privilege<\/strong>: restrict what workstation roles can do in AWS APIs (especially S3 bucket access).<\/li>\n<li><strong>Separate admin roles<\/strong>: studio provisioning vs day-to-day studio operations.<\/li>\n<li><strong>Use groups<\/strong>: map launch profiles to directory groups rather than individual users.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Cost best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Control instance sizes<\/strong> via launch profiles; require approval for the largest GPU tiers.<\/li>\n<li><strong>Idle shutdown<\/strong>: enforce session timeouts and stop idle instances where possible.<\/li>\n<li><strong>Avoid NAT surprises<\/strong>: prefer VPC endpoints for S3\/SSM; monitor NAT costs closely.<\/li>\n<li><strong>Storage lifecycle<\/strong>: move cold assets to cheaper S3 classes; prune caches.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Performance best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Locate users near the Region<\/strong>: latency matters for interactive DCC.<\/li>\n<li><strong>Choose storage intentionally<\/strong>:<\/li>\n<li>High IOPS pipelines need appropriate filesystem choices and tuning.<\/li>\n<li>Object storage is great for distribution\/archival; shared filesystem is often required for interactive workflows.<\/li>\n<li><strong>Test with real workloads<\/strong>: synthetic tests rarely match DCC cache patterns.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Reliability best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Use multi-AZ patterns where appropriate<\/strong> for critical shared services (depends on storage type and architecture).<\/li>\n<li><strong>Backup strategy<\/strong>: regular filesystem backups, versioned S3 buckets, tested restore procedures.<\/li>\n<li><strong>Document golden images<\/strong>: immutable image versions and rollback plans.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operations best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Patch management<\/strong>: use Systems Manager Patch Manager for workstation images and base instances where applicable.<\/li>\n<li><strong>Monitoring<\/strong>:<\/li>\n<li>Instance health, disk space, GPU utilization, session failures<\/li>\n<li>Storage throughput and latency<\/li>\n<li><strong>Runbooks<\/strong>: common fixes (license checkout failure, mount failure, image mismatch).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Governance\/tagging\/naming best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use consistent tags:<\/li>\n<li><code>Environment<\/code> (dev\/test\/prod)<\/li>\n<li><code>Project<\/code> \/ <code>Show<\/code><\/li>\n<li><code>CostCenter<\/code><\/li>\n<li><code>Owner<\/code><\/li>\n<li><code>DataClassification<\/code><\/li>\n<li>Naming conventions for:<\/li>\n<li>Studios: <code>studio-&lt;env&gt;-&lt;org&gt;-&lt;region&gt;<\/code><\/li>\n<li>Launch profiles: <code>&lt;dept&gt;-&lt;tier&gt;-&lt;os&gt;<\/code><\/li>\n<li>Images: <code>&lt;dcc-suite&gt;-&lt;version&gt;-&lt;date&gt;<\/code><\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">12. Security Considerations<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Identity and access model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Treat the studio as a high-value boundary: it can provide access to sensitive IP.<\/li>\n<li>Prefer centralized identity with MFA and strong password policies.<\/li>\n<li>Minimize AWS console access for artists; use Nimble Studio user access flow.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Encryption<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>At rest<\/strong>:<\/li>\n<li>Use SSE-KMS for S3 buckets holding assets.<\/li>\n<li>Use KMS-backed encryption for filesystems where supported.<\/li>\n<li>Encrypt EBS volumes for workstation instances and image builders.<\/li>\n<li><strong>In transit<\/strong>:<\/li>\n<li>Enforce TLS for data transfers to AWS APIs.<\/li>\n<li>Ensure remote display traffic is protected (verify the streaming protocol security model in docs).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Network exposure<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Avoid public inbound access to workstations.<\/li>\n<li>Place workstations in private subnets.<\/li>\n<li>Control egress:<\/li>\n<li>Use VPC endpoints for AWS services.<\/li>\n<li>Restrict internet via NAT + egress filtering if required.<\/li>\n<li>For on-prem connectivity:<\/li>\n<li>Use VPN\/Direct Connect with route controls and firewall rules.<\/li>\n<li>Segment license servers and pipeline services.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secrets handling<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Avoid baking secrets into workstation images.<\/li>\n<li>Use AWS Secrets Manager or SSM Parameter Store for secrets needed by pipeline tools (with strict IAM).<\/li>\n<li>Rotate credentials and audit usage.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Audit\/logging<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Enable CloudTrail for all Regions in the organization (if feasible).<\/li>\n<li>Consider S3 data event logging for high-value buckets (cost tradeoff).<\/li>\n<li>Centralize logs to a security account with restricted access.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Compliance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Media IP may have contractual requirements (MPA, TPN, ISO 27001-aligned controls, SOC evidence).<\/li>\n<li>Map controls to AWS artifacts:<\/li>\n<li>IAM access reviews<\/li>\n<li>Encryption evidence<\/li>\n<li>Logging and retention<\/li>\n<li>Incident response procedures<\/li>\n<li>Always validate compliance scope with your auditors and the AWS compliance documentation:<\/li>\n<li>https:\/\/aws.amazon.com\/compliance\/<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Common security mistakes<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Leaving unrestricted egress from workstations (data exfiltration risk).<\/li>\n<li>Overly broad S3 permissions (<code>s3:*<\/code> on <code>*<\/code>) in workstation roles.<\/li>\n<li>Sharing a single admin account among multiple admins.<\/li>\n<li>No tagging\/ownership: orphaned resources, unclear accountability.<\/li>\n<li>Skipping image hardening and patch baselines.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secure deployment recommendations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use a multi-account strategy (shared services + production accounts) where maturity requires it.<\/li>\n<li>Implement guardrails:<\/li>\n<li>SCPs to limit risky services\/actions for workstation roles<\/li>\n<li>Config rules for encryption and public exposure<\/li>\n<li>Conduct a threat model:<\/li>\n<li>Insider risk (authorized user exfiltration)<\/li>\n<li>Compromised endpoint credentials<\/li>\n<li>Misconfigured storage permissions<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">13. Limitations and Gotchas<\/h2>\n\n\n\n<blockquote>\n<p>These are common constraints observed in cloud workstation\/studio deployments. Verify Nimble Studio-specific limits and behaviors in the official docs.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Known limitations \/ common constraints<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Region availability<\/strong>: not every AWS Region supports Nimble Studio.<\/li>\n<li><strong>GPU capacity<\/strong>: GPU instance families can have limited availability; plan for quotas and capacity constraints.<\/li>\n<li><strong>Latency sensitivity<\/strong>: interactive DCC performance depends strongly on latency and packet loss.<\/li>\n<li><strong>Software licensing<\/strong>: many DCC vendors have strict cloud licensing rules; ensure compliance before production use.<\/li>\n<li><strong>Storage performance tuning<\/strong>: shared storage configuration is often the difference between success and failure.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quotas<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>EC2 GPU instance quotas are frequently the first blocker.<\/li>\n<li>Directory services may have scaling constraints.<\/li>\n<li>Filesystem throughput and connection limits can apply.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Regional constraints<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Even if Nimble Studio is available, specific GPU instance types may not be available in that Region\/AZ.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Pricing surprises<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>NAT Gateway charges can become significant if many workstations download updates or assets through NAT.<\/li>\n<li>Always-on directory services and filesystems accrue cost even when idle.<\/li>\n<li>Data transfer out can spike during client deliveries or outsourcing.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Compatibility issues<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Some DCC tools require specific GPU drivers; image standardization must include driver lifecycle management.<\/li>\n<li>Plugins may require node-locked licenses incompatible with ephemeral instances.<\/li>\n<li>SMB\/NFS semantics can impact pipelines; test file locking and pathing.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operational gotchas<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Image drift: artists installing ad-hoc tools inside sessions leads to \u201cit works on my machine\u201d incidents.<\/li>\n<li>Patching: failing to patch base images creates security exposure.<\/li>\n<li>Artifact sprawl: caches and temp files explode storage usage if not managed.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Migration challenges<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Moving a pipeline from on-prem to cloud is often more about:<\/li>\n<li>Identity and access patterns<\/li>\n<li>Storage path conventions<\/li>\n<li>License server reachability<\/li>\n<li>Data gravity and transfer windows\nthan about raw compute.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Vendor-specific nuances<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>DCC licensing, color pipeline requirements, and review workflows can impose non-obvious constraints.<\/li>\n<li>Always validate with vendor documentation and your legal\/procurement teams.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">14. Comparison with Alternatives<\/h2>\n\n\n\n<p>Amazon Nimble Studio is part of a broader solution space: VDI, app streaming, self-managed remote workstations, and other clouds\u2019 virtual desktop offerings.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Comparison table<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Option<\/th>\n<th>Best For<\/th>\n<th>Strengths<\/th>\n<th>Weaknesses<\/th>\n<th>When to Choose<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>Amazon Nimble Studio<\/strong><\/td>\n<td>Cloud creative studios (Media pipelines)<\/td>\n<td>Studio-centric abstraction, integrates identity\/network\/storage\/workstations, designed for creative workflows<\/td>\n<td>More moving parts than simple desktops; Region\/instance constraints; underlying AWS resources still need ops<\/td>\n<td>You need a managed \u201cstudio\u201d layer for creative teams and want AWS-native building blocks<\/td>\n<\/tr>\n<tr>\n<td><strong>Amazon WorkSpaces<\/strong><\/td>\n<td>Persistent managed desktops (general purpose)<\/td>\n<td>Simpler desktop provisioning; managed VDI experience<\/td>\n<td>May not fit high-end GPU DCC needs depending on requirements; less \u201cstudio pipeline\u201d oriented<\/td>\n<td>You want managed desktops with less pipeline complexity<\/td>\n<\/tr>\n<tr>\n<td><strong>Amazon AppStream 2.0<\/strong><\/td>\n<td>App streaming (single apps)<\/td>\n<td>Stream apps without full desktops; can simplify endpoint needs<\/td>\n<td>Not the same as full workstation workflows; complex DCC pipelines may need full desktop + storage integration<\/td>\n<td>You can deliver required tools as streamed apps and avoid full desktops<\/td>\n<\/tr>\n<tr>\n<td><strong>EC2 + NICE DCV (self-managed)<\/strong><\/td>\n<td>Maximum control and customization<\/td>\n<td>Full control over images, networking, protocol tuning<\/td>\n<td>Higher operational burden; you must build user portal, access control, lifecycle mgmt<\/td>\n<td>You have platform engineering maturity and need deep customization<\/td>\n<\/tr>\n<tr>\n<td><strong>Third-party VDI (e.g., VMware Horizon, Citrix)<\/strong><\/td>\n<td>Enterprise VDI standardization<\/td>\n<td>Mature VDI features, policy control, ecosystem<\/td>\n<td>Licensing cost and complexity; may still require AWS integration work<\/td>\n<td>Your organization already standardizes on a VDI platform<\/td>\n<\/tr>\n<tr>\n<td><strong>Azure Virtual Desktop<\/strong><\/td>\n<td>Microsoft ecosystem VDI<\/td>\n<td>Strong Windows integration, familiar VDI constructs<\/td>\n<td>Different cloud; migration\/integration work<\/td>\n<td>You\u2019re primarily on Azure or require AVD-specific capabilities<\/td>\n<\/tr>\n<tr>\n<td><strong>Google Cloud workstations\/VDI patterns<\/strong><\/td>\n<td>GCP-based desktop strategies<\/td>\n<td>GCP-native approaches and GPUs<\/td>\n<td>Different cloud; feature fit varies<\/td>\n<td>You\u2019re on GCP and want consistent platform alignment<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">15. Real-World Example<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Enterprise example: global VFX studio with strict security and outsourcing<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: A global VFX company needs to onboard remote artists and external vendors while keeping assets protected and auditable.<\/li>\n<li><strong>Proposed architecture<\/strong>:<\/li>\n<li>Amazon Nimble Studio in a supported Region close to the primary team<\/li>\n<li>Private subnets for workstations<\/li>\n<li>Shared filesystem for active projects + S3 for long-term storage<\/li>\n<li>VPC endpoints to S3\/SSM; restricted NAT egress<\/li>\n<li>VPN\/Direct Connect to on-prem license servers and asset management<\/li>\n<li>CloudTrail centralized to a security account; CloudWatch alarms for anomalous behavior<\/li>\n<li><strong>Why this service was chosen<\/strong>:<\/li>\n<li>The studio control plane reduces time to deploy compared to building a custom workstation portal.<\/li>\n<li>Launch profiles map cleanly to role-based access (anim, comp, lighting).<\/li>\n<li><strong>Expected outcomes<\/strong>:<\/li>\n<li>Faster onboarding for remote teams<\/li>\n<li>Reduced endpoint data exposure<\/li>\n<li>Better auditability and centralized controls<\/li>\n<li>Elastic capacity during peak shots<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Startup\/small-team example: indie game cinematic team<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: A 6-person team needs occasional high-end GPU workstations for cinematic production without buying hardware.<\/li>\n<li><strong>Proposed architecture<\/strong>:<\/li>\n<li>One Nimble Studio studio<\/li>\n<li>A small set of launch profiles (standard GPU, heavy GPU)<\/li>\n<li>S3 for asset exchange and archiving; minimal always-on infrastructure<\/li>\n<li>Aggressive shutdown\/idle policies and budgets\/alerts<\/li>\n<li><strong>Why this service was chosen<\/strong>:<\/li>\n<li>Faster and safer than building EC2 + remote access from scratch.<\/li>\n<li>Lets artists work from modest laptops while compute runs in AWS.<\/li>\n<li><strong>Expected outcomes<\/strong>:<\/li>\n<li>Lower upfront cost<\/li>\n<li>Better ability to scale for short deadlines<\/li>\n<li>Centralized and repeatable workstation environments<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">16. FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1) Is Amazon Nimble Studio a VDI service?<\/h3>\n\n\n\n<p>It provides a managed \u201cstudio\u201d experience that includes remote workstation streaming, but it\u2019s best thought of as a <strong>cloud studio orchestration service<\/strong> that uses AWS infrastructure (like EC2 and shared storage) to deliver workstation sessions.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2) Do artists need AWS console access?<\/h3>\n\n\n\n<p>Typically, no. A key goal is to let artists access workstations through the studio access flow while admins manage AWS resources and policies.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3) Is Amazon Nimble Studio available in all AWS Regions?<\/h3>\n\n\n\n<p>No. You must select a supported Region. Verify in the AWS console and official docs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4) What is the biggest cost driver?<\/h3>\n\n\n\n<p>Usually <strong>GPU EC2 instance hours<\/strong>, followed by always-on components like shared storage, directory services, and NAT gateways (depending on architecture).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">5) Can I use my existing VPC?<\/h3>\n\n\n\n<p>Often yes, but the best approach depends on your network baseline and the Nimble Studio setup flow. For production, using an existing, governed VPC is common.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6) Can I connect to on-prem license servers?<\/h3>\n\n\n\n<p>Commonly, yes\u2014via VPN or Direct Connect\u2014if your network routing and security rules allow it.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">7) Do I need Amazon FSx?<\/h3>\n\n\n\n<p>Not always, but most interactive creative workflows need shared POSIX\/SMB semantics and high performance. Many studios use FSx and\/or S3 together. Choose based on workflow requirements.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">8) How do I prevent data exfiltration from workstations?<\/h3>\n\n\n\n<p>Use private subnets, restrict egress, limit clipboard\/drive redirection features as supported by your remote display stack, enforce least-privilege storage access, and monitor\/analyze logs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">9) Can I use Spot Instances for artist workstations?<\/h3>\n\n\n\n<p>Spot can reduce cost, but interruptions can disrupt interactive sessions. It\u2019s more commonly used for non-interactive compute. Use carefully and test.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">10) How do I manage workstation images?<\/h3>\n\n\n\n<p>Maintain a \u201cgolden image\u201d pipeline: build, test, version, and roll out images on a schedule with rollback capability. Validate Nimble Studio\u2019s recommended image management approach in the docs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">11) What about patching and antivirus\/EDR?<\/h3>\n\n\n\n<p>Treat workstation images like enterprise endpoints: patch regularly, apply security baselines, and integrate with your organization\u2019s endpoint security tooling where feasible.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">12) Can I restrict which instance types users can launch?<\/h3>\n\n\n\n<p>Yes\u2014this is a core control-plane benefit. Use launch profiles to constrain sizes and reduce unexpected spend.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">13) How do I monitor usage and costs by project?<\/h3>\n\n\n\n<p>Use tagging, AWS Cost Allocation Tags, Cost Explorer, and Budgets. Ensure studio-created resources inherit tags where possible.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">14) Is Nimble Studio suitable for non-media workloads?<\/h3>\n\n\n\n<p>It can be used for other remote workstation use cases, but it\u2019s optimized for <strong>Media and creative studio workflows<\/strong>. For general desktops, consider WorkSpaces.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">15) How do I start learning it safely?<\/h3>\n\n\n\n<p>Start with a small pilot: one studio, one profile, one or two users, minimal always-on components, strict cleanup, and measure performance with real project data.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">17. Top Online Resources to Learn Amazon Nimble Studio<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Resource Type<\/th>\n<th>Name<\/th>\n<th>Why It Is Useful<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Official product page<\/td>\n<td>https:\/\/aws.amazon.com\/nimble-studio\/<\/td>\n<td>High-level overview, current announcements, links to docs<\/td>\n<\/tr>\n<tr>\n<td>Official documentation<\/td>\n<td>https:\/\/docs.aws.amazon.com\/nimble-studio\/<\/td>\n<td>Canonical setup\/configuration guidance and concepts<\/td>\n<\/tr>\n<tr>\n<td>What is \/ User guide entry<\/td>\n<td>https:\/\/docs.aws.amazon.com\/nimble-studio\/latest\/userguide\/what-is-nimble-studio.html<\/td>\n<td>Fast orientation to terminology and components<\/td>\n<\/tr>\n<tr>\n<td>Pricing page<\/td>\n<td>https:\/\/aws.amazon.com\/nimble-studio\/pricing\/<\/td>\n<td>Official pricing model and billing dimensions<\/td>\n<\/tr>\n<tr>\n<td>AWS Pricing Calculator<\/td>\n<td>https:\/\/calculator.aws\/#\/<\/td>\n<td>Build scenario-based estimates (workstations, storage, NAT, etc.)<\/td>\n<\/tr>\n<tr>\n<td>Service Quotas<\/td>\n<td>https:\/\/console.aws.amazon.com\/servicequotas\/<\/td>\n<td>Identify and request quota increases (GPU instances, etc.)<\/td>\n<\/tr>\n<tr>\n<td>EC2 instance limits<\/td>\n<td>https:\/\/docs.aws.amazon.com\/AWSEC2\/latest\/UserGuide\/ec2-resource-limits.html<\/td>\n<td>GPU quota and capacity planning essentials<\/td>\n<\/tr>\n<tr>\n<td>CloudTrail docs<\/td>\n<td>https:\/\/docs.aws.amazon.com\/awscloudtrail\/latest\/userguide\/cloudtrail-user-guide.html<\/td>\n<td>Auditing and governance patterns<\/td>\n<\/tr>\n<tr>\n<td>NICE DCV overview<\/td>\n<td>https:\/\/aws.amazon.com\/hpc\/dcv\/<\/td>\n<td>Background on remote display tech commonly used for AWS workstations<\/td>\n<\/tr>\n<tr>\n<td>AWS Media &amp; Entertainment<\/td>\n<td>https:\/\/aws.amazon.com\/media\/<\/td>\n<td>Broader AWS Media context and related services<\/td>\n<\/tr>\n<tr>\n<td>AWS re:Post (community)<\/td>\n<td>https:\/\/repost.aws\/<\/td>\n<td>Practical Q&amp;A and troubleshooting patterns (validate against docs)<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">18. Training and Certification Providers<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Institute<\/th>\n<th>Suitable Audience<\/th>\n<th>Likely Learning Focus<\/th>\n<th>Mode<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>Cloud\/DevOps engineers, architects<\/td>\n<td>AWS fundamentals, DevOps, operations practices<\/td>\n<td>check website<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>ScmGalaxy.com<\/td>\n<td>Engineers, students<\/td>\n<td>DevOps, SCM, CI\/CD, cloud basics<\/td>\n<td>check website<\/td>\n<td>https:\/\/www.scmgalaxy.com\/<\/td>\n<\/tr>\n<tr>\n<td>CLoudOpsNow.in<\/td>\n<td>Cloud operations teams<\/td>\n<td>CloudOps, monitoring, reliability, operations<\/td>\n<td>check website<\/td>\n<td>https:\/\/www.cloudopsnow.in\/<\/td>\n<\/tr>\n<tr>\n<td>SreSchool.com<\/td>\n<td>SREs, platform engineers<\/td>\n<td>SRE principles, reliability engineering<\/td>\n<td>check website<\/td>\n<td>https:\/\/www.sreschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>AiOpsSchool.com<\/td>\n<td>Ops\/engineering teams<\/td>\n<td>AIOps concepts, automation, observability<\/td>\n<td>check website<\/td>\n<td>https:\/\/www.aiopsschool.com\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">19. Top Trainers<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Platform\/Site<\/th>\n<th>Likely Specialization<\/th>\n<th>Suitable Audience<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>RajeshKumar.xyz<\/td>\n<td>DevOps\/cloud training content (verify offerings)<\/td>\n<td>Beginners to intermediate engineers<\/td>\n<td>https:\/\/rajeshkumar.xyz\/<\/td>\n<\/tr>\n<tr>\n<td>devopstrainer.in<\/td>\n<td>DevOps training (verify course catalog)<\/td>\n<td>Engineers and teams<\/td>\n<td>https:\/\/www.devopstrainer.in\/<\/td>\n<\/tr>\n<tr>\n<td>devopsfreelancer.com<\/td>\n<td>Freelance DevOps help\/training (verify services)<\/td>\n<td>Teams needing hands-on guidance<\/td>\n<td>https:\/\/www.devopsfreelancer.com\/<\/td>\n<\/tr>\n<tr>\n<td>devopssupport.in<\/td>\n<td>DevOps support\/training (verify services)<\/td>\n<td>Ops teams, project support<\/td>\n<td>https:\/\/www.devopssupport.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">20. Top Consulting Companies<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Company<\/th>\n<th>Likely Service Area<\/th>\n<th>Where They May Help<\/th>\n<th>Consulting Use Case Examples<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>cotocus.com<\/td>\n<td>Cloud\/DevOps consulting (verify offerings)<\/td>\n<td>Architecture, implementation, operations<\/td>\n<td>Studio landing zone setup, VPC design, cost optimization<\/td>\n<td>https:\/\/cotocus.com\/<\/td>\n<\/tr>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>DevOps\/cloud consulting and training<\/td>\n<td>DevOps practices, platform enablement<\/td>\n<td>CI\/CD for workstation images, monitoring and governance baselines<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>DEVOPSCONSULTING.IN<\/td>\n<td>DevOps consulting (verify offerings)<\/td>\n<td>Cloud migration, automation, operations<\/td>\n<td>Identity integration review, IaC pipelines, logging\/audit readiness<\/td>\n<td>https:\/\/www.devopsconsulting.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">21. Career and Learning Roadmap<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn before Amazon Nimble Studio<\/h3>\n\n\n\n<p>To be effective with Nimble Studio, learn these AWS fundamentals first:\n&#8211; <strong>AWS IAM<\/strong>: roles, policies, least privilege\n&#8211; <strong>Amazon VPC<\/strong>: subnets, routing, security groups, NAT, endpoints\n&#8211; <strong>Amazon EC2<\/strong>: instance families (GPU), AMIs, EBS, autoscaling concepts\n&#8211; <strong>Amazon S3<\/strong>: buckets, policies, encryption, lifecycle\n&#8211; <strong>CloudWatch and CloudTrail<\/strong>: monitoring and auditing basics\n&#8211; Basic Windows\/Linux administration (depending on workstation OS)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn after Amazon Nimble Studio<\/h3>\n\n\n\n<p>For production readiness and scale:\n&#8211; <strong>AWS Organizations<\/strong>: multi-account governance\n&#8211; <strong>AWS KMS<\/strong>: key management, encryption patterns\n&#8211; <strong>AWS Systems Manager<\/strong>: patching, automation, inventory\n&#8211; <strong>Cost management<\/strong>: budgets, cost allocation tags, CUR (Cost &amp; Usage Report)\n&#8211; Media pipeline services\/tools you use (render management, asset management, review systems)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Job roles that use it<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Media pipeline engineer \/ pipeline TD<\/li>\n<li>Cloud solutions architect (Media)<\/li>\n<li>Platform engineer (creative tooling)<\/li>\n<li>DevOps\/SRE supporting creative infrastructure<\/li>\n<li>Security engineer for Media IP environments<\/li>\n<li>Technical producer \/ studio technology manager (with technical depth)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Certification path (AWS)<\/h3>\n\n\n\n<p>There is no Nimble Studio-specific certification commonly listed as a standalone. Typical AWS certifications relevant to operating Nimble Studio environments include:\n&#8211; AWS Certified Solutions Architect \u2013 Associate\/Professional\n&#8211; AWS Certified SysOps Administrator \u2013 Associate\n&#8211; AWS Certified Security \u2013 Specialty<\/p>\n\n\n\n<p>Always verify current AWS certification offerings:\n&#8211; https:\/\/aws.amazon.com\/certification\/<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Project ideas for practice<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Build a \u201ctwo-tier\u201d studio: standard vs heavy launch profiles with budgets and alerts.<\/li>\n<li>Implement a secure egress design using VPC endpoints + restricted NAT.<\/li>\n<li>Create an image versioning pipeline with rollback and patch windows.<\/li>\n<li>Benchmark storage throughput and latency for a representative asset workload.<\/li>\n<li>Build a cost report dashboard grouped by <code>Project<\/code> and <code>LaunchProfile<\/code>.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">22. Glossary<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Studio (Nimble Studio)<\/strong>: A logical environment representing your cloud studio configuration\u2014identity, profiles, storage, and access patterns.<\/li>\n<li><strong>Launch profile<\/strong>: A configuration that controls who can launch what workstation sessions and with what permissions\/settings.<\/li>\n<li><strong>Streaming session \/ Workstation session<\/strong>: A remote desktop session delivered to the user, backed by cloud compute (often EC2).<\/li>\n<li><strong>DCC (Digital Content Creation)<\/strong>: Creative software and workflows for 3D modeling, animation, VFX, and design.<\/li>\n<li><strong>VPC (Virtual Private Cloud)<\/strong>: Your isolated AWS network environment.<\/li>\n<li><strong>Private subnet<\/strong>: A subnet without direct inbound internet routing; typically used for secure workloads.<\/li>\n<li><strong>NAT Gateway<\/strong>: Enables outbound internet access for private subnets; can be a significant cost driver.<\/li>\n<li><strong>VPC endpoint<\/strong>: Private connectivity to AWS services without routing through the public internet (can reduce NAT usage).<\/li>\n<li><strong>FSx<\/strong>: AWS managed file system services (used for shared storage patterns).<\/li>\n<li><strong>S3<\/strong>: Object storage often used for asset storage, transfer, and archival.<\/li>\n<li><strong>KMS<\/strong>: AWS Key Management Service for encryption key control.<\/li>\n<li><strong>CloudTrail<\/strong>: Records AWS API activity for auditing.<\/li>\n<li><strong>CloudWatch<\/strong>: Metrics\/logs service for monitoring.<\/li>\n<li><strong>Least privilege<\/strong>: Security principle of granting only the permissions required to perform a task.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">23. Summary<\/h2>\n\n\n\n<p>Amazon Nimble Studio (AWS) is a managed service in the <strong>Media<\/strong> category that helps you build and operate a cloud-based creative studio: centralized access control, launch profiles, and on-demand streaming workstations integrated with AWS networking and storage.<\/p>\n\n\n\n<p>It matters because creative pipelines demand secure access to high-performance compute and shared assets, and assembling those pieces manually can take significant engineering effort. Nimble Studio provides a studio-oriented control plane while letting you use standard AWS building blocks like EC2, VPC, FSx\/S3, IAM, CloudWatch, and CloudTrail.<\/p>\n\n\n\n<p>Cost and security are tightly linked: the biggest cost drivers are typically GPU compute hours, always-on storage\/directory services, and NAT\/data transfer. The biggest security wins come from private networking, controlled egress, least-privilege storage access, strong identity, and robust auditing.<\/p>\n\n\n\n<p>Use Amazon Nimble Studio when you want a structured, AWS-native way to deliver cloud workstations for creative teams with centralized governance. As a next step, build a small pilot in a supported Region, measure performance with real workloads, and use the AWS Pricing Calculator to model your steady-state production costs before scaling.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Media<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20,34],"tags":[],"class_list":["post-285","post","type-post","status-publish","format-standard","hentry","category-aws","category-media"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/285","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/comments?post=285"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/285\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/media?parent=285"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/categories?post=285"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/tags?post=285"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}