MediaPackage Egress Endpoint Failure When Using SPEKE and MediaConvert for HLS

Question

My MediaPackage is failing at the egress endpoint. What are the possible causes of this error? I’m using SPEKE with MediaConvert to generate HLS

MediaConvert converts the MP4 file to HLS, and then we create an asset in MediaPackage with Axinom SPEKE DRM. This flow works correctly.
However, when we add an additional audio language, MediaConvert re-encodes the audio together with the original video. This is where the issue occurs, the process fails at the MediaPackage ingress endpoint.

Roman Chekmazov · Accepted Answer

There is no customer faced logs on EMP VoD for ingest.

You have only event notification for ingest:

https://docs.aws.amazon.com/mediapackage/latest/ug/cloudwatch-events-example.html

If you need more data you need to go to AWS support

re:Post Agent · Answer

Based on the information provided, there are several potential causes for your MediaPackage egress endpoint failure when using SPEKE with MediaConvert for HLS, especially after adding an additional audio language:

1. Audio track ordering issue: When you add a second audio language, MediaPackage may be changing the default audio track to the first one in the list, regardless of your original configuration in MediaConvert. This is a known behavior where MediaPackage honors the track ordering of incoming renditions. If you've designated a specific language as default in MediaConvert but it's not the first track, MediaPackage might override this setting.

2. DRM configuration issues: If you're using SPEKE with Axinom DRM, ensure that your SPEKE key provider is correctly configured for the content protection you're using. For MSS endpoints specifically, only PlayReady DRM is supported, though this may not be directly related to your HLS issue.

3. MediaConvert output format compatibility: The additional audio track might be causing format compatibility issues. Check that the audio codec and packaging settings are compatible with MediaPackage's requirements.

To resolve these issues, you could try:

1. Reordering your audio tracks in MediaConvert so that your desired default audio track appears first in the list.

2. Verifying that your SPEKE configuration is correct for multiple audio tracks.

3. Checking MediaConvert job logs for any errors related to the audio encoding process.

4. Reviewing MediaPackage ingress settings to ensure they're compatible with your new multi-audio MediaConvert output.  
**Sources**  
[Troubleshooting MSS endpoints in AWS Elemental MediaPackage - AWS Elemental MediaPackage v2](https://docs.aws.amazon.com/mediapackage/latest/userguide/mss-troubleshooting.html)  
[Default Audio Language Changed After Packaging with MediaPackage VOD | AWS re:Post](https://repost.aws/questions/QURR9CvsZGQI2ZO0QMAb2tTg/default-audio-language-changed-after-packaging-with-mediapackage-vod)

Roman Chekmazov · Answer

Try to create packaging group without DRM and check if MediaPackage can ingest multiple audio asset. You then will know should you focus on encryption or on transcoding process tuning.

MediaPackage Egress Endpoint Failure When Using SPEKE and MediaConvert for HLS

Add your answer

Relevant content