Qumulo Studio Q on the AWS Cloud

Quick Start Reference Deployment

QS

May 2021
Dack Busch, Qumulo
Troy Ameigh and Dave May, AWS Quick Start team

Visit our GitHub repository for source files and to post feedback, report bugs, or submit feature ideas for this Quick Start.

This Quick Start was created by Qumulo in collaboration with Amazon Web Services (AWS). Quick Starts are automated reference deployments that use AWS CloudFormation templates to deploy key technologies on AWS, following AWS best practices.

Overview

This guide provides instructions for deploying the Studio Q Quick Start reference architecture in the AWS Cloud.

The Studio Q Quick Start is designed to help you quickly build a non-linear editing environment for your remote editorial creative teams. The remote environment consists of a Qumulo cluster and one or more editorial workstations all hosted on AWS.

Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on the Quick Start.

Qumulo Studio Q on AWS

Qumulo is a high-performance, multi-protocol file data platform for managing billions of files in a single namespace on AWS. Supporting petabyte-scale data, Qumulo’s file data platform is the foundation that makes all files available to all editors for collaborative editorial workflows.

This Quick Start builds a Qumulo cluster and one or more editorial workstations all hosted on AWS with options for 1-TB and 12-TB usable capacity. Workstations are built on the AWS G4dn family of Amazon Elastic Compute Cloud (Amazon EC2) instances with NVIDIA T4 graphics processing units (GPUs) and a Teradici PC over IP (PCoIP) agent on the workstation. You can optionally add more workstations as a post-deployment step.

With Qumulo’s Studio Q solution, editors have the same editorial experience as if they are working with local resources.

If you prefer larger editorial environments, contact Qumulo.

AWS costs

You are responsible for the cost of the AWS services and any third-party licenses used while running this Quick Start. There is no additional cost for using the Quick Start.

The AWS CloudFormation templates for Quick Starts include configuration parameters that you can customize. Some of the settings, such as the instance type, affect the cost of deployment. For cost estimates, see the pricing pages for each AWS service you use. Prices are subject to change.

After you deploy the Quick Start, create AWS Cost and Usage Reports to deliver billing metrics to an Amazon Simple Storage Service (Amazon S3) bucket in your account. These reports provide cost estimates based on usage throughout each month and aggregate the data at the end of the month. For more information, see What are AWS Cost and Usage Reports?

Software licenses

This Quick Start requires two subscriptions: one to the Amazon Machine Image (AMI) for Qumulo (either the 1 or 12-TB usable capacity option) and the other for AMI for Teradici, both of which are available from AWS Marketplace. Additional pricing, terms, and conditions may apply. For instructions, see Deployment steps section.

Architecture

Deploying this Quick Start for a new virtual private cloud (VPC) builds the following Studio Q environment in the AWS Cloud.

Architecture
Figure 1. Quick Start architecture for Studio Q on AWS

As shown in Figure 1, the Quick Start sets up the following:

  • A VPC configured with public and private subnets, according to AWS best practices, to provide you with your own virtual network on AWS.*

  • In the public subnet:

    • A managed network address translation (NAT) gateway to allow outbound. internet access for resources in the private subnet.*

    • One or more EC2 g4dn instances running Windows Server 2019.

      • Teradici PCoIP is installed for streaming the editorial workspace to remote editors.

      • Windows is configured in an optimized fashion for Adobe Premiere Pro with a pop-up per boot cycle for Adobe Creative Cloud login.

  • In the private subnet:

    • A cluster of four Qumulo EC2 instances providing 1TB or 12TB of usable capacity.

    • Multiple Amazon Elastic Block Store (EBS) volumes connected to the Qumulo cluster.

      • 1TB usable capacity: 24x 100GiB EBS gp2 volumes.

      • 12TB usable capacity: 20x 100GiB EBS gp2 volumes and 40x 500GiB EBS st1 volumes.

    • Two Lambda functions to monitor and report on the Qumulo environment.

      • One Lambda function sends metrics for the Qumulo cluster to CloudWatch.

      • The other Lambda function monitors the health of EBS volumes and autmatically replaces any unhealthy volumes.

    • An EC2 m5.large instance acting as an Active Directory domain controller and local DNS server.

      • All workstations and the Qumulo cluster are joined to the AD domain automatically.

      • The AD server also provides all DNS services local to the VPC forwarding public requests to Route53.

    • A temporary provisioner instance that performs the following:

      • Creates Qumulo cluster users, roles, IP failover, and an SMB share.

      • Joins the cluster to the AD domain.

      • Tags all EBS volumes with the CloudFormation stack name and modifies the KMS Customer Managed Key (CMK) policy if a CMK is specified in the template.

