Skip to content
This repository has been archived by the owner on Aug 12, 2022. It is now read-only.

Latest commit

 

History

History
174 lines (89 loc) · 8.8 KB

MediaTailorModule.md

File metadata and controls

174 lines (89 loc) · 8.8 KB
Raw

Monetizing an Encrypted Live Stream with AWS Elemental MediaTailor

This module will take you through creating a Mediatailor configuration using previously created AWS Elemental MediaLive and AWS Elemental MediaPackage channels. The MediaPackage channel will have been encrypted using a SPEKE reference server.

Prerequisites

This module relies on the completion of the following previous modules:

You will also need an Ad decision server (ADS). For this workshop, we will use a previously deployed simple, serverless mock ADS.

Implementation Instructions

1. Create an AWS Elemental MediaTailor Configuration

Step-by-step instructions

  1. From the AWS Management Console, choose Services then select AWS Elemental MediaTailor.

  2. Click on Create configuration.

  3. Enter MyTestConfig for the Configuration Name.

  4. For the Video content source, enter the encrypted MediaPackage HLS Endpoint URL, but without the manifest filename .

    If your MediaPackage endpoint is:

    https://547f72e6652371c3.mediapackage.us-west-2.amazonaws.com/out/v1/85ae554d000d48cab55aab1ae3df9071/index.m3u8

    Then your content source is:

    https://547f72e6652371c3.mediapackage.us-west-2.amazonaws.com/out/v1/85ae554d000d48cab55aab1ae3df9071

  5. Enter https://d2v7jbplksd24.cloudfront.net/Dev/MyADS for the Ad decision server.

  6. Expand the Additional configuration section. Enter https://d2qohgpffhaffh.cloudfront.net/MediaTailor/AWSE_Logo_15sec.mp4 for the Slate ad.

    alt

  7. Click Create Configuration.

  8. Click on MyTestConfig. Under Playback endpoints, note down the HLS playback prefix as you'll need it in the next section.

