🚀 Azure Media Services Explorer for Ravnur Media Services is now available! 🚀
The tool that you're familiar with now works with Ravnur Media Services, and of course, it does because RMS is a mirror of AMS. Just connect the AMSE to RMS and you can do everything with RMS that you can do with AMS. Download the RMS version of AMSE here: AMSE for Ravnur Media Services
Note
This is a console application to help you test the Ravnur Media Services API. It is not the repo for Ravnur Media Services. Contact Ravnur at [email protected] to deploy the RMS managed application from the Azure Marketplace, or to gain access to Ravnur’s test environment
Ravnur Media Services (RMS) and its API have been engineered for Azure Media Services (AMS) customers seeking to transition away from AMS without significant modifications to their existing application code. The demo application in this repository will help you understand how RMS can seamlessly replace AMS with minimal changes to your existing code.
We’ve created this console application to give you a quick and simple way to test and explore the Ravnur Media Services API. There are two versions of the Dotnet demo application and a separate one for Node.js.
Please select the dotnet demo version that corresponds to the way you use the Azure Media Services (AMS) v3 API:
- If you're using the Azure.ResourceManager.Media SDK, please use this application: sdk-azure-resource-manager-demo.
- For those using the Microsoft.Azure.Management.Media SDK, please use this application: sdk-ms-azure-management-demo.
After selecting one of the links above, you’ll find instructions on installing and running the demo application and SDK-specific code samples that highlight the code changes required for authentication and redirecting to RMS.
Introducing a Node.js demo app package designed to help you test Ravnur Media Services. This package contains code samples and instructions for updating your SDK to connect and interact with RMS.
For setup and detailed usage instructions, visit the Node.js Demo App directory.
To run the RMS demo application, you will need:
✅ A deployed instance of RMS. You can deploy one from the Azure marketplace or use a Ravnur-hosted POC environment. Contact Ravnur to deploy the RMS managed application from the Azure Marketplace, or to gain access to Ravnur’s test environment.
✅ The corresponding RMS API endpoint. You will get this after deploying RMS from the marketplace, or from Ravnur support if you use Ravnur’s test environment.
✅ The RMS API secret key. You will get this after deploying RMS from the marketplace, or from Ravnur support if you use Ravnur’s test environment.
✅ Dotnet installed for dotnet 6 Azure apps sdk-azure-resource-manager-demo / sdk-ms-azure-management-demo (both SDK and runtime), or Node.JS installed for node-js-demo.
✅ Azure CLI installed (only if you want to run the Azure apps sdk-azure-resource-manager-demo / sdk-ms-azure-management-demo using an existing AMS account to compare the output with RMS. Azure CLI is not required by RMS).
Azure CLI is not required for node-js-demo.
Any demo application, whether it is dotnet or Node.js, will connect to the RMS API and allow you to upload, encode, and stream a video. With each subsequent release of RMS, you will be able to test more functionality. Please see the product roadmap below for upcoming features and availability dates.
Specifically, the RMS API will enable you to:
- Add a custom transform
- Optionally add AES-128 encryption
- Create an input asset (if the input is a local file)
- Upload video/audio to the input asset (if input is a local file)
- Create output asset
- Initiate encoding job
- Await completion of the encoding job
- Create a streaming locator
- Retrieve streaming and download URLs, and the AES-128 token if used in the transform
- Monitor and act on all Event Grid job-related event types supported by Azure Media Services
- Use the filter or order parameter to find the objects you're interested in
On the respective pages for the SDK version of the demo application, you can see a screenshot of the API responses.
Note
TEST AND COMPARE RMS WITH AMS
You can also use your Azure apps sdk-azure-resource-manager-demo / sdk-ms-azure-management-demo to connect to your AMS account to compare the responses. Because the RMS and AMS API are the same, all you need to do to connect it to AMS and upload a file is change RMS to AMS in the command:
- To test RMS use:
dotnet run rms <your file> - To test AMS use:
dotnet run ams <your file>.
This is also found in Step 8 of the respective SDK demo app instructions.
Such an option is not available for node-js-demo.
Ravnur Media Services (RMS) replaces the most recent version of the Azure Media Services v3 API. This means AMS customers can continue to use their existing Azure SDK without making extensive code alterations. Because the RMS API is a mirror of the AMS v3 API, you can refer to the existing Microsoft Azure Media Services (v3) documentation for the comprehensive REST API description and documentation. With RMS, you do not need to reencode your content, and you can use your existing storage account because the output of RMS is identical to AMS.
Please refer to the RMS roadmap for guidance on which endpoints have already been implemented and which endpoints are planned in coming releases. The initial release implemented the core AMS functionality for VOD encoding and streaming. The current version includes additional functionality, such as support for custom transforms, filtering, CDN tokenization, AES-128 encryption, content key policies, and streaming policies.
RMS is offered as a managed application available from the Azure Marketplace. This means that you can deploy it in your Azure tenant into a dedicated resource group. Ravnur manages the Azure services and the RMS application for you. During the deployment you can configure the regions and connections to existing Azure storage accounts, or specify new accounts. The RMS marketplace package is in the process of being certified for publication in the Azure Marketplace. However, in the meanwhile we can quickly create a private offer that will allow you to access and deploy RMS. Deployment instructions for RMS will be published in the Azure Marketplace once the marketplace package clears certification. In the interim, you may reach out to us, and we'll grant you access to a shared demo RMS instance.
Ravnur includes a Console UI as part of the RMS management application. It allows you to perform maintenance task including migration of data from existing AMS account. Migration job copies the asset metadata (not content - that stays put), content key policies, transforms, and streaming locators from AMS to RMS so that your assets are streamable within minutes. We have a complete migration guide and AMS metadata migration guide as a part of it.
| Feature | State | Comments |
|---|---|---|
| Assets | Released | |
| Jobs | Released | Supported job inputs: JobInputAsset, JobInputHttp. Does not support processing multiple media files in one job |
| Streaming Locators | Released | |
| Custom Transforms | Released | |
| Event Grid support | Released | Supported all job-related event types. More details about Event Grid support can be found on this page |
| Automatic migration of AMS assets/locators to RMS | Released | Migration instructions can be found on this page |
| Custom Streaming Policy | Released | |
| AES stream encoding | Released | HLS Proxy service for RMS is here |
| DRM stream encoding | Released | DRM instructions are here |
| Smooth streaming | In development | This is a lower priority feature due to limited customer usage |
| Custom Streaming Endpoints | Released | There is only one predefined streaming endpoint available. Its domain matches the domain of the RMS API endpoint. However, you can create a custom host domain for the streaming endpoint |
| Filtering, ordering, and paging | Released | RMS fully supports OData query filtering and ordering options, learn more in the official documentation |
| Account filters | Released | RMS supports the following account filters: "property": "Name", "property": "Type", "property": "Bitrate", trimming:Â "startTimestamp" "endTimestamp". |
-
HOW CLOSELY DOES YOUR API'S ARCHITECTURE MIRROR THAT OF AMS IN TERMS OF REQUEST/RESPONSE PATTERNS, URL STRUCTURES, AND DATA MODELS? The RMS API structure is a 100% mirror of the AMS API structure. The endpoints delivered so far (January 2024) are Assets, Jobs, Streaming Locators, Streaming Endpoints, Transforms and Content Key Policies.
-
DO I NEED TO RE-ENCODE ALL MY VIDEOS? No, you do not need to re-encode any videos. RMS can work with existing AMS assets without any issues.
-
DO I NEED TO CHANGE THE STREAMING URL OR STREAMING LOCATOR? RMS can use the existing streaming locator. The streaming URL will need to be changed, but you need to change only the host. For example, if you have a streaming URL like this: https://ams1.streaming.media.azure.net/5197ca71-3edc-42b0-adff-12570b48b4e4/video_3500000.ism/manifest(format=m3u8-cmaf) you would need to change ams1.streaming.media.azure.net to the RMS host or to your CDN domain which uses RMS as origin. Both RMS host can be customized to use your own domain.
-
DO I NEED TO CHANGE THE STREAMING URL OR STREAMING LOCATOR IF I’M USING A CDN? Yes, you need to change streaming URLs because Microsoft will not support the streaming.media.azure.net AMS domains after the AMS retirement. That's why you need to create your own custom domain and map it to your CDN. You can do it independently even now because it is not a part of the RMS infrastructure. That's why we suggest you to create your own custom domain and update your streaming links in advance. You can create a separate CDN endpoint or map your custom domain name to your existing CDN endpoint, choose what is better for you. In case of reusing an existing CDN endpoint then you need to change its origin, so that it uses the RMS streaming endpoint hostname instead of AMS. It is explained in our migration guide.
-
DO I NEED TO MAKE CODE CHANGES IN MY APPLICATION TO USE THE RMS API? Yes, but just a little bit. If you are using the Microsoft Azure SDK, you just need to tell the SDK to connect to RMS instead of AMS. Code samples can be found on the pages for the respective SDK versions of the demo app (links above). If you have your own implementation, you need to change only the host from AMS to RMS.
-
WHAT STREAMING PROTOCOLS DO YOU SUPPORT? RMS supports HLS and MPEG-DASH.
-
WHAT ENCODING FORMATS AND CODECS DO YOU SUPPORT? RMS encoding supports a wide range of codecs and containers and can accept the same codecs and containers as AMS. If you have a need to encode an unsupported codec/container, we’ll add it. The standard output asset is h.264/AAC in an mp4 container.
-
CAN I USE CUSTOM ENCODING PRESETS SIMILAR TO WHAT I HAD IN AMS? Yes, custom transforms are supported.
-
HOW WOULD YOU MIGRATE THE STREAMING FUNCTIONALITY FOR MY CURRENT AMS ASSETS? The overall migration process consists of replacing the AMS connection with RMS in your application code, registering your storage accounts in RMS, and triggering the AMS migration job in the RMS Console. If you use Event Grid subscriptions or CDN you have to configure them as well. All these are described in detail in our complete migration guide and AMS metadata migration guide as a part of it.
-
DO YOU PROVIDE ANY MIGRATION TOOLS FOR TRANSITIONING FROM AMS TO YOUR PLATFORM? Yes, RMS has a special console UI that allows you to perform different maintenance actions including migration of your existing AMS account. It allows you to register your AMS storage account and trigger the migration process which will copy your AMS metadata to RMS: transforms, streaming policies, content key policies, assets, and locators. You can find instructions on how to do it here.
-
WHERE IS THE MEDIA CONTENT STORED, AND CAN IT INTEGRATE SEAMLESSLY WITH MY CURRENT STORAGE ACCOUNT? All media content is stored in your Azure Storage Account, following the existing AMS structure. No data copying is required. To register your existing AMS storage in RMS use these instructions. Note that the RMS instance should be deployed to the same region as your existing AMS storage account.
-
HOW DOES YOUR PLATFORM HANDLE API AUTHENTICATION? IS IT SIMILAR TO THE WAY AMS HANDLES IT? We use JWT bearer token authentication, like AMS. RMS will not require Azure Active Directory service principal or Managed Identity.
-
IS THERE A SANDBOX OR TESTING ENVIRONMENT WHERE I CAN VERIFY THE COMPATIBILITY BEFORE GOING LIVE? Yes. Ravnur can set up a testing environment for you where you can run a POC. We can do this in your Azure tenant or ours.
-
HOW DOES YOUR PLATFORM SCALE WITH INCREASED DEMAND? The RMS application is engineered to scale both streaming and encoding to meet the demands of your users and viewers. The encoding management application monitors queues and jobs to ensure that jobs are efficiently allocated, and provisions encoders as needed. Streaming demand is managed by a combination of CDN and auto-scaling triggered by egress bandwidth and CPU monitoring
-
HOW IS PRICING STRUCTURED FOR ENCODING, STREAMING, STORAGE, AND ANY ADDITIONAL FEATURES? The pricing for RMS is comprised of two components. There is a fixed cost for support and updates, and there is a variable cost for Azure services. The RMS application is deployed to your Azure tenant from the Azure Marketplace as a managed application. This means that Ravnur manages the RMS application and the Azure services that provision the application. Fixed cost. Support of the application and Azure environment, and regular upgrades for the RMS encoding and streaming solution begins at $499/month. When subscribed to from the Azure Marketplace, this can be paid for from your Azure commitment, or added to your Azure monthly invoice as a marketplace charge. Variable cost. Because RMS runs in your Azure tenant, all encoding, streaming, and storage costs accrue to your Azure expense. RMS uses VMs, Container Apps and Azure SQL (serverless), along with Azure Storage Queues and Tables. In RMS’s idle state, the encoding VMs are deallocated and not billing. The streaming servers running in Container Apps can be scaled to zero to minimize Azure expenses.
-
ARE THERE ANY ADDITIONAL OR HIDDEN COSTS I SHOULD BE AWARE OF? If you use DRM (Widevine, PlayReady, FairPlay), you will need to pay for DRM licenses. We partner with EZDRM for DRM licenses.
-
DO YOU SUPPORT ENCRYPTION AND DRM? We support AES-128 encryption natively, and we use EZDRM for multi-DRM support.
Ravnur Media Services (RMS) is the replacement for Azure Media Services (AMS), which Microsoft is retiring on June 30, 2024. The similarity in naming is intentional; The RMS API is a mirror of the AMS API and migrating from AMS to RMS requires minimal code changes to the existing Azure SDK used with the AMS API (i.e. Azure.ResourceManager.Media SDK or the Microsoft.Azure.Management.Media SDK).
The diagram below is the reference architecture for Ravnur Media Services (RMS). The Azure Services that provision RMS are deployed from the Azure Marketplace to a dedicated resource group in the customer’s Azure subscription.
The architecture of RMS is similar to AMS, and it provides scalability for encoding and streaming demands. Azure Front Door sits in front of the RMS API. The RMS API endpoints terminate in Azure Kubernetes Service. Streaming locators and asset metadata are stored in Azure SQL databases (primary and failover). Encoding jobs are processed by Azure VMs; the number and size can be configured during deployment. Output content assets (e.g. video files, thumbnails, manifest files, etc.) are stored in containers in Azure blob storage, and the account can be specified during deployment (e.g. connect an existing storage account or a new storage account). Streaming servers run in AKS and scale based on real-time monitoring. The connection to the Content Delivery Network is not shown on the diagram.
| Azure Service | Purpose |
|---|---|
| Azure Front Door | Manages and optimizes API traffic with global routing. Acts as a layer-7 load balancer that distributes traffic to corresponding services. Provides SSL offloading, and WAF protects services |
| Azure Kubernetes Service environment | Provides the runtime environment for the services |
| Application Insights | Provides telemetry and service performance monitoring |
| Managed Identity | Grants permissions to resources securely without storing credentials in code. |
| DNS Zones | Maps domain names to IP addresses. |
| Key Vault | Safely stores and manages secrets, keys, and certificates needed for RMS |
| Log Analytics workspace | Aggregates and analyzes log data from Application Insights, App Service event logs, Container Apps, and various Azure services. |
| Network security group | Filters and controls inbound and outbound traffic. This is created by default when a VM is created. |
| Azure SQL DB | Microsoft SQL DB stores assets, locators, and metadata. Configured with failover DB. |
| Azure SQL Server | Managed service provisioning of the SQL Server for the SQL DBs. |
| Azure Storage Account | (Optional - you can use your existing account outside of the managed RG) This storage account stores video originals, assets, sub-resources, etc. |
| Azure Storage Account | This storage account is used for infrastructure deployment. |
| Virtual Network | Provides an isolated and secure environment to run Azure resources. This Vnet is deployed by default and is needed for container apps, VMs, and DB. |
| Azure Service Bus | Message broker |
| Event Grid | Client can subscribe to the RMS events |
| Container Instances | Used for system upgrade |
Ravnur is an experienced video content management and live streaming solution provider that has been serving government customers such as the Department of Homeland Security, Department of Defense, and the Department of Commerce, as well as global commercial clients like Microsoft, Xerox, and Warner Brothers for over a decade. Our flagship solution, the Ravnur Media Platform (RMP), delivers scalable and reliable live and on-demand video workflows of high quality to any device. RMP allows customers to start fast with easy-to-use live streaming and video content management processes, and its rich functionality enables customers to grow their use of video, audio, and live content in other workflows as the need arises.
Our unique platform architecture allows RMP to function as a private multi-tenant SaaS solution for organizations that have multiple internal clients and require the security and privacy that a private SaaS solution offers. RMP is hosted in the customer’s FedRAMP-certified Microsoft Azure Cloud, in either the commercial cloud or the government cloud, based on the customer's preference. Ravnur's solutions prioritize data privacy and security. Unlike other cloud solutions, we ensure that each customer's data and content are segregated and protected through separate databases and storage accounts, even when running as a private SaaS solution in the customer’s Azure tenant.
We believe in simplifying the procurement process for government organizations. That's why we offer Ravnur solutions in the Microsoft Azure Marketplace. Customers can purchase and use our solutions as Azure services from their existing Azure monetary commitments. Standard procurement is also offered.
We're proud to be a Veteran Owned Small Business, and we look forward to helping Azure Media Services customers migrate from AMS to RMS.