*The template that deploys the Quick Start into an existing VPC skips the components marked by asterisks and prompts you for your existing VPC configuration.

Planning the deployment

Specialized knowledge

This deployment requires a moderate level of familiarity with AWS services. If you’re new to AWS, see Getting Started Resource Center and AWS Training and Certification. These sites provide materials for learning how to design, deploy, and operate your infrastructure and applications on the AWS Cloud.

This Quick Start assumes a basic knowledge of the Windows environment and no previous knowledge of Qumulo or Teradici.

To customize the configuration of the Qumulo cluster, see Qumulo Care.

To customize the configuration for Teradici PCoIP, see the Teradici Knowledge Center.

AWS account

If you don’t already have an AWS account, create one at https://aws.amazon.com by following the on-screen instructions. Part of the sign-up process involves receiving a phone call and entering a PIN using the phone keypad.

Your AWS account is automatically signed up for all AWS services. You are charged only for the services you use.

Technical requirements

Before you launch the Quick Start, review the following information and ensure that your account is properly configured. Otherwise, deployment might fail.

Resource quotas

If necessary, request service quota increases for the following resources. You might need to request increases if your existing deployment currently uses these resources and if this Quick Start deployment could result in exceeding the default quotas. The Service Quotas console displays your usage and quotas for some aspects of some services. For more information, see What is Service Quotas? and AWS service quotas.

Resource This deployment uses

VPCs

1

Elastic IP addresses

1 for NAT Gateway, plus 1 for each workstation

Security groups

6

AWS Identity and Access Management (IAM) roles

5, plus 1 for each workstation

m5.2xlarge, m5.4xlarge, m5.8xlarge, or c5n.9xlarge instances

4

m5.large instances

1

t3.large instances

1

g4dn.2xlarge, g4dn.4xlarge, g4dn.8xlarge, or g4dn.16xlarge instances

1 for each workstation

Lambda functions

2

Supported AWS Regions

For any Quick Start to work in a Region other than its default Region, all the services it deploys must be supported in that Region. You can launch a Quick Start in any Region and see if it works. If you get an error such as “Unrecognized resource type,” the Quick Start is not supported in that Region.

For an up-to-date list of AWS Regions and the AWS services they support, see AWS Regional Services.

Certain Regions are available on an opt-in basis. For more information, see Managing AWS Regions.

IAM permissions

Before launching the Quick Start, you must sign in to the AWS Management Console with IAM permissions for the resources that the templates deploy. The AdministratorAccess managed policy within IAM provides sufficient permissions, although your organization may choose to use a custom policy with more restrictions. For more information, see AWS managed policies for job functions.

Deployment options

This Quick Start provides two deployment options:

  • Deploy Studio Q into a new VPC. This option builds a new AWS environment consisting of the VPC, subnets, NAT gateway, security groups, and other infrastructure components. It then deploys Studio Q into this new VPC.

  • Deploy Studio Q into an existing VPC. This option provisions Studio Q in your existing AWS infrastructure.

The Quick Start provides separate templates for these options. It also lets you configure Classless Inter-Domain Routing (CIDR) blocks, instance types, and Studio Q settings, as discussed later in this guide.

When deploying into an existing VPC, this Quick Start deploys the Active Directory server as the domain controller, and all subsequent infrastructure depends on domain controller’s local DNS. Plan accordingly.

Deployment steps

Sign in to your AWS account

  1. Sign in to your AWS account at https://aws.amazon.com with an AWS Identity and Access Management (IAM) user role that has the necessary permissions. For details, see Planning the deployment earlier in this guide.

  2. Make sure that your AWS account is configured correctly, as discussed in the Technical requirements section.

Subscribe to the Marketplace AMIs

This Quick Start requires a subscription to the Amazon Machine Image (AMI) for Studio Q and Teradici in AWS Marketplace.

  1. Sign in to your AWS account.

  2. Open one of the following two Qumulo pages in the AWS Marketplace, and choose Continue to Subscribe. Regardless of which offer you choose, you are only charged for what is deployed.

  3. Review the terms and conditions for software usage, and then choose Accept Terms.
    A confirmation page loads, and an email confirmation is sent to the account owner. For detailed subscription instructions, see the AWS Marketplace documentation. When the subscription process is complete, continue to step 4. Do not provision the software from AWS Marketplace, as the Quick Start deploys the AMI for you.

  4. Still in the AWS Marketplace, open the Teradici AMI page, and choose Continue to Subscribe.

  5. Review the terms and conditions for software usage, and then choose Accept Terms.
    A confirmation page loads, and an email confirmation is sent to the account owner. For detailed subscription instructions, see the AWS Marketplace documentation. When the subscription process is complete, exit out of AWS Marketplace without further action. Do not provision the software from AWS Marketplace, as the Quick Start deploys the AMI for you.

