AMS API concepts

Introduction to the existing API structure from AMS to help existing customers migrate their workflows

To support the transition and to streamline our initial launch we have focused on replicating the functionality found in the Azure Media Services v3 API guide.

If you use AMSv2 APIs, a guide is available to support you in any major changes: Migrating from AMSv2 to AMSv3.

To help you navigate this transition we’ve created a simple guide to AMS API concepts, data model and usage. This should help you map to our implementation in the migration guide found later in this documentation.

Let’s explore the AMS API

The AMS API is conceptually broken into four parts: Inputs, Assets, Streaming Locators, and Streaming Endpoints.

4 Building Blocks of AMS APIs

4 Building Blocks of AMS APIs

  • Inputs are ways of getting content into the system.
  • Assets are where content is stored and are decoupled from inputs.
  • Streaming Locators connect DRM and filters to the asset for a dynamic packager (JITP) to process.
  • Streaming Endpoint defines a domain name for content and provides an option for configuring frontdoor and CDN for the user.

AMS Data Model

Everything within AMS revolves around an Asset. Inputs, either file-based or live are treated as assets on the output side.

AMS Data Model

AMS Data Model

Assets then have policies attached to them via a Streaming Locator, which can then be bound to a Streaming Endpoint for delivery.

Let’s take a look at each of these in turn.