AWS Media Services

👍

This article attempts to simplify using AWS Media Services with Studio DRM.

However since AWS Media Services products evolve, we strongly recommend verifying the steps in this documentation with the documentation for each specific AWS service. A link to each service's documentation is listed in the following table.

When using AWS Media Services with Studio DRM, you must use several services to package your media, create a bucket, and create a job. Each of the required AWS services is listed in the following table.

In addition to the AWS service, you must set up an API gateway to use the SPEKE API.

Implementation

Configure Media Packaging

1. Log into AWS.
2. In the Console Home page search bar, type MediaPackage and click MediaPackage. The AWS Elemental MediaPackage page appears.

📘

You can also click Services > Media Services > MediaPackage.

3. Click Create a new channel. The Create channel page appears.
4. In the ID field, enter a channel identifier.
5. Click Create. The details of the newly created channel appear.
6. In the Endpoint section, click Add endpoints. The Add/edit endpoints page appears.
7. In the ID field, enter an endpoint identifier.
8. (Optional) Add a Description of the endpoint.
9. In the Manifest Name, type manifest.
10. In the Packager settings section from the Type dropdown menu, select the packager type:
       • Apple HLS: For use with FairPlay DRM
       • DASH-ISO: For use with Playready or Widevine DRM
    
    
11. In the Package encryption section, choose Encrypt content. The encryption settings appear.
12. In the Resource ID field, add a resource ID.
13. In the System IDs text box, type the appropriate DRM system identifiers:
       • 94ce86fb-07ff-4f43-adb8-93d2fa968ca2 (FairPlay DRM/Apple HLS)
       • 9a04f079-9840-4286-ab92-e65be0885f95 (PlayReady DRM/DASH ISO)
       • edef8ba9-79d6-4ace-a3c8-27dcd51d21ed (Widevine DRM DRM/DASH ISO)
    
    
14. In the URL field, enter the API gateway URL.
15. In the Role ARN field, enter an appropriate Amazon Resource Name.
16. Click Save.

📘

You can use the stream tester to test the endpoints URL.

Create a Bucket

1. In the Console Home page search bar, type S3 and click S3. The Amazon S3 page appears.

📘

You can also click Services > Storage > S3.

2. Click Create bucket. The Create bucket page appears.
3. In the General configuration section in the Bucket name field, enter a unique bucket name.
4. Click Create bucket. The bucket’s summary page appears.
5. In the Buckets section, click the name of the bucket.
6. Click Create folder.
7. In the Folder name field, enter a unique name.
8. Click Create folder. Remember the folder name. This will be required later in the setup process.
9. Duplicate the browser tab.

Create a Job

1. In the Amazon search bar of the new tab, type MediaConvert and click MediaConvert. The AWS Elemental MediaConvert page appears.

📘

You can also click Services > Media Services > MediaConvert.

2. Under Create a job, click Get started. The Create job page appears.
3. In the Input 1 section in the Input file URL field, enter the URL of the source clip.
4. In the side navigation under Output groups, click Add. The Add output group popup window appears.
5. Select an output group:
      • For FairPlay, select Apple HLS.
      • For PlayReady or Widevine, select DASH ISO.
   
   
6. Click Select. A page with the group settings appears.
7. Under Destination, click Browse. The Choose a location popup window appears.
8. From the S3 bucket dropdown menu, select the destination S3 bucket.
9. In the Location field, search for the S3 bucket folder. The folder should have a path similar to your-bucket/your-folder-name/.
10. Click Choose. The popup window closes.
11. In the Destination field, append manifest to the end of the destination.
12. From the Segment control dropdown menu, select Segmented files.
13. Add DRM and add an output to the output group. Only use one of the following instructions:
       • FairPlay
       • PlayReady
       • Widevine
    
    
14. In the main side navigation under Job settings, click AWS integration. The AWS integration settings appear in the main panel.
15. Under Service access, select Use an existing service role from the Service role control dropdown menu. The Service role field appears.
16. In the Service role field, choose the relevant IAM role.
17. Click Create.

Wait several minutes for the job to process. On the Jobs page, you can press the Refresh button to check the status of the job. Once the job is complete, a value appears in the Finish time column.

Test the Content

1. From Amazon S3, locate the bucket folder you created.
2. Right-click the folder.
3. Select Make public.
4. Click Make public.
5. Click the folder.
6. Copy the manifest file URL.
7. Paste the manifest file URL in the stream tester.

API Gateway

Import the API from Swagger

1. In the Amazon search bar of the new tab, type API Gateway and click API Gateway. The API Gateway page appears.

📘

You can also click Services > Networking & Content Delivery > API Gateway.

2. In the REST API section, click Import. A setup page appears.
3. Under Choose the protocol, select REST.
4. Under Create new API, select Import from Swagger or Open API 3.
5. Under Import from Swagger or Open API 3, paste the following JSON.

{
  "swagger": "2.0",
  "info": {
    "title": "speke proxy"
  },
  "basePath": "/speke",
  "schemes": [
    "https"
  ],
  "paths": {
    "/": {
      "post": {
        "produces": [
          "application/json"
        ],
        "parameters": [
          {
            "name": "API-KEY",
            "in": "header",
            "required": false,
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "200 response"
          }
        }
      }
    }
  }
}

6. Click Import.

API Gateway Setup

1. In the POST box, click Set up now.
2. For the Integration type, select HTTP.
3. Check Use HTTP Proxy integration.
4. Set the Endpoint URL to https://speke.vudrm.tech/{your-client-name}/speke.
5. Click Save. The Method Execution page appears.
6. Click Integration Request.
7. Expand the HTTP Headers section.
8. Click Add header. A row appears.
9. In the Name field, enter API-KEY.
10. In the Mapped from field, enter '{your-api-key}'. Be sure that the API key is surrounded by single quotes.
11. At the end of the row, click the checkmark to save the header.
12. At the top of the page, click Actions > Deploy API. The Deploy API popup window appears.
13. From the Deployment stage dropdown menu, select [New Stage].
14. In the Stage name field, enter an appropriate name.
15. Click Deploy. The Stage Editor page appears for the stage that has been created.

At the top of the Stage Editor page, your Invoke URL is listed. The Invoke URL can be used by other AWS services to make requests to JW Player's SPEKE API.

Stream Tester

Validate your Studio DRM-protected stream in web environments using the JWP Stream Tester.