Launch the Quick Start

If you’re deploying Studio Q into an existing VPC, make sure that your VPC has two private subnets in different Availability Zones for the workload instances and that the subnets aren’t shared. This Quick Start doesn’t support shared subnets. These subnets require NAT gateways in their route tables to allow the instances to download packages and software without exposing them to the internet. Also make sure that the domain name option in the DHCP options is configured as explained in DHCP options sets. You provide your VPC settings when you launch the Quick Start.

Each deployment takes about 40 minutes to complete.

  1. Sign in to your AWS account, and choose one of the following options to launch the AWS CloudFormation template. For help with choosing an option, see Deployment options, earlier in this guide.

Deploy Studio Q into a new VPC on AWS

View template

Deploy Studio Q into an existing VPC on AWS

View template

  1. Check the AWS Region that’s displayed in the upper-right corner of the navigation bar, and change it if necessary. This Region is where the network infrastructure for Studio Q is built. The template is launched in the us-east-1 Region by default. For other choices, see Supported Regions earlier in this guide.

  1. On the Create stack page, keep the default setting for the template URL, and then choose Next.

  2. On the Specify stack details page, change the stack name if needed. Review the parameters for the template. Provide values for the parameters that require input. For all other parameters, review the default settings and customize them as necessary. For details on each parameter, see the Parameter reference section of this guide. When you finish reviewing and customizing the parameters, choose Next.

  3. On the Configure stack options page, you can specify tags (key-value pairs) for resources in your stack and set advanced options. When you finish, choose Next.

  4. On the Review page, review and confirm the template settings. Under Capabilities, select the two check boxes to acknowledge that the template creates IAM resources and might require the ability to automatically expand macros.

  5. Choose Create stack to deploy the stack.

  6. Monitor the status of the stack. When the status is CREATE_COMPLETE, the Studio Q deployment is ready.

  7. To view the created resources, see the values displayed in the Outputs tab for the stack.

Test the deployment

  1. If you haven’t already installed the Teradici client, check the Outputs section of the main stack and navigate to the URL beside the TeradiciPCoIPClientURL key.

Architecture
Figure 2. Teradici PCoIP client download URL
  1. Download and install the Teradici thin client for your local Windows/Mac/Linux machine.

  2. Check the Outputs section of the main stack and copy the value for the WorkstationPublicIP1 key.

Architecture
Figure 3. Workstation host address
  1. Launch the Teradici client and paste the WorkstationPublicIP1 value into the hostname field. Optionally provide a name in the Connection Name field to create a shortcut when launching the Teradici client.

Architecture
Figure 4. Teradici PCoIP client
  1. Choose Next. If prompted with a certificate warning, select Connect Insecurely. To replace the self-signed certificate, see Creating, Installing, and Managing Certificates on the Teradici website.

Architecture
Figure 5. Certificate warning
  1. Check to see if the Teradici client recognizes the Active Directory domain name entered in the template. Workstations take about 10 minutes to boot and configure after the template completes. If the domain name is not found, close the Teradici window and repeat steps 3 and 4.

Architecture
Figure 6. Teradici login with valid Active Directory domain
  1. Enter the Active Directory accounts base user name and the number of the workstation that you want to connect to. Use the default password for Active Directory accounts that you entered when launching the Quick Start, and choose LOGIN.

Architecture
Figure 7. Teradici login user name and default password
  1. If you entered one of the temporary user credentials, a Windows login screen will appear. Use the Connection menu to choose CTRL + ALT + DELETE. Note: If using a Mac, the Connection menu is in the menu bar at the top of the screen.

Architecture
Figure 8. Workstation welcome screen
  1. If logging in for the first time, you are prompted to enter your credentials again and change your password.

Architecture
Figure 9. Password reset warning
  1. After logging in to the workstation, the Studio Q desktop appears.

Architecture
Figure 10. Studio Q Desktop
  1. Open File Explorer and verify that the Q drive has been mapped. Notice the local NVME drive has been initialized and formatted as well. When configuring Adobe Premiere Pro set the cache to use the local NVME drive.

Architecture
Figure 11. Q: Drive mapped to Qumulo
  1. Open the Windows launch view and choose Server Manager.

Architecture
Figure 12. Windows Launch View
  1. Choose Local Server, and verify that Windows Defender Antivirus has a Windows Real-time Protection: Off status.

Architecture
Figure 13. Windows Server Manager
Architecture
Figure 14. Windows Local Server

Post-deployment steps

Set the default browser

  1. Go to the upper-right corner of the Chrome browser and choose Settings > Default browser, and choose Chrome as the default browser. Close the Settings window.