2. Test MediaTailor Playback

  1. Construct the playback URL that you will need to play back your video. This will consist of the HLS playback prefix (eg. https://f445cfa805184f3e8d86dc2ac1137efa.mediatailor.us-west-2.amazonaws.com/v1/master/cf6421621b389b384c1fd22e51603ee95db76ae0/MyTestConfig/) concatenated with the manifest filename of your MediaPackage playback endpoint (eg. index.m3u8)

    Sample full playback URL: https://f445cfa805184f3e8d86dc2ac1137efa.mediatailor.us-west-2.amazonaws.com/v1/master/cf6421621b389b384c1fd22e51603ee95db76ae0/MyTestConfig/index.m3u8

  2. On a browser, navigate to VideoJS's HLS demo player page.

  3. In the Video URL testbox, enter the playback URL constructed above and hit Load. If your player doesn't start automatically, hit the Play button. You should see the main content of your video play for the first 60 seconds, followed by ads for 45 seconds, and then back to video content. Note: You may not see ads the first time you play back if ads are not ready and are still being transcoded.

    alt

CHECKPOINT! Make sure that playback is working before proceeding to the next section. Integrating with CloudFront will only work if initial playback is successful.

3. Integrate with Amazon CloudFront

Step-by-step instructions

3a. Add Origins to the CloudFront Distribution

  1. From the AWS Management Console, choose Services then select CloudFront.

  2. Select the distribution created by the template ran at the beginning of the workshop.

  3. Click on the Origins tab, and click on the Create Origin button.

  4. Enter MediaTailor's hostname for the Origin Domain Name. This will come from the HLS playback prefix of MediaTailor (e.g. f445cfa805184f3e8d86dc2ac1137efa.mediatailor.us-west-2.amazonaws.com)

  5. Leave the Origin Path blank.

  6. Update the Origin ID to MediaTailor.

  7. Update the Origin Protocol Policy to HTTPS.

  8. Click Create.

  9. Go back to the Origins tab, and click on the Create Origin button.

  10. Enter MediaTailor's ad server hostname for the Origin Domain Name. Since we're in us-west-2, this will be: ads.mediatailor.us-west-2.amazonaws.com

  11. Leave the Origin Path blank.

  12. Update the Origin ID to MediaTailor-Ads.

  13. Update the Origin Protocol Policy to HTTPS.

  14. Click on Create.

    alt

3b. Add Cache Behaviors to Your Distribution

  1. Click on the Behaviors tab and click on the Create Behavior button.

  2. Select the Default behavior, and click on the Edit button.

  3. Update the Origin and select the MediaTailor-Ads origin.

  4. Set Cache Based on Selected Request Headers to None (Improves caching).

  5. Click on Yes, Edit.

  6. Click the Create button to add another cache behavior.

  7. Enter /v1/* for the Path Pattern.

  8. Under Origin, select the MediaTailor origin.

  9. For Query String Forwarding and Caching, select Forward all, cache based on all.

  10. Click on Create.

  11. Click the Create button to add another cache behavior.

  12. Enter /out/v1/* for the Path Pattern.

  13. Under Origin, select the mediapackage origin.

  14. For Query String Forwarding and Caching, select Forward all, cache based on all.

  15. Click on Create.

  16. Under the Behaviors tab, double-check the precedence of the caching behavior as this matters. Your primary precedence should be the MediaTailor origin (precedence 0), followed by the MediaPackage origin (precedence 1), and lastly by the ads origin (which is at Precedence 2 and is the Default). If this is not the precedence reflected, select one of the Behaviors and Change Precedence by clicking on either the Move Up or Move Down button, to make the adjustment.

    NOTE: When you make changes to the CloudFront distribution, it will go into In Progress state. Once it's back to the Deployed state, your changes will have taken effect.

    alt

Update MediaTailor Configuration with CloudFront Details

  1. From the AWS Management Console, choose Services then select AWS Elemental MediaTailor.

  2. Click on the Configuration (MyTestConfig) you created in section 1 and hit the Edit button.

  3. For the CDN content segment prefix, construct your URL by putting together the protocol(https), the CloudFront Domain Name, and the path of the MediaPackage endpoint URL. For example: https://d32ftvdskdjq4u.cloudfront.net/out/v1/85ae554d000d48cab55aab1ae3df9071

  4. For the CDN ad segment prefix, construct your URL by putting together the protocol, and the CloudFront Domain Name. For example: https://d32ftvdskdjq4u.cloudfront.net

  5. Click Save.

    alt

Test MediaTailor Playback with CloudFront

  1. Once your CloudFront distribution is in the Deployed status, and Enabled state, try playing back your stream using the same demo player. Take your playback URL from Section 2, Step 2 and replace the MediaTailor hostname with the CloudFront Domain Name that was assigned to your distribution.

    For example, if your MediaTailor playback URL is: https://f445cfa805184f3e8d86dc2ac1137efa.mediatailor.us-west-2.amazonaws.com/v1/master/cf6421621b389b384c1fd22e51603ee95db76ae0/MyTestConfig/index.m3u8

    then your CloudFront playback URL is: https://d32ftvdskdjq4u.cloudfront.net/v1/master/cf6421621b389b384c1fd22e51603ee95db76ae0/MyTestConfig/index.m3u8

  2. Video should play back as before the CloudFront integration. You should see the main content of your video play for the first 60 seconds, followed by ads for 45 seconds, and then back to video content.

Completion

Congratulations! You've successfully integrated your streaming video with AWS Elemental MediaTailor. In addition, you have successfully integrated MediaTailor with Amazon CloudFront.

Cloud Resource Clean Up

CloudFormation

Select and delete the Live Streaming and SPEKE CloudFormation templates deployed as part of the prerequisites. This will clean up all the resources created by the two templates.

AWS Elemental MediaTailor

Select the configuration you created and hit the Delete button to remove the configuration.