DRM encryption on AWS Elemental using a multi-DRM service

AWS Media Services are a set of fully managed services that can be used to build video workflows on the cloud. AWS Elemental MediaPackage is a just-in-time video packaging and origination service that helps users deliver secure and scalable video streams to a diverse range of playback devices and content delivery networks (CDNs). It offers a broadcast-grade viewing experience and built-in resilience and scalability which make content protection and control easier with no manual intervention required.

AWS Elemental MediaConvert is a file-based video processing service that can be used by content owners and distributors for scalable video processing. Digital rights management (DRM) technology is necessary to protect copyrighted content from unauthorized access. AWS MediaConvert and MediaPackage support the Secure Packager and Encoder Key Exchange (SPEKE) API that uses a simple configuration to enable the encryption of DASH/HLS outputs.

The SPEKE specification is an open, royalty-free API specification based on DASH-IF Content Protection Information Exchange Format (CPIX) that defines the standard for communication and authentication between key servers and encoders, transcoders, and origin servers of media content and DRM key providers, thus enabling a full-fledged DRM video protection system. DRM systems provide keys to AWS Elemental MediaPackage for content encryption, and licenses to supported players for decryption.

A multi-DRM video protection service can be easily applied to live streams and VOD content generated by AWS Elemental Media Services or AWS Elemental appliance-based solutions. The SPEKE API integration can be configured on the AWS console while one packages the VOD or live sources. The encrypted DASH or HLS outputs can then be delivered by Amazon CloudFront or any other CDN.

When the client’s player plays the content, the encryption key is requested to the multi-DRM server for decryption and playback. This license request can be used to set various playback and security policies. For example, content owners can enable the download and offline playback feature, and set a limit to the playback period. DRM security levels and output protections that might be needed can also be set by using output groups such as DASH ISO output with Google Widevine and Playready DRM for Chrome, Firefox, Edge, Android, etc., and Apple HLS output with FairPlay DRM for Safari and Apple devices.

Sponsor Ads

• Ad Space Available - Rent it Now!

Report this Page

Created on May 12th 2021 06:41. Viewed 46 times.

Share on APSense

Comments