Automated deployment - AWS Edit in the Cloud

Automated deployment

Before you launch the solution, review the architecture, network security, other considerations discussed in this guide. Follow the step-by-step instructions in this section to configure and deploy the solution into your account.

Time to deploy: Approximately one hour

Deployment overview

Use the following steps to deploy this solution on AWS. For detailed instructions, follow the links for each step.

Step 1. Launch the stack

  • Launch the AWS CloudFormation template into your AWS account.

  • Enter values for required parameters: Availability Zones, Edit Host Access CIDR, Key Pair Name, and Domain Admin Password.

  • Review the other template parameters, and adjust if necessary.

Step 2. Add Teradici license to the EC2 instance

  • Obtain the EC2 IP address.

  • Activate the Teradici license.

Step 3. Mount the NVMe Disk

  • Use Windows PowerShell terminal to mount the NVMe Disk.

Step 4. Load data from Amazon S3

  • Use Windows PowerShell terminal to load data from Amazon S3.

Step 1. Launch the stack

This automated AWS CloudFormation deploys Edit in the Cloud in the AWS Cloud.

Note

You are responsible for the cost of the AWS services used while running this solution. For more details, visit to the Cost section in this guide, and refer to the pricing webpage for each AWS service used in this solution.

  1. Sign in to the AWS Management Console and select the button to launch the aws-edit-in-the-cloud AWS CloudFormation template.

    
              AWS Edit in the Cloud launch button

    Alternatively, you can download the template as a starting point for your own implementation.

  2. The template launches in the US East (N. Virginia) Region by default. To launch the solution in a different AWS Region, use the Region selector in the console navigation bar.

  3. On the Create stack page, verify that the correct template URL is in the Amazon S3 URL text box and choose Next.

  4. On the Specify stack details page, assign a name to your solution stack. For information about naming character limitations, refer to IAM and STS Limits in the AWS Identity and Access Management User Guide.

  5. Under Parameters, review the parameters for this solution template and modify them as necessary. This solution uses the following default values.

    Parameter Default Description
    Network Configuration
    Availability Zones <Requires input> Select two Availability Zones to use for the VPC subnets. The template presents all Availability Zones available, select two.
    VPC CIDR 10.0.0.0/16 CIDR block for the VPC that contains the Windows EC2 instance.
    Private Subnet 1 CIDR 10.0.0.0/19 CIDR block for private subnet 1 located in Availability Zone 1.
    Private Subnet 2 CIDR 10.0.32.0/19 CIDR block for private subnet 2 located in Availability Zone 2.
    Public Subnet 1 CIDR 10.0.128.0/20 CIDR block for the public DMZ subnet 1 located in Availability Zone 1.
    Public Subnet 2 CIDR 10.0.144.0/20 CIDR block for the public DMZ subnet 2 located in Availability Zone 2.
    Amazon EC2 Configuration
    Amazon EC2 instance type g4dn.4xlarge

    The Amazon EC2 instance type for the video editing servers.

    Note: You can change the size of the EC2 instance that you can use for editing; however, the majority of the price is based on the size of the EC2 instance that you select here. Check the Cost section for more information.

    Edit Host Access CIDR <Requires input>

    The CIDR block that is used for the security group on your Amazon EC2 instance editing host.

    Note: Use a website such as, https://checkip.amazonaws.com to determine your public facing IP address for this step.

    Key Pair Name <Requires input> The PEM key that allows you to securely connect to your EC2 instance after it launches. You can create a PEM key in the Amazon EC2 console.
    Microsoft Active Directory Configuration
    Domain DNS Name example.com Fully qualified domain name (FQDN) of the forest root domain.
    Domain NetBIOS Name example NetBIOS name of the domain (up to 15 characters) for users of earlier versions of Windows.
    Domain Admin User Admin User name for the account that will be added as Domain Administrator. This is separate from the default Administrator account.
    Domain Admin Password <Requires input> Password for the Domain Administrator user. Must be at least 8 characters containing letters, numbers, and symbols.
    FSx Configuration
    FSx File System Size 1024 The storage capacity of the file system being created. 32 GiB - 65,536 GiB (64 TiB)
    FSx Throughput 16 The throughput capacity of an Amazon FSx file system, measured in megabytes per second in powers of 2 (8, 16, 32, .., 1024), with the recommended value based on the file system size: 8 for <800 GiB, 16 for <1,600 GiB, ... 512 for <51,200 GiB, 1,024 for >=51,200 GiB
    FSx AZ Deployment Mode SINGLE_AZ_2 Specifies the file system deployment type.
    Other Parameters
    Project Cloud-video-edit-fsx Used for billing and resource groups.
  6. Choose Next.

  7. On the Configure stack options page, choose Next.

  8. On the Review page, review and confirm the settings. Check the boxes acknowledging that the template will create AWS Identity and Access Management (IAM) resources.

  9. Choose Create stack to deploy the stack.

    You can view the status of the stack in the AWS CloudFormation Console in the Status column. You should receive a CREATE_COMPLETE status in approximately one hour.

