Skip to content

Latest commit

 

History

History
188 lines (126 loc) · 12.3 KB

app-migration.md

File metadata and controls

188 lines (126 loc) · 12.3 KB
Raw

Complete guide of Migration to RMS

Prerequisites

✅ You have an RMS instance deployed using Azure Marketplace.

✅ You have a Microsoft account with access to an Azure Tenant where the RMS instance is deployed.

✅ You obtained RMS connection credentials, learn more.

Note

Consider the following scenarios before starting:

  1. Encrypted Videos (AES or DRM): If you have a large number of encrypted videos (AES or DRM) consider using the migration option to generate new keys instead of migrating existing ones. AMS API throttling will not allow you to migrate more than 1200 assets per hour if they have content keys. Contact us to turn on the key-generation option in the migration configuration for you.

  2. Content Key Policies: Check if you have a large number of content key policies in your AMS account (e.g., policy per asset). This is considered bad practice from AMS's perspective (see Best Practices and Considerations) and is limited by AMS throttling to 1200 requests per hour. There is an option to apply a single policy for all migrated streaming locators of the same encryption scheme. Contact us, and we will specify it in the migration configuration before you start.

1. Register Your AMS Storage(s) in RMS

You can find here how to register a custom storage account with RMS.

Note

Before migrating, it is essential to include all storage accounts associated with your AMS account in the RMS Console. If any storage accounts are not listed, the migration process will not initiate. Additionally, ensure that each storage account has a Managed Identity assigned with the appropriate role as described on this page.

2. Migrate Your Application

The RMS API mirrors the AMS API, meaning no significant code changes are required. You can continue using your existing SDK and logic without modifications. However, RMS uses a different authentication scheme, so you will need to update your code to use the new credentials. You can copy them from the following sources:

Then your media service client initialization code will look like this:

// For Microsoft.Azure.Management.Media SDK
var credentials = new RmsApiKeyCredentials(
    new Uri("<RMS API endpoint>"),
    "<RMS Subscription ID>",
    "<RMS API Key>");

var mediaServicesClient = new AzureMediaServicesClient(credentials, new HttpClient(), true)
{
    SubscriptionId = "<RMS Subscription ID>"
};
// All mediaServicesClient method calls then use RMS Resource Group and Account Name

or

// For Azure.ResourceManager.Media SDK
var credentials = new RmsApiKeyCredentials(
    new Uri("<RMS API endpoint>"),
    "<RMS Subscription ID>",
    "<RMS API Key>");

ArmClient armClient = new ArmClient(
        credentials,
        "<RMS Subscription ID>",
        new ArmClientOptions
        {
            Environment = new ArmEnvironment(new Uri("<RMS API endpoint>"), "test"),
        });

var mediaServicesAccountIdentifier = MediaServicesAccountResource.CreateResourceIdentifier(
    "<RMS Subscription ID>",
    "<RMS Resource Group Name>",
    "<RMS Account Name>");

var mediaServiceClient = armClient.GetMediaServicesAccountResource(mediaServicesAccountIdentifier)

After applying these updates, your media service client initialization will be adapted for RMS.

You can see detailed implementations for a demo application that can switch between AMS and RMS:

3. Replace Azure Media Player with Another Player

Azure Media Player was developed specifically for AMS streams and does not work with other streaming links, including those from RMS. You need to use a different player. Currently, the following players are compatible with RMS:

You can find the developer guide on how to set up Ravnur Media Player here.

Validation

At this stage, you have completed the RMS compatibility changes in steps 2 and 3. Ensure the following:

  • your transforms work properly in RMS producing the expected output
  • videos are streamed according to your streaming and content key policies

This validates the success of the Migration steps above.

Additionally, the Streaming URL has been updated: the host name has been changed from the AMS endpoint to the RMS endpoint.

Old URL: http://ams111-aaaa.streaming.media.azure.net/...

New URL: http://fd-111a1aaaaa1-a1aaaaaaaaaaaaa.z02.azurefd.net/...

This URL change proves the successful completion of backend compatibility. A change of the player, surely, would represent the completion of front-end changes.

Please proceed with the remaining steps to fully complete the procedure.

Optional: Change Event Grid Subscriptions

RMS produces the same Event Grid events schema as AMS. Use these instructions to change your current Event Grid subscriptions to listen to RMS events instead.

Note

For this, your RMS instance should be deployed in the same subscription as your current AMS account.

4. AMS metadata migration

At this point you have your storages registered in RMS and you ensured that your application works seamlessly with RMS API. Now you can migrate all your existing AMS assets metadata to RMS. This migration copies only metadata of your assets; it does not copy or move your assets contents from storage. These instructions will guide you through this process.

Streaming Endpoints note

There is no migration of streaming endpoints from AMS to RMS. RMS does not support full streaming endpoints functionality. It contains only one hard-coded streaming endpoint which you can't remove. By default RMS streaming endpoint uses same domain name as API and Console. The only RMS streaming endpoint property which you can change is HostName which your code may require for producing streaming URLs (it concatenates Streaming Endpoint host name with Streaming Locator paths). If you are using CDN then you must specify your CDN domain name there (to verify it navigate to your Streaming Endpoint in Azure Portal). CDN migration instructions will tell you what actions are required from you in this case. If you do not want to use CDN but still want to use your custom domain name then please contact us and we will setup your custom domain in RMS for you.

5. Update CDN configuration

Change CDN domain

The AMS streaming domain will be deleted immediately after the AMS account is deleted. If you keep the AMS account active, it will be available for a while after AMS shutdown, but Microsoft will delete the DNS records before the end of 2024. So we highly recommend that you prepare your own custom domain for your CDN in advance before migrating to RMS. It means that all your existing streaming links should be updated from the AMS streaming endpoint domain to your own custom domain instead. There are two ways to use a new domain:

  1. Create a separate CDN endpoint that is pointed to the RMS streaming endpoint. It is the preferred option.
  2. Reuse your existing CDN endpoint (which you use for AMS account) and map your custom domain to that endpoint. Here Microsoft gives instructions on how to do this. After that, your CDN endpoint should look like this: CDN before RMS migration

Note

The second option makes releasing updates more difficult therefore, it is not recommended. There could be downtime after switching from AMS to RMS and purging the CDN cache. It's recommended to set up and test a separate CDN endpoint first, and then switch all video links to it.

Option 1: Create a separate CDN endpoint that uses RMS as the origin (recommended)

  1. Create an endpoint specifying your RMS streaming domain as the origin (it matches the RMS API endpoint domain) Create CDN endpoint
  2. Wait for the origin change to propagate in the CDN. This can take a while. To ensure that the new origin is available, you can check the URL in a browser: "https://{your custom CDN domain}/console".
  3. Then. To complete migration you just need to:
    • Repoint your application to use RMS API instead of AMS
    • Update existing streaming links in your system to use new streaming domain.

Option 2: Change origin for existing CDN endpoint

If for some reason you want to reuse the existing CDN endpoint (you have some complicated and specific settings) you can use this option. As far as you change the existing endpoint after this step, all your existing streaming links will be routed to the RMS streaming server. That's why it should be performed as part of your final migration procedure and incorporated into your first release with RMS, which can look like this:

  1. Repoint your application to use RMS API instead of AMS After this step, your application will create all new videos in RMS instead of AMS, but their links will not work from CDN until the next step is completed.

  2. Change your CDN origin

    • Navigate to your AMS Streaming Endpoint CDN profile
    • Select the endpoint routed to your AMS endpoint. Ams endpoint location
    • Change the origin to your RMS streaming domain (it matches the RMS API endpoint domain). Change CDN origin
    • Wait for the origin change to propagate in the CDN. This can take a while. To ensure that the new origin is available, you can check the URL in a browser: "https://{your custom CDN domain}/console".

  3. Purge your CDN cache. Your CDN contains cached AMS manifests with AMS segments URLs. And if some of the segments are not in the cache it will go to RMS which does not recognize such URLs. That's why please purge your CDN cache to ensure that all your VODs are correctly streamed.

    As a result, all video URLs will now be streamed from RMS. No need to update existing streaming links similar to Option 1 - it's done automatically.

Specify the CDN domain as a new RMS streaming endpoint hostname

You need to complete this step in any case: whether you selected Option 1 or Option 2.

  1. Go to RMS Console -> Manage -> Streaming Endpoints. RMS Console endpoints
  2. Remember the host name of your RMS streaming endpoint, as you will need to use it as the new origin for your CDN
  3. In the "Host Name" text box, specify your CDN domain name (for AMS, it's the AMS streaming endpoint hostname), and then click "Save" Change endpoint host name

Note

Without completing this step, your application may generate streaming links with the RMS origin domain instead of your CDN domain. The reason is that RMS API returns it to your application as a streaming endpoint hostname.

As a result, the  CDN domain will serve content using the RMS streaming domain as its origin. This transition won't require any additional training or redirects for your viewers. 

Verification and troubleshooting

Congratulations on completing the migration process! You successfully transferred the data, configurations, and streaming infrastructure from Azure Media Services (AMS) to Ravnur Media Services (RMS). Now, your existing storage, application connections, and media playback seamlessly integrate with RMS. All your video URLs are now streaming directly from RMS, resulting in a smooth performance for your viewers.

You can now initiate your Post-migration Release Procedure. Check this document for valuable recommendations to help you finalize your media service application migration to RMS.

If you require additional guidance, please contact Ravnur for help.