AWS Elemental Integration

Overview

DoveRunner KMS supports SPEKE (Secure Packager and Encoder Key Exchange), which issues the keys required for Multi DRM packaging in AWS Elemental MediaConvert and MediaPackage.

You can easiliy integrate DoveRunner Multi-DRM with AWS Elemental Media Services by setting DoveRunner KMS URL to DRM encryption setting of MediaConvert or MediaPackage.

MediaConvert integration

MediaConvert Tutorial Video

This video is a tutorial for enabling DRM encryption on VOD content packaging with AWS Elemental MediaConvert.

Create MediaConvert IAM role

Please refer to IAM Settings AWS Guide Document and proceed as follows.

1. In the AWS Console, select the IAM service.

2. Click the Roles tab and select create role.

3. Select MediaConvert and click the Next: permission button.

4. Confirm the S3 Access and APIGateway access permissions and click Next: Review button.

   

5. Set RoleName to MediaConvert-role and click the create role button.

   

Create MediaConvert job and set IAM role

1. In the AWS Console, select the MediaConvert service.
2. Click the create job button on the Jobs tab to start job creation.
3. Select the MediaConvert-role created in the previous step in the IAM role setting section of the Job settings screen.

   

Set MediaConvert Input

1. In the Input field, enter the content path to be packaged in s3.

   

Set MediaConvert Output groups

1. Add the ouptput to the output groups by pressing the Add button. (DASH ISO for PlayReady and Widevine, Apple HLS for FairPlay and NCG-HLS)

   

2. In Custom group name, enter a name that is easy for you to identify.

3. In the Destination field, type the path on s3 that contains the package-completed file.

   

4. Select the DRM encryption option, and then enter the Resource ID, System ID, and URL.

   • Resource ID: It is a value corresponding to the content ID (CID) in the integration specification in DRM Token Guide.
   • System ID: The DRM-specific system id value specified in Dash System ID. You need to set PlayReady and Widevine ID for DASH output(as shown below). Refer to the next sections for HLS output configuration.
     • PlayReady: 9a04f079-9840-4286-ab92-e65be0885f95
     • Widevine: edef8ba9-79d6-4ace-a3c8-27dcd51d21ed
   • Key Provider URL: Enter the following KMS URL. The KMS Token at the end of the URL is an API authentication token that is generated when you sign up DoveRunner service, and can be found on the DoveRunner Console site.
     • KMS URL format: https://kms.pallycon.com/v1/cpix/getKey?enc-token=YOUR-KMS-TOKEN
   • Certificate ARN: leave it blank
   • Play device compatibility: CENC v1

     

5. Set the Outputs and click the Create button.

   • In case of widevine, it is mandatory to create the video and audio track separately because there are clients that can not play if you do not divide video and audio tracks into output. (click ‘add output’ button to add track)

     

     

6. Make public or set permission on the S3 storage to play the generated file stored on it.

HLS configuration for FairPlay DRM

If you want to support Apple devices as well as others, you need to create both ‘DASH ISO’ and ‘Apple HLS’ output groups for a single input. To apply FairPlay DRM to Apple HLS output group, set the encryption options as below.

• Encryption method: Sample AES
• Key provider type: SPEKE
• Resource ID: the same content ID as DASH output
• System ID: DRM system ID for FairPlay (94ce86fb-07ff-4f43-adb8-93d2fa968ca2)
• Key provider URL: same as DASH output (DoveRunner KMS URL with enc token)
• the other items: leave them as default

HLS configuration for NCG-HLS

You can also use the ‘Apple HLS’ output group to package HLS content with our proprietary NCG DRM instead of FairPlay DRM. For the NCG-HLS packaging, create an Apple HLS output group and set the DRM encryption options as shown below.

• Encryption method: AES128
• Key provider type: SPEKE
• Resource ID: Enter the same content ID as the DASH output group
• System ID: NCG HLS system ID (81376844-f976-481e-a84e-cc25d39b0b33)
• Key Provider URL: DoveRunner KMS URL same as DASH output group
• Other items: leave them as default

Notes on CMAF Packaging

In addition to DASH-ISO and Apple HLS, CMAF(Common Media Application Format) type output can also be generated through SPEKE integration.

To ensure that CMAF content is supported in as many client environments as possible, including Apple devices, the encryption method in the DRM encryption setting should be set to AES-CBC subsample. Also, the KMS URL you enter in the Key provider URL field must use the URL below that supports CBCS encryption instead of the default SPEKE v1 URL.

https://kms.pallycon.com/v1/cpix/cbcs/getKey?enc-token=YOUR-KMS-TOKEN

Multi-key Packaging via SPEKE v2

MediaConvert service supports both SPEKE v1, which encrypts all output tracks including audio with one key (single-key packaging), and the SPEKE API v2, which supports multi-key packaging.

Multi-key packaging is a function that encrypts the output video and audio tracks with different keys when DRM encryption is applied, and is necessary to apply hardware DRM such as PlayReady SL3000 or Widevine L1.

If you select SPEKE Version 2.0 in the Apple HLS, DASH-ISO, or CMAF output group settings of the MediaConvert job, you can apply multi-key packaging through the following options:

You need to input the SPEKE v2 KMS URL when you choose the SPEKE v2 integration. You can find your own KMS Token value on DoveRunner Console (Multi-DRM > DRM Setting > Multi-DRM Settings).

SPEKE v2 KMS URL: https://kms.pallycon.com/v2/cpix/getKey?enc-token=YOUR-KMS-TOKEN

MediaPackage integration

AWS MediaPackage service supports real-time packaging and encryption for live or VOD content.

MediaPackage Tutorial Video

This video is a tutorial for enabling DRM encryption on live stream packaging with AWS Elemental MediaPackage.

Create MediaPackage IAM role

1. Create the same as MediaConvert IAM Authorization, and create only Role Name with SPEKEAccess.

2. On the Roles tab, select SPEKEAccess role and click the Edit trust relationship button on the Trust relationships tab.

   

3. Change the value of Principal.Service to mediapackage.amazonaws.com and click the Update button.

   

Create MediaPackage Channel

1. In the AWS Console, select the MediaPackage service.

2. Create a channel.

   

3. At the endpoints, press the Add button to set the endpoint.

4. Set the endpoint name, packager settings, etc. according to the desired content specification.

5. Configure Encryption and Outputs in the same way as MediaConvert Output groups setting no. 4.

6. Enter the SPEKEAccess Role created in Role ARN.

7. Click the Save button.

   

Multi-key Packaging via SPEKE v2

The MediaPackage service supports multi-key packaging based on SPEKE API v2 for live DASH or CMAF output. Multi-key packaging is a function that encrypts the output video and audio tracks with different keys when DRM encryption is applied, and is necessary to apply hardware DRM such as PlayReady SL3000 or Widevine L1.

If you select SPEKE Version 2.0 in the DASH or CMAF Endpoint settings of the MediaPackage live channel, you can apply multi-key packaging through the following options:

You need to input the SPEKE v2 KMS URL when you choose the SPEKE v2 integration. You can find your own KMS Token value on DoveRunner Console (Multi-DRM > DRM Setting > Multi-DRM Settings).

SPEKE v2 KMS URL: https://kms.pallycon.com/v2/cpix/getKey?enc-token=YOUR-KMS-TOKEN

MediaPackage Live v2

MediaPackage Live v2 is a new version of the AWS MediaPackage service released in May 2023. This version offers improved features and UI over v1, especially support for low-latency HLS (LL-HLS), which is ideal for real-time services such as live sporting events.

Please note the following when integrating AWS MediaPackage Live v2 with DoveRunner Multi-DRM service.

Container Types

In the MediaPackage Live v1 channel, you could select a packaging type for the endpoint for output, such as DASH-ISO, Apple HLS, Smooth Streaming, or CMAF.

Instead of a packaging type, endpoints in the MediaPackage Live v2 service channel are required to select the following container types.

• TS: Applies MPEG-TS container. Supports AES-128 (clear-key encryption) or Sample AES (FairPlay DRM).
• CMAF: Applies fMP4 container. Support for CENC (PlayReady, Widevine) or CBCS (PlayReady, Widevine, FairPlay).

For streaming protocols that fall under the earlier packaging type option, v2 can generate output in the form of DASH, HLS or LL-HLS protocols.

Key rotation configuration

As with MediaPackage Live v1, when applying DRM encryption to endpoints on a v2 channel, you can set the key rotation period in the Additional configuration section. (Key rotation applies when setting a period greater than 0)

Please note the following when you enable key rotation:

• You need to add a key rotation parameter to the key server URL.
  • Add key-rotation=true parameter to the DoveRunner KMS SPEKE v2 URL that you enter in Key server URL of Encryption option (enter two parameters: enc-token and key-rotation).
  • Example: https://kms.pallycon.com/v2/cpix/getKey?key-rotation=true&enc-token=YOUR-KMS-TOKEN

• Enable key rotation in token policy when requesting DRM licenses
  • When generating a license token for content with key rotation, the key_rotation item in the token JSON specification must be set to true.
• Enable key rotation for DoveRunner Multi-DRM service account
  • In order to issue DRM licenses for content with key rotation, the key rotation right must be activated in the DoveRunner service account of the site. (You can check it on the DoveRunner Console > Multi DRM > DRM Settings screen.)
  • Please contact Helpdesk or our business team to request key rotation activation and inquire about additional charges.