HLS AES encryption can be used for HLS only, certainly it not applicable to RTMP; probably you mean RTMPS/RTMPE? Unfortunately, nimble doesn't support it.
If you need to encrypt traffic between origin and edge servers, we would recommend to use SRT protocol with encryption ( passphrase / pbkeylen parameters). Refer to this page for SRT support in Nimble: https://wmspanel.com/nimble/srt
If you just mean you want to perform AES encryption for your output HLS streams - origin of streams doesn't matter, so it can be applied to streams pulled by RTMP like any other stream. You can read about HLS AES encryption support here: https://blog.wmspanel.com/2015/02/hls-aes-encryption-drm-support-nimble-streamer.html
Thank you. The second answer was what I wanted. I just want to perform AES Encryption for my output HLS streams. Do I perform the steps on my edge nimble servers?
Yes, it should be set up on edge servers.
I am following step 1. from https://blog.wmspanel.com/2015/02/hls-aes-encryption-drm-support-nimble-streamer.html url for using encryption key hosted by Nimble, is there any other configuration that I need to perform?
I am getting "GET /test/test.stream/hls.key?nimblesessionid=230 HTTP/1.1" on my nimble access log when a stream is requested but the playlist.m3u8 has only the following parameters
How do I get the aes key format? I have created an application and pulled a RTMP stream.
Master playlist does not contain a reference to hls.key, but chunklist does (check the content of chunks.m3u8). HLS AES key is just 16 bytes used as an encryption key.
Thank you your explanation. I am a bit new to streaming and have only been recently testing nimble. I have the following data in the chunks.m2u8:
Does this mean my stream is aes encrypted?
Yes, HLS AES encryption is applied to that stream. If you download a chunk from this chunklist (e.g. l_934_22481738_2248.ts) it will not be played without decryption (try to play downloaded chunk file with e.g. VLC).
and required to achieve the purposes illustrated in the
If you want to know more or withdraw your consent to all or some of the cookies, please
refer to the