Architecture
Figure 15. Chrome settings
Architecture
Figure 16. Chrome default browser
Architecture
Figure 17. Make Chrome default
Architecture
Figure 18. Chrome select as default browser

Log in to the Qumulo dashboard

  1. Open the Qumulo-UI desktop icon and accept the self-signed certificate by choosing Advanced and then proceeding to the site. If you want to replace the self-signed certificate, see Install a Signed SSL Certificate from Qumulo.

Architecture
Figure 19. Qumulo self-signed certificate
  1. Enter your Active Directory domain-name\user-name and your password. You will be authenticated with your Active Directory credentials and given read-only privileges to view all settings and activity on the cluster.

Architecture
Figure 20. Qumulo UI login
  1. The Qumulo dashboard displays either 1.3 or 12.6-TB usable capacity, depending on your configuration when the template is launched.

Architecture
Figure 21. Qumulo dashboard
  1. Choose Cluster. Four nodes are displayed numbered 1 through 4. These are each of your EC2 instances.

Architecture
Figure 22. Qumulo Cluster Overview
  1. In the same window, choose any one of the four nodes. The drive details should show all drives as healthy. The drives are the EBS volumes connected to the specific node (EC2 instance) that you selected.

Architecture
Figure 23. Qumulo cluster node 1 details
  1. Choose Cluster > Network Configuration. The Search Domains shows your fully qualified domain name (FQDN). Each of the four nodes shows a persistent IP address (EC2 primary IP address) and three floating IP addresses (EC2 secondary IP addresses) for IP failover.

Architecture
Figure 24. Qumulo network configuration
  1. Choose Cluster > Active Directory. At the top of the window, you can confirm that the cluster with the name you gave it has joined the FQDN of your domain.

Architecture
Figure 25. Qumulo Active Directory
  1. Choose Cluster > SMB Shares. Note how the adobe-projects share has been created. Use this share for all video content and subsequent editing in Adobe Premiere Pro.

Architecture
Figure 26. Qumulo SMB shares
  1. Now, all of the Studio Q infrastructure is set up and confirmed to be properly configured. You can move content on to the Qumulo cluster using the S3 Browser link on the desktop or any other preferred S3 utility and drop the content in the Q drive. All workstations and users now have access to the Q drive. Also, if you create multiple workstations, you can log in to those workstations using the credentials created in this first Teradici session. Any user can log in to any workstation because they are authenticated with Active Directory. Twenty users are created by default (for example, studioqUser1, studioqUser2,…​studioqUser20). At first login, users must change their password.

Add another workstation

The initial deployment deploys 1 to 10 workstations. If you want to add another workstation, follow these steps:

  1. Launch the following template: Deploy additional Studio Q workstation. You can also (view the template).

  1. From the original, top-level stack, copy the WorkstationStackName key value.

Architecture
Figure 27. Stack outputs
  1. Paste the stack name in to the Add Workstation template, fill in the fields, and launch the template.

Architecture
Figure 28. Add Workstation template input
  1. When the stack completes, go to the top level for the new stack and choose Outputs to see the public IP address for the new workstation. The new workstation has the same configuration as the original workstations that were created.

Architecture
Figure 29. Add Workstation template outputs

Upgrade the Qumulo cluster

Qumulo releases software every two weeks in an agile development fashion. The upgrade process takes only a few minutes and should not impact service.

  1. Copy the temporary administrator password from the original stack’s top-level outputs.

Architecture
Figure 30. Add Workstation template outputs
  1. Log in to the Qumulo cluster as admin using the copied password.

Architecture
Figure 31. Admin Login
  1. In the Qumulo-UI, choose Support > Software Upgrade and then latest upgrade file. For more information about Qumulo upgrades, see Qumulo Core Upgrades via UI.

Architecture
Figure 32. Get the latest upgrade
  1. Copy the downloaded .qimg file to any SMB share on the cluster. This example uses the adobe-projects share.

Architecture
Figure 33. Qumulo upgrade file copied to adobe-projects
  1. Back in Qumulo-UI, choose Support > Software Upgrade and enter the path to the file. Then choose Upgrade and confirm to continue. The upgrade takes a few minutes.

Architecture
Figure 34. Qumulo upgrade file specified
  1. When the upgrade is completed, confirm that the new version is installed.

Architecture
Figure 35. Qumulo upgraded

Upgrade the sidecar Lambda functions

The final step in the upgrade is to update the Python code in the sidecar Lambda functions. This insures that CloudWatch metrics and EBS volume monitoring are in sync with the latest Qumulo Core software on the cluster.

  1. In the AWS Management Console, navigate to CloudFormation and select the original top-level stack for the deployment. Then select Update.

