- Newest
- Most votes
- Most comments
Aws MediaConvert and MediaPackage have the possibility to manage external DRM ( not provided by themselves). you can easily able DRM encryption and insert the External DRM parameter like ID , Key and URL. Here one example : https://github.com/awslabs/speke-reference-server/blob/master/workflow/drm-live.md. Here a step by step guide with a specific DRM : https://pallycon.com/blog/how-to-enable-drm-encryption-in-aws-media-services/
First, you'll need to choose a SPEKE-compliant DRM key provider. If you don't want to run your own, you could go with a third-party service like Verimatrix, BuyDRM, or Irdeto. They'll give you the key server URL and other credentials you'll need. A third-party service will usually stay on top of any changes or updates in the DRM landscape as well.
In your MediaPackage console, you'll want to create a new packaging configuration. When you do this, you'll see an option for encryption. Enable encryption and choose the encryption method. You'll typically want to select "Sample-AES" for HLS or "SAMPLE-AES-CTR" for DASH.
You'll need to input the details from your key provider. This includes the URL of the key server and any authentication details they've given you. You'll also need to specify which DRM systems you want to use - Widevine (Google), PlayReady (Microsoft), FairPlay (Apple), or some combination. Once that's set up, create your MediaPackage endpoints using this packaging configuration so MediaPackage requests keys from your DRM provider whenever it needs to package content. Finally, you'll need to make sure your video player on the client side is set up to handle the DRM.
Relevant content
- asked 2 years ago
- asked 3 years ago
- Accepted Answerasked 3 years ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 15 days ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 3 years ago