[Edit in the Cloud] AWS Media Asset Preparation System (MAPS) Construction Guide

Introduction

In an introductory blog post on the AWS Media Asset Preparation System (AWS MAPS), MAPS uploads media to AWS, organizes files / folders, moves files on AWS storage volumes, prepares media, assigns permissions, searches, and filters. , I gave an overview of how to solve issues such as content distribution. This article provides an overview of how MAPS plays an important role in the production process and provides a step-by-step guide detailing how to deploy MAPS in your environment. After introducing MAPS, I hope that you can refer to this guide and connect it to the pipeline construction of the production environment.

Use cases in production

Suppose the day's shoot is over and the material is uploaded to Amazon Simple Storage Service (Amazon S3) as part of your production content lake strategy. Media managers and administrators must organize these assets into logical groups and make them available to editors the next day.

There are some major challenges to this workflow.

That's where MAPS comes in. MAPS provides an interface that allows production professionals, including media managers and administrators, to visualize assets and organize them intuitively with just a few clicks. This user interface eliminates the technical side and allows media managers and administrators to focus on content and production requirements. Once the assets are organized, the media manager can add permissions to prepare the editor for the upcoming editing session. At the end of the editing session, media managers and administrators can use MAPS to clean up and organize their files while advancing best practices on various storage volumes. These efforts save storage and optimize costs, regardless of the size of the production.

Step-by-step construction

This section provides a guide for deploying MAPS in your AWS environment.

Requirements

1. AWS account
2. Code repository (eg GitHub)

Step 1: One-click deployment with AWS Amplify

1. Click this orange button to deploy MAPS with your AWS account.

1. You will be redirected to the AWS Amplify page in the AWS Management Console.

1. Select "Connect to GitHub" to create a fork of the MAPS main repository under your GitHub account.
2. If you haven't used AWS Amplify, which has been approved in the past, you'll be redirected to GitHub for approval.

1. Once GitHub approval is complete, you'll be automatically redirected to the Amplify console. If you have not set the Amplify backend service role in the past, select "Create New Role".

1. Select Save and deploy.
2. Click Continue when you have completed the three deployment process steps.

This deployment can take up to 20 minutes.

Settings and setup

Step 2: Create admin user

By default, all new users registered on the MAPS sign page are assigned to the "editors" user group.

1. In the Amazom Cognito UserPool Console, select mapsuserpool-.

1. Select Create User from Users and Groups.

1. Enter the required information and click Create User.

1. Select the user created above and click "Add to Group".

1. Select admin from the drop-down list and click Add to Group.

Note: It is mandatory to add the admin user to the "admin group". If this setting is not made, the MAPS interface function cannot be used.

Step 3: MAPS interface settings

1. In the AWS CloudFormation console, locate amplify-maps --- resMAPS.

1. Select the Outputs tab and copy the MediaBucketName.

1. Get the URL where MAPS was deployed from the AWS Amplify console.

1. Open the URL from a web browser (Chrome recommended).
2. On the sign-in page, log in with the "admin" user information created above.

1. The first time you log in, you will be asked to change your password.

1. After logging in, you can access the MAPS interface.

1. To set the interface, select the gear icon on the control toolbar.
2. Enter the Media Bucket Name on the settings page, save and return to the main view. This will register the bucket with the deployed MAPS. This setting only needs to be done once in admin.

Note: If you see an error, make sure there are no spaces before or after the bucket name.

Step 4: Register the Amazon FSx for Windows file server with MAPS

MAPS allows you to move assets between storage volumes such as Amazon S3 and Amazon FSx for Windows file servers. To take advantage of this feature, you need to deploy the Edit in the Cloud environment to your AWS account. If you don't have an existing Edit in the Cloud deployment, you can deploy from this GitHub repo.

1. Gets the DNS name of the Amazon FSx for Windows file server used from the console.

1. Open the MAPSApiProcessing-Lambda function.

1. In the Configuration settings, select Environment Variables from the left menu.

1. Enter the Amazon FSx DNS name obtained in step 4.1 above in the FSX_MOUNT environment variable.

Note: Currently, to move files between Amazon S3 and Amazon FSx, you need to connect to an EC2 instance with a public Elastic IP address to work with MAPS.

1. Download the MoveMedia.ps1 script from here and save it to the next EC2 instance directory: C:\ProgramData\Amazon\EC2-Windows\Launch\Scripts : This script uses AWS Systems Manager (SSM) to save media files to Amazon S3. And needed to move between Amazon FSx.
2. Make sure the SSM agent is installed on your edit instance and that the AmazonEC2RoleforSSM policy is added to your instance profile.

Step 5: Prepare the media using MAPS

Once the MAPS deployment setup is complete, prepare the media files to start the workflow.

Control toolbar

You can work with media files on the control toolbar. The outline is described below.

1. Download – Download the asset from the registered Amazon S3 URL.
2. Delete – Deletes the asset.
3. Create New – Upload a new asset.
4. Create Folder – Create a new folder.
5. Settings – Set up your S3 bucket.

MAPS user interface

MAPS has two layouts. 1) The table layout is a view with a folder structure. 2) The card layout displays a thumbnail of the media along with the technical metadata.

Creating a folder

1. Click the Create Folder button from the control toolbar.
2. Enter the folder name and select "Create Folder".

Media upload

1. Click the "Create New" button to upload the file.
2. Click the Browse button and select the file. After selecting, click the "Upload" button.

1. The update status of the file is displayed as a percentage.

1. When the file is transferred to Amazon S3, the row is added to the MAPS table view.

1. The file format is automatically displayed when the backend process is complete. This allows successful transcoding for file preview and subsequent operations.

Media preview

1. To preview the media, double-click a row in Table view or double-click a thumbnail in Card view.
2. The media player plays the proxy file. You can also check the technical metadata.

Organize media files

1. To organize your media files into folders, select all the assets you want to move in the table view.

1. Right-click on the highlighted location and select Move to Folder.

1. Specify the destination of the asset selected in the folder navigation tool and click "Move".

Note: It may take several seconds depending on the number of files selected and the file size.

Move media files

1. To move media files between Amazon S3 and Amazon FSx, select the asset you want to move in the table view.

1. Right-click on the highlighted location and select Copy to FSx.

1. If you want to remove a file from Amazon FSx, select the asset, right-click on the highlighted location and select Remove from FSx.
2. If these actions are successful, the status field will be updated. If the file exists in Amazon S3 and its copy is in FSx, the status will be "S3_FSX", and if it exists only in S3, it will be "S3".

Note: It may take a few seconds to copy the files to the FSx for Windows file server and delete them from the same shared network.

Manage folder permissions

By default, when deploying MAPS, there are two permission groups, "admin" and "editors". When a user creates a folder, that folder and all the assets in it inherit that user's group permissions. The admin group is automatically added to all new folders. Users in the admin group are the only users who can update permissions for a particular folder. Group additions must be done in the Amazon Cognito console. For example, you can create separate permission groups for the editors of different projects and then add users to those user groups.

1. To change the folder permissions, right-click on the folder and select Permissions.

1. Select / deselect the groups you want to give or exclude, and click "Save".

Note: You cannot remove admin privileges.

Cleanup

To clean up your MAPS deployment, you need to empty the three S3 buckets that were created. The bucket names are as follows.

After deleting the content in your bucket, go to your AWS Amplify MAPS project and select Delete App from the Actions dropdown. This will remove all related resources deployed by MAPS.

If you have deployed the Edit in the Cloud solution, also delete the associated CloudFormation stack.

in conclusion

This article provided an overview of how MAPS fits into the production process and provided steps to get MAPS into your environment. For future code updates and feature releases, please visit the MAPS GitHub repository and star them to be notified of updates.

Many customers are using AWS for supply chain management, from ingest to media processing, creation, and delivery to the cloud. In addition, more than 80 AWS partners offer media supply chain & archiving applications. See https://aws.amazon.com/media/supply-chain-archive/ for more information.

Reference link

AWS Media Services AWS Media & Entertainment Blog (Japanese) AWS Media & Entertainment Blog (English)

For inquiries from the AWS media team: awsmedia@amazon.co.jp * We have started a monthly e-mail newsletter. We will send you the latest news and event information. If you would like to subscribe, please contact the above address.

He was translated by BD Yamaguchi and SA Kobayashi. Please see here for the original text.