Mediapackage Endpoint

Question

I am using MediaPackage, MediaLive, and S3 for live streaming. I am using MediaPackage for broadcasting and S3 for storing the data coming form Medialive channel input and share it to the users again.

After creating every necessity form node js backend, i am starting the channel from my backend. Channel is running  but the data is not coming to the endpoint and S3 bucket. Interesting point is that, when i enter the aws console and open the Medialive channel which i have created from backend, and go to the update section and click update button  **WITHOUT CHANGING ANYTHING** and start it again it is working perfectly.  I tried to update it from backend as it is working when i have updated from aws console, but updating from backend did not help. I know it is strange that it is not working unless it is updated with no change, but this is the case.

Answer

Thank you for your answer,
For starting and stopping channel i am already using these apis' javascript sdk:
https://docs.aws.amazon.com/medialive/latest/apireference/channels-channelid-start.html https://docs.aws.amazon.com/medialive/latest/apireference/channels-channelid-stop.html

And you also advised testing creation of stream using Workflow Wizard. I tested Workflow Wizard too. In my api i am doing the same steps with workflow wizard, but still need to update. Isn't it a little strange that updating a channel to be able to run it, without any change? What else could you suggest me to try?

Answer

Can you provide a clarification of the workflow? Is AWS MediaLive sending HLS streams to AWS MediaPackage and to S3, or just to S3? Also, are you using the Harvest Job function in AWS MediaPackage?

Typical live streaming has MediaLive sending HLS to MediaPackage, then a CDN, such as CloudFront, will pull the stream renditions from MediaPackage. Endpoints in MediaPackage need to be defined for CloudFront to pull from.
An alternative is MediaLive writing HLS to S3 and CloudFront pulling from S3.
In this scenario, MediaPackage can ingest the captured stream from S3, after the live event, and create an asset that can be pulled from a MediaPackage endpoint.

As to issues of controlling the channel from the API vs AWS console, something could be missing from the API based orchestration.

Answer

Perhaps there is something missing from the backend (API) process. A configuration or a procedure. You may want to review the Channel Start and Channel Stop in the MediaLive API documents, along with reviewing interfacing through the AWS API
https://docs.aws.amazon.com/medialive/latest/apireference/channels-channelid-start.html
https://docs.aws.amazon.com/medialive/latest/apireference/channels-channelid-stop.html

https://aws.amazon.com/api-gateway/

AWS MediaPackage should not be used for supplying streams directly to live streaming viewers. It is designed as an origin server, with Just-In-Time Packaging, that sources a CDN, such as CloudFront. Without a CDN, MediaPackage will be overloaded by direct viewer requests.
The same is true for accessing the stored streams in S3. It should be done through a CDN for both load distribution and safety reasons.

If the issue being experienced is not resolved, it may be helpful to use the Workflow Wizard in MediaLive's console. This will create an end-to-end channel, along with a CloudFormation template, which could be used for a configuration base. The individual AWS services could then be modified for the specific application and needs.

Mediapackage Endpoint

Relevant content