-
Hi Good Day ! I’m trying to encrypt the hls video outputs in our AWS MediaConvert but right now I can’t seem to make it work. I’m following this guide https://foliovision.com/player/securing-your-video/mediaconvert-encrypted-hls-guide but it’s not working for us because I can’t set a specific destination path since we’re doing VOD Automation where in when a user uploaded a file in s3 bucket, it will automatically digest and process the file the uploaded file based on the set job templates. Each outputs have unique directories in the destination s3 bucket which is why I can’t do step 10 and 16. Is there a way we can encrypt the processed videos so media/video grabbers can’t download the media files since we’re creating a subscription website. Hope you can help us Thank you in advance :).
-
-
Hello Slogin,
Thanks for reaching to us!
The destination in point 10 and 16 is an output destination that needs to be set manually. Unfortunately, there’s no way to make this process automatic and you need to do it for every video by hand, that’s the biggest limitation with AWS.
I’ll discuss our possibilities with development team but I’m worried there’s not much that we can do in this case.
Thanks,
Juraj
That’s really unfortunate. Is there another way we can prevent video downloading apps and the likes of idm downloading our videos considering aws mediaconvert encryption is out of the question? Thank you
Hello Slogin,
you should be able to do this without issues. You know what will be the target S3 bucket path like, so you can easily use part of that path for step 10 and 16.
If you are able to do AWS automation then this really should be the easy part of it. When you are submitting a new encoding job you will have to adjust these paths of course, but that really should be possible to do in AWS.
Thanks,
Martin