Architecture
Figure 36. Update original stack
  1. Keep the default Use current template.

Architecture
Figure 37. Use current template for the stack update
  1. The template that you originally filled out is displayed. Scroll to the Qumulo CloudWatch Metrics & Monitoring Configuration section and change the Qumulo Sidecar Template URL version number in the path to match the version on the Qumulo cluster.

Architecture
Figure 38. Use current template for the stack update
  1. The top-level stack displays UPDATE_COMPLETE in the Stacks and Events lists.

FAQ

Q. I encountered a CREATE_FAILED error when I launched the Quick Start.

A. If AWS CloudFormation fails to create the stack, relaunch the template with Rollback on failure set to Disabled. This setting is under Advanced in the AWS CloudFormation console on the Configure stack options page. With this setting, the stack’s state is retained, and the instance keeps running so that you can troubleshoot the issue. (For Windows, look at the log files in %ProgramFiles%\Amazon\EC2ConfigService and C:\cfn\log.)

When you set Rollback on failure to Disabled, you continue to incur AWS charges for this stack. Delete the stack when you finish troubleshooting.

For more information, see Troubleshooting AWS CloudFormation.

Q. I encountered a size-limitation error when I deployed the AWS CloudFormation templates.

A. Launch the Quick Start templates from the links in this guide or from another S3 bucket. If you deploy the templates from a local copy on your computer or from a location other than an S3 bucket, you might encounter template-size limitations. For more information, see AWS CloudFormation quotas.

Q. I forgot which passwords I entered in the CloudFormation template.

A. In the AWS Management Console, navigate to Secrets Manager. The passwords entered in the CloudFormation template are stored under <stackname>-SECRETSSTACK…​-DomainControllerSecrets. Choose Retrieve secret value to locate the user names and passwords for the Active Directory server.

Troubleshooting

Confirm that the provisioner node successfully shut down by inspecting the EC2 instances and filtering on the stack name in the AWS Management Console. Make sure to clear the running instances filter. The provisioner instance should automatically shut down soon after the main stack completes.

Even if the stack deploys successfully, if the provisioner instance cannot successfully complete the post-deployment steps, several issues might occur:

  • The SMB file share might not exist, which means that you cannot use the Q drive.

  • The cluster might not be joined to the Active Directory domain.

  • The EBS volumes might not be tagged with the stack name.

  • The link to Qumulo UI on the workstation desktop might not work.

Another cause of failure is with the local DNS resolution or the ability to reach public IP addresses. However, these issues are unlikely if you deployed the template into a new VPC. If the template was deployed into an existing VPC, causes of failure might include:

  • The existing VPC does not have a functioning NAT gateway, and the provisioning node is unable to reach public IP addresses for AWS services.

  • The existing VPC does not have route tables correctly configured for public and private subnets in relation to an internet gateway and NAT gateway.

  • The existing VPC has network access control lists (ACLs) that are blocking traffic.

  • The existing VPC has DHCP options that are misconfigured for the Active Directory server that the stack deployed, causing DNS resolution issues. Review the DHCP Options section to review and resolve the options created by the stack and other option sets in the VPC.

  • The existing VPC already had an Active Directory server, and now a conflict exists.

Customer responsibility

After you successfully deploy this Quick Start, confirm that your resources and services are updated and configured — including any required patches — to meet your security and other needs. For more information, see the AWS Shared Responsibility Model.

Parameter reference

Unless you are customizing the Quick Start templates for your own deployment projects, keep the default settings for the parameters labeled Quick Start S3 bucket name, Quick Start S3 bucket Region, and Quick Start S3 key prefix. Changing these parameter settings automatically updates code references to point to a new Quick Start location. For more information, see the AWS Quick Start Contributor’s Guide.

Parameters for launching into a new VPC

Table 1. AWS network configuration
Parameter label (name) Default value Description

Specify an Availability Zone (AvailabilityZone)

Requires input

All resources are created in this Availability Zone.

AWS VPC subnet (VpcCidr)

10.0.0.0/16

Must be specified as an IPv4 address followed by / and a subnet mask of 0-32.

AWS VPC public subnet (PublicSubnetCidr)

10.0.1.0/24

Must be an IPv4 address followed by / and a subnet mask of 0-32.

AWS VPC private subnet (PrivateSubnetCidr)

10.0.2.0/24

Must be an IPv4 address followed by / and a subnet mask of 0-32.

Table 2. Qumulo file data platform configuration
Parameter label (name) Default value Description

Qumulo usable capacity and media type (QCapacityType)

1TB All Flash

1 TB All Flash or 12 TB Hybrid (Flash First architecture with st1 backing disks).

