- Newest
- Most votes
- Most comments
If your MediaPackage channel already exists, the desired endpoint will need to be added to the CloudFront distribution as an origin. Also define behaviors for specific file types (ex. *.m3u8, *.ts) If your MediaPackage endpoint is https://<mediapackage_channel_uid>.mediapackage.us-east-1.amazonaws.com/out/v1/<mediapackage_endpoint_uid>/index.m3u8 then the CloudFront path will be https://<cloudfront_distribution_uid>.cloudfront.net/out/v1/<mediapackage_endpoint_uid>/index.m3u8
Also, you may want to look at the Workflow Wizard in AWS MediaLive console. This will allow you to create a streaming channel with MediaConnect, MediaLive, MediaPackage and CloudFront. You will need to select a CloudFront endpoint when configuring the MediaPackage. https://docs.aws.amazon.com/medialive/latest/ug/wizard.html https://docs.aws.amazon.com/medialive/latest/ug/wizard-procedure.html
Note that Workflow Wizard will add several endpoints in MediaPackage for HLS, DASH and CMAF. All of those may not be needed in your application. The output from Workflow Wizard may be useful as a reference if you want to edit your existing streaming channel.
I just tried this, and I cannot make it past Step 1 because the Next button does absolutely nothing. All of the settings are correct, but the Next button does not work.
Relevant content
- asked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated 21 days ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago
Turns out MediaLive Workflows do work, as long as you create one completely from scratch. And I have to say I'm very impressed by the Workflow Wizard thus far.