Note

This solution includes the custom-resource AWS Lambda function, which runs only during initial configuration or when resources are updated or deleted. Do not delete this function because it is necessary to manage associated resources.

Step 2. Add Teradici license to the EC2 instance

After the stack deploys, use Windows Remote Desktop to add a Teradici license to the EC2 instance. First, obtain the public IP address of the EC2 edit host.

Obtain the EC2 IP address

  1. Navigate to the Amazon Elastic Compute Cloud console.

  2. In the navigation pane, choose Instances.

  3. Select the win-host EC2 instance

  4. On the Networking tab, copy the value for Public IPv4 address.

Windows connection steps

  1. Open Remote Desktop. If you can’t find it, choose Start, enter MSTSC, and press Enter.

  2. When prompted, enter the IP address of the edit host and choose Connect.

  3. When prompted, enter the username and password. The username is the value that you entered for the Domain Admin User parameter (Admin by default). The password is the value that you entered for the Domain Admin Password parameter when launching the stack.

MacOS connection steps

If you use MacOS, you must download the Microsoft Remote Desktop Client from the App Store.

  1. Open Microsoft Remote Desktop.

  2. Select the + icon, then select Add PC.

  3. For PC Name, enter the IP address of the edit host. You can specify a friendly name for easy reference, such as Edit Host.

  4. Choose Add.

  5. When the new PC appears in your connection options, select it to connect to the EC2 instance.

  6. When prompted, enter the username and password. The username is the value that you entered for the Domain Admin User parameter (Admin by default). The password is the value that you entered for the Domain Admin Password parameter when launching the stack.

Activate the Teradici license

In order to use Teradici, you must purchase a license first.

  1. Select the Teradici icon (refer to Figure 2), and choose Licensing.

    
          Teradici icon

    Figure 2: Teradici icon

  2. In the PCoIP Control Panel box, enter your registration code, and choose Register.

Connect to the edit host

After activating your Teradici license, connect to the edit host using a Teradici PCoIP Client.

  1. On the connection screen, enter in the IP address of your edit host and a connection name for future reference.

  2. When prompted for a username and password, use the same credentials you used earlier to connect to the instance using Windows Remote Desktop.

    You are now connected to your edit host using Teradici.

Step 3. Mount the NVMe disk

In this deployment, we will mount ephemeral storage to the edit host for a scratch media edit space. Ephemeral storage provides low-latency to the host as it is physically attached storage.

Important

Any assets stored on this volume will be lost upon edit host reboot or termination. We recommend saving all project assets to the FSx file share.

  1. Open Windows Powershell terminal:

    1. Choose Start.

    2. Enter “powershell” in the Search bar.

    3. Right click the Windows Powershell icon and choose Run as Administrator.

    4. If prompted with an alert to allow Windows Powershell to make changes on your device, select Yes.

  2. In the Windows Powershell terminal, enter the following Powershell command to change to the correct directory:

    cd C:\ProgramData\Amazon\EC2-Windows\Launch\Scripts
  3. Enter the following Powershell command to mount the NVMe disk:

    .\InitializeDisks.ps1

The FSx file share mounts to the F drive upon user sign in.

Step 4. (Optional) Load data from Amazon S3

Follow these steps to move your media assets from Amazon S3 to Amazon FSx for Windows File Server.

  1. Choose Start.

  2. Enter “powershell” in the Search bar.

  3. Select Windows Powershell for AWS.

  4. Change to the FSx File Share drive mapping:

    F:
  5. Create a new directory for media:

    mkdir Media
  6. Use the following command to list the contents of your S3 bucket:

    aws s3 ls s3://<bucket-name>
  7. Use the following command to load the data from your S3 Bucket into the FSx File Share. <key-prefix> is any folder or object you want to load into the file share.

    aws s3 sync s3://<bucket-name>/<key-prefix> .\Media\

To verify that your files were synchronized from S3 to the FSx file share

  1. Navigate to your Windows File Explorer, then to your FSx File Share, which is mounted to the F: Drive.

  2. From your file share, verify that the Media folder is there.

  3. Open the Media folder and check that the contents of your S3 Bucket have synchronized.