- Newest
- Most votes
- Most comments
File group would only output audio/video in media containers such as .mp4, .mov, etc. or raw in the case of audio (aac, wav, etc.).
To provide DRM, one of the other output group types must be used such as HLS, DASH, or CMAF.
The reason for this is that a manifest file is generated along with the media which provides instructions for interacting with the DRM solution used, whether static key or SPEKE (https://docs.aws.amazon.com/speke/latest/documentation/what-is-speke.html).
Here is a description of Apple's Fairplay DRM and how it interacts with HLS: https://developer.apple.com/streaming/fps/
And the spec for DRM with DASH: https://dashif.org/identifiers/content_protection/
Correct. See documentation here: https://docs.aws.amazon.com/mediaconvert/latest/ug/encrypting-content.html You could have MediaConvert output HLS audio-only and add the DRM info there if you'd like.
Is aws planning to add a DRM integration option for file groups?
Or what do you suggest to integrate DRM on .mp3 and .aac audio because we don't want to create hls or dash audios ?
Relevant content
- asked 2 years ago
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
So, we can not integrate a DRM if we use file groups ?
we use file groups for ajust bitrates and simple rates to different format like .mp3 and .aac
So what's the best solution to that?