AMSMigrate 1.0.1

Azure Media Services Migration Tool

Overview

A rich and flexible command line tool to migrate your data from Azure Media Services. This tool helps you to migrate your media data from Azure Media Services (AMS). It can be used to just copy the data to other cloud storage like AWS S3 or GCS. Or can be packaged to be streamed directly from Azure storage without any service.

It has extensible support to migrate AMS assets to Azure storage or AWS S3 or GCS. Fairly easy to plugin another service (e.g mux.com or encoding.com) or another cloud storage if needed.

The tool supports both ffmpeg and shaka-packager to conver the videos to directly streamable format. The content is converted to CMAF format with both a DASH and HLS manifest to support a wide range of devices. The default is shaka packager because it can use pipes to reduce the temporary storage required but can changed via the command line.

Features

• Cross-Platform. Works on all platforms where .NET core is available.
• Simple command line interface. Intuitive and easy to use.
• Docker container to run anywhere or can be installed as a .NET tool.
• Support for packaging both VOD and live archive assets.
• Marks migrated assets and provides summary.

Open Issues

• More testing on AWS/GCP migration.
• Support to migrate AMS transforms to AWS Elemental Media Convert Job Specification.
• Support to convert AMS transforms to GCS Trancsode API Job templates.
• Support to migrate AMS Keys to AWS KMS or GCP Secret Manager.

How to Install

• Install .NET SDK for the platform you are runnig. Click here on how to download.
• Run the following command to install the tool

dotnet tool install -g amsmigrate

How to Run

Run the tool with -? to get more help

amsmigrate -?

A typical command is of the form

amsmigrate command [options]

Credentials used

The tools uses Azure Identity library for authentication. See here for various ways to authenticate and the settings needed. The identity used to migrate must have 'Contributor' role on the Azure Media Services account being migrated and 'Storage Blob Delegator' role on the storage account associated.

Types of Migration

The tool supports various types of migration depending on the asset format and the command line options.

• It can simply upload the files to the new storage account.
• For assets created by live events, it can convert to MP4 files and then upload.
• For direct streaming, it can convers the assets to CMAF files with a DASH and HLS manifest.

FFmpeg dependency

The tool uses ffmpeg for media format conversion. It doesn't ship a copy of FFmpeg itself but uses the one in the PATH.

• On Windows you can use winget or chocolatey to install ffmpeg.

winget install ffmpeg

• On Ubuntu/Debian Linux use apt to install ffmpeg

sudo apt install -y ffmpeg

• On RedHat Linux use dnf to install ffmpeg.

sudo dnf install ffmpeg

• On MacOs use brew to install ffmpeg

brew install ffmpeg

Temporary storage needed.

The tool uses temporary storage space for format conversion and the amount of storage needed is directly proportional to the size of the files in the asset.

Migrate to an Azure Storage Account.

Migrate to an AWS S3 account.

Migrate to a custom service.

• Clone the source code locally.
• Implement your custom migration.
• Build and Run the code locally. You can write your own custom migrator if needed

Running the tool in the Azure Cloud.

The tool is packaged as a docker container and is available to run in the cloud via Azure Container Instances or Azure Functions.