Qumulo EC2 instance type (QInstanceType)

m5.2xlarge

EC2 instance type for Qumulo nodes. Write/read max throughput in MBs for 1-TB All Flash: m5.2xlarge = 1400/2100, m5.8xlarge = 2000/2500, c5n.9xlarge = 2500/3800. Write/read max throughput in MBs for 12-TB hybrid: m5.2xlarge = 800/2100, m5.8xlarge = 1100/2400.

(Optional) Amazon EBS volumes encryption key (VolumesEncryptionKey)

Blank string

The AWS Key Management Service (AWS KMS) key to encrypt the volumes. Use either a key ID, Amazon Resource Name (ARN), or an alias. Aliases must begin with alias/ followed by the name, such as alias/exampleKey. If empty, the default Amazon EBS key is used. Choosing an invalid key name causes the instance to fail to launch.

Qumulo cluster name (QClusterName)

Cloud-Q

Name must be an alphanumeric string between 2 and 15 characters. Dash (-) is allowed if not the first or last character.

Qumulo security group (QSgCidr)

10.0.0.0/16

An IPv4 CIDR block for specifying the generated security group’s allowed addresses for inbound traffic. Set to x.x.x.x/32 to allow one specific IP address access, 0.0.0.0/0 to allow all IP addresses access, or another CIDR range.

SMB share name (SMBShareName)

adobe-projects

Server Message Block (SMB) share name.

(Optional) Qumulo instance recovery topic (QInstanceRecoveryTopic)

Blank string

Optionally enter the ARN of an SNS topic that receives messages when an instance alarm is triggered.

Table 3. Qumulo CloudWatch metrics and monitoring configuration
Parameter label (name) Default value Description

Qumulo sidecar user name (SideCarUsername)

SideCarUser

NO_DESCRIPTION

Qumulo sidecar password (SideCarPassword)

Requires input

Requires a minumum of 8 characters and must include at least one uppercase, one lowercase, and one special character.

Qumulo sidecar template URL (SideCarTemplate)

https://qumulo-sidecar-us-east-1.s3.amazonaws.com/4.2.0/sidecar_cft.json

Do not change unless a newer version of Qumulo is being used.

(Optional) Qumulo sidecar SNS topic (SideCarSNSTopic)

Blank string

Optionally enter an SNS topic ARN to which Lambda errors and successful disk replacements are published.

Table 4. Adobe workstation configuration
Parameter label (name) Default value Description

AWS Teradici instance type (windowsGrxInstanceType)

g4dn.2xlarge

Adobe editorial personas: 2xlarge = news/simple edit, 4xlarge = creative, 8xlarge = promo.

(Optional) Total number of Adobe workstations (numberOfWorkstations)

1

The total number of workstations to build with the instance type.

(Optional) Remote public IP CIDR (publicRemoteCidr)

0.0.0.0/0

Must be specified as an IPv4 address followed by / and a subnet mask of 0-32. 0.0.0.0/0 (any public source IP can attempt to access the workstation). If the public source network is not static or is unknown for the clients accessing the workstation, keep the default value of 0.0.0.0/0.

Table 5. Domain controller (Active Directory and DNS) configuration
Parameter label (name) Default value Description

Active Directory service administrator user name (adServiceAccountUsername)

SvcAdmin

User name for the service administrator account.

Active Directory service administrator password (adServiceAccountPassword)

Requires input

Password for the service administrator user. Must be at least 8 characters containing letters, numbers, and symbols.

Domain controller administrator user name (dcAdminUsername)

administrator

User name for the domain administrator account. This account is not the same as the default administrator account.

Domain controller administrator password (dcAdminPassword)

Requires input

Password for the domain administrator user. Must be at least 8 characters containing letters, numbers, and symbols.

Domain controller safe-mode administrator password (safeModeAdminPassword)

Requires input

Password for a separate administrator account when the domain controller is in restore mode. Must be at least 8 characters containing letters, numbers, and symbols.

Active Directory accounts: base user name (testusername)

studioqUser

Base user name for 20 Active Directory accounts that will be created. For example, studioqUser1 through studioqUser20 will be created with a base user name of studioqUser.

Active Directory accounts: default password (testuserpassword)

Requires input

Default password for the Active Directory accounts that will be created. Must be at least 8 characters containing letters, numbers, and symbols.

Domain name (domainName)

studioq.local

Private DNS Fully Qualified Domain Name (FQDN).

DNS record name for Qumulo Round Robin DNS (qumuloFloatRecordName)

qumulo

Record name for Round Robin DNS entries for Qumulo cluster floating IPs.

Table 6. AWS Quick Start configuration
Parameter label (name) Default value Description

AWS key-pair name (KeyPair)

Requires input

Name of an existing EC2 key pair to enable authentication to instances.

Quick Start S3 bucket name (QSS3BucketName)

aws-quickstart

Name of the S3 bucket for your copy of the Quick Start assets. Keep the default name unless you are customizing the template. Changing the name updates code references to point to a new Quick Start location. This name can include numbers, lowercase letters, uppercase letters, and hyphens, but do not start or end with a hyphen (-). See https://aws-quickstart.github.io/option1.html.

Quick Start S3 bucket Region (QSS3BucketRegion)

us-east-1

AWS Region where the Quick Start S3 bucket (QSS3BucketName) is hosted. Keep the default Region unless you are customizing the template. Changing this Region updates code references to point to a new Quick Start location. When using your own bucket, specify the Region. See https://aws-quickstart.github.io/option1.html.

Quick Start S3 key prefix (QSS3KeyPrefix)

quickstart-qumulo-studio-q/

S3 key prefix that is used to simulate a directory for your copy of the Quick Start assets. Keep the default prefix unless you are customizing the template. Changing this prefix updates code references to point to a new Quick Start location. This prefix can include numbers, lowercase letters, uppercase letters, hyphens (-), and forward slashes (/). End with a forward slash. See https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html and https://aws-quickstart.github.io/option1.html.

Parameters for launching into an existing VPC

Table 7. AWS network configuration
Parameter label (name) Default value Description

AWS VPC ID (VpcId)

Requires input

ID of the VPC (e.g., vpc-0343606e).

AWS VPC subnet (VpcCidr)

10.0.0.0/16

Must be specified as an IPv4 address followed by / and a subnet mask of 0-32.

Public subnet ID (PublicSubnetId)

Requires input

ID of the public subnet.

Private subnet ID (PrivateSubnetId)

Requires input

ID of the private subnet.

Table 8. Qumulo file data platform configuration
Parameter label (name) Default value Description

Qumulo usable capacity and media type (QCapacityType)

1TB All Flash

1 TB All Flash or 12 TB Hybrid (Flash First architecture with st1 backing disks).

Qumulo EC2 instance type (QInstanceType)

m5.2xlarge

EC2 instance type for Qumulo nodes. Write/read max throughput in MBs for 1 TB All Flash: m5.2xlarge = 1400/2100, m5.8xlarge = 2000/2500, c5n.9xlarge = 2500/3800. Write/read max throughput in MBs for 12 TB Hybrid: m5.2xlarge = 800/2100, m5.8xlarge = 1100/2400.

(Optional) Amazon EBS volumes encryption key (VolumesEncryptionKey)

Requires input

The AWS KMS key to encrypt the volumes. Use either a key ID, Amazon Resource Name (ARN), or an alias. Aliases must begin with alias/ followed by the name, such as alias/exampleKey. If empty, the default KMS EBS key is used. Choosing an invalid key name causes the instance to fail to launch.

Qumulo cluster name (QClusterName)

Cloud-Q

Name must be an alphanumeric string between 2 and 15 characters. Dash (-) is allowed if not the first or last character.

Qumulo security group (QSgCidr)

10.0.0.0/16

An IPv4 CIDR block for specifying the generated security group’s allowed addresses for inbound traffic. Set to x.x.x.x/32 to allow one specific IP address access, 0.0.0.0/0 to allow all IP addresses access, or another CIDR range.

Linux server for secondary configuration of Qumulo (ProvisioningServerAMI)

/aws/service/ami-amazon-linux-latest/amzn2-ami-hvm-x86_64-gp2

Linux server Amazon Machine Image (AMI).

SMB share name (SMBShareName)

adobe-projects

Server Message Block (SMB) share name.

(Optional) Qumulo instance recovery topic (QInstanceRecoveryTopic)

Blank string

Optionally enter the ARN of an SNS topic that receives messages when an instance alarm is triggered.

Table 9. Qumulo CloudWatch metrics and monitoring configuration
Parameter label (name) Default value Description

Qumulo sidecar user name (SideCarUsername)

SideCarUser

NO_DESCRIPTION

Qumulo sidecar password (SideCarPassword)

Requires input

Requires a minimum eight characters and must include one uppercase, one lowercase, and one special character.

Qumulo sidecar template URL (SideCarTemplate)

https://qumulo-sidecar-us-east-1.s3.amazonaws.com/4.2.0/sidecar_cft.json

Do not change unless a newer version of Qumulo is being used.

(Optional) Qumulo sidecar SNS topic (SideCarSNSTopic)

Blank string

Optionally enter an SNS topic ARN to which Lambda errors and successful disk replacements are published.

Table 10. Adobe workstation configuration
Parameter label (name) Default value Description

AWS Teradici instance type (windowsGrxInstanceType)

g4dn.2xlarge

Adobe editorial personas: 2xlarge = news/simple edit, 4xlarge = creative, 8xlarge = promo.

(Optional) Total number of Adobe workstations (numberOfWorkstations)

1

Specify the total number of workstations to build with the instance type.

(Optional) Remote public IP CIDR (publicRemoteCidr)

0.0.0.0/0

Must be specified as an IPv4 address followed by / and a subnet mask of 0-32. 0.0.0.0/0 (any public source IP can attempt to access the workstation). If the public source network is not static or is unknown for the clients accessing the workstation, keep the default value of 0.0.0.0/0.

Table 11. Domain controller (Active Directory and DNS) configuration
Parameter label (name) Default value Description

Active Directory service administrator user name (adServiceAccountUsername)

SvcAdmin

User name for the service administrator account.

Active Directory service administrator password (adServiceAccountPassword)

Requires input

Password for the service administrator user. Must be at least eight characters containing letters, numbers, and symbols.

Domain controller administrator user name (dcAdminUsername)

administrator

User name for the domain administrator account. This account is not the same as the default administrator account.

Domain controller administrator password (dcAdminPassword)

Requires input

Password for the domain administrator user. Must be at least eight characters containing letters, numbers, and symbols.

Domain controller safe-mode administrator password (safeModeAdminPassword)

Requires input

Password for a separate administrator account when the domain controller is in restore mode. Must be at least eight characters containing letters, numbers, and symbols.

Active Directory accounts: base user name (testusername)

studioqUser

Base user name for the 20 Active Directory accounts that are created. For example, studioqUser1 through studioqUser20 are created with a base user name of studioqUser.

Active Directory accounts: default password (testuserpassword)

Requires input

Default password for the Active Directory accounts that are created. Must be at least eight characters containing letters, numbers, and symbols.

AWS directory server AMI (DirectoryServerAmi)

/aws/service/ami-windows-latest/Windows_Server-2019-English-Full-Base

AWS Windows Server AMI for the domain controller and Active Directory.

Domain name (domainName)

studioq.local

Private DNS Fully Qualified Domain Name (FQDN).

DNS record name for Qumulo Round Robin DNS (qumuloFloatRecordName)

qumulo

Record name for Round Robin DNS entries for Qumulo cluster floating IPs.

Table 12. AWS Quick Start configuration
Parameter label (name) Default value Description

AWS key pair name (KeyPair)

keypairname

Name of an existing EC2 key pair to enable authentication to instances.

Quick Start S3 bucket name (QSS3BucketName)

aws-quickstart

Name of the S3 bucket for your copy of the Quick Start assets. Keep the default name unless you are customizing the template. Changing the name updates code references to point to a new Quick Start location. This name can include numbers, lowercase letters, uppercase letters, and hyphens, but do not start or end with a hyphen (-). See https://aws-quickstart.github.io/option1.html.

Quick Start S3 bucket Region (QSS3BucketRegion)

us-east-1

AWS Region where the Quick Start S3 bucket (QSS3BucketName) is hosted. Keep the default Region unless you are customizing the template. Changing this Region updates code references to point to a new Quick Start location. When using your own bucket, specify the Region. See https://aws-quickstart.github.io/option1.html.

Quick Start S3 key prefix (QSS3KeyPrefix)

quickstart-qumulo-studio-q/

S3 key prefix that is used to simulate a directory for your copy of the Quick Start assets. Keep the default prefix unless you are customizing the template. Changing this prefix updates code references to point to a new Quick Start location. This prefix can include numbers, lowercase letters, uppercase letters, hyphens (-), and forward slashes (/). End with a forward slash. See https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html and https://aws-quickstart.github.io/option1.html.

Send us feedback

To post feedback, submit feature ideas, or report bugs, use the Issues section of the GitHub repository for this Quick Start. To submit code, see the Quick Start Contributor’s Guide.

Quick Start reference deployments

GitHub repository

Visit our GitHub repository to download the templates and scripts for this Quick Start, to post your comments, and to share your customizations with others.


Notices

This document is provided for informational purposes only. It represents AWS’s current product offerings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS’s products or services, each of which is provided “as is” without warranty of any kind, whether expressed or implied. This document does not create any warranties, representations, contractual commitments, conditions, or assurances from AWS, its affiliates, suppliers, or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers.

The software included with this paper is licensed under the Apache License, version 2.0 (the "License"). You may not use this file except in compliance with the License. A copy of the License is located at http://aws.amazon.com/apache2.0/ or in the accompanying "license" file. This code is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either expressed or implied. See the License for specific language governing permissions and limitations.