search

awslabs / speke-reference-server

Secure Packager and Encoder Key Exchange (SPEKE) is part of the AWS Elemental content encryption protection strategy for media services customers. SPEKE defines the standard for communication between our media services and digital rights management (DRM) system key servers. This project provides the basic framework that partners can specialize and extend to support their specific method of Digital Rights Management while utilizing AWS' video streaming solutions.
https://docs.aws.amazon.com/speke/latest/documentation/what-is-speke.html
Apache License 2.0
109 stars 48 forks source link

is SPEKE mandatory for DRM integration between MediaPackage and DRM provider ? #42

Open jorgebento opened 3 years ago

jorgebento commented 3 years ago

Hi All,

Do I need to use SPEKE in order to stablish a communication between media Package and DRM provider?

I mean may I fill the key proxy address with my server ? Is it possible to mediapackage retrieves keys directly on my server ?

image

Or at least may I connect media package to my drm server bypassing speke? just using api gateway ?

image

Regards

andreasgangso commented 3 years ago

You don't need to use this reference server. But as far as I know, whatever URL you enter needs to be a server that implements SPEKE. So you need to check with your DRM provider if they have a SPEKE url you can use.

jorgebento commented 3 years ago

Thank you, In the meantime I was able to deploy a mock drm server that basically always respond same speke xml file but with real keys retrieved from my drm provider. For dash+cenc you can use a cpix compliant xml but for hls+fairplay need to format xml file with speke tags otherwise does not work. Media converter can talk directly to drm server, does not need aws api gateway Media packager only works via api gateway, so you need to intermediate the communication using api gateway. For vod content is straigh forward but for live channels did not worked already....