Streaming Locators

Streaming locators are used to bind assets to streaming policies.

Streaming Locators provide an entry point to access the files contained in an Asset and allow you to attach policies for DRM, access and manifest re-writes.

πŸ“˜

To make video Assets available to clients for playback, you have to create a Streaming Locator and then build streaming URLs once you have a Streaming Endpoint defined.

The process of creating a Streaming Locator is called publishing. By default, the Streaming Locator is valid immediately after you make the API calls, and lasts until it is deleted, unless you configure the optional start and end times.

When creating a Streaming Locator, you must specify an Asset name and a Streaming Policy name. The Streaming Policy can optionally point to a Content Key for encryption.

Streaming Locators can have a many to one relationship with a Streaming Policy, such that different Locators can provide different start times and connection types to different clients while all using the same permission and duration settings.

🚧

Because of a shared access policy restriction set by Azure storage services, you cannot have more than 5 unique Streaming Locators associated with a given Asset at one time.

Streaming Policies

Streaming Policies enable you to define streaming protocols and encryption options for your Streaming Locators. As with Azure Media Services v3, you get some predefined Streaming Policies out of the gate, so that you can use them directly for trial or production.

Examples of Streaming Policies:

  • Predefined_DownloadOnly: For allowing downloading only.
  • Predefined_ClearStreamingOnly: For allowing clear streaming only.
  • Predefined_DownloadAndClearStreaming: For allowing both downloading and clear streaming.
  • Predefined_ClearKey: For allowing HLS/DASH encrypted with envelopeEncryption with Media Services issuing the content key.
  • Predefined_MultiDrmCencStreaming: For allowing streaming with DASH/Smooth encrypted with commonEncryptionCenc with Media Services issuing the PlayReady and Widevine licenses.
  • Predefined_MultiDrmStreaming: For allowing streaming with DASH/Smooth encrypted with commonEncryptionCenc with Media Services issuing the PlayReady and Widevine licenses, or for allowing streaming with HLS encrypted with commonEncryptionCbcs with Media Services issuing the FairPlay license.

You will also be able to create your own streaming policies if these don’t meet your needs.

Content Keys

Both AES128 and DRM (Widevine, FairPlay, Playready) are supported on the platform for both live and file-based streaming.

The Content Key Policy is used to configure how the content key (secure access to your Assets) is delivered to end clients. You need to set the requirements (restrictions) on the Content Key Policy that must be met in order for keys with the specified configuration to be delivered to clients.

πŸ“˜

The content key policy is not needed for clear streaming or downloading.

In most cases, the content key policy is associated with the Streaming Locator. When creating a custom streaming policy for advanced scenarios, you can specify the content key policy inside of a Streaming Policy.

Streaming Endpoints

A Streaming Endpoint must exist to bind your streaming locator to and enable you to scale your output based on viewer concurrency.


What’s Next