Preserve your AMS assets

Integrate your existing AMS assets into MK.IO without relocation

This guide walks through the steps needed to integrate existing file assets, that you have hosted and available for streaming in AMS, into MK.IO.

👍

This is done in minimal steps, without any need to relocate, re-process or re-encode your source files.

Before starting

Ensure that you have subscribed to MK.IO through Azure Marketplace and that your MK.IO subscription is up and running.

Also ensure that you Connect your Azure storage account that contains the assets that you need to integrate. MK.IO will connect directly to this account, to index the existing files and create new access URLs for you to stream your content from. Assets will remain in your Azure storage account and part of your existing Azure subscription. Access to your assets, from MK.IO, can be easily managed by you, using the Shared Access Signature (SAS token) that you create directly in Azure.

Import your assets

Three different approaches are possible to reference your first assets in MK.IO.

👍

Whatever the approach, your asset remain in their storage after migration.

Using AMS Migration tool from MediaKind

All the steps are detailed in Bulk asset migration from AMS storage.

Using Azure Media Services Explorer tool

You can retrieve the AMS Explorer tool in this public GitHub repository: https://github.com/Azure/Azure-Media-Services-Explorer

This version of the Azure Media Services Explorer supports creating assets in MK.IO from existing AMS assets.

Using the MK.IO web interface

Once logged into the MK.IO portal, you import your assets, stored in the storage accounts that you have connected to MK.IO, in a few simple steps.

📘

Existing assets need to be encoded into an MP4 container format for import and saved in your storage account with associated .ism (manifest) and .ismc (client manifest) files.

  • From the MK.IO Dashboard view, go to Assets from the left-hand side menu.
  • On the top right of the Asset page, click Migrate Asset to bring up the migration dialog box.
  • Fill out the information in the dialog with the following information:
SettingDescription
NameThe unique identifier you want to use in MK.IO for that asset.
DescriptionThe name of the specific container where the hosted assets lives in your Azure Storage Account.
Storage ContainerThe name of the specific container where the hosted assets lives in your Azure Storage Account.
In AMS, each asset is stored in a specific container. You can confirm the storage container name by navigating to the Assets view in AMS, locating your 'output' asset name you need to migrate and copying the name of the 'Storage Link' field. This will typically start with an asset-XXX naming convention and point to the container where the associated files are stored.
Storage Account From the drop down, select the connected Storage Account linked to your MK.IO account, where the asset is located.

When you click submit, the asset will be saved in your list and MK.IO will connect, ingest, and make the content available to be configured for streaming.

You can repeat this process to migrate as many assets as you need into MK.IO.

📘

This workflow is to migrate assets one at a time

To view the workflow to import video assets in bulk from AMS to MK.IO and retrieve the bulk-ingest tool, see the support article Bulk Migration to MK.IO from AMS.

Once completed, you will see all available assets in your Assets view via the Dashboard.

Verify your assets have been imported

Once you have imported an asset, you can verify that it's been ingested and indexed into MK.IO.

  • Click on the asset name in the list using the link.
  • In the Asset page, scroll down to the 3rd pane you should see:
    • Tracks: Which shows all the video track information for that asset.
    • Files on Storage: Which shows all the files and associated metadata ingested from your storage account.

If you can't see any tracks or files listed, then:

  • Check you have connected your Azure Storage account correctly. Verifying you've used the correct and SAS keys that are valid and haven't expired.
  • Check you have copied your storage container name correctly as detailed in the callout above.

If you still have trouble seeing your migrated assets, try our community and support pages for more help.