Media Live details


Could you please help me in my application? I read all the media live documentation but I still have many questions in order to use media live in a web tv application. I'm newbie in aws services.
I will describe you my goal. It is a web TV application to live stream once a month a webinaire about a subject. Meanwhile, this video must be stored for later use.
My questions:

  1. In the input, three cameras will be used. How can I integrate them. RTMP pull or push? I have to use software encoder like OBS?
  2. The live streaming must be stored. How can I do it? By aws media store or use the output archive of the media package service?
  3. To serve the most of devices, what output group formats I have to use?
  4. The Interactive Video Service (IVS) can replace media live in my case? I discovered that is simpler than media live but I haven't idea about what is the better in cost, utility ...
    Best regards
asked 3 years ago490 views
2 Answers


I'll try to answer your questions in the order you had posed them.

Storage for later use
This can be done via either an Archive output group, or an HLS output group to S3, or by using MediaPackage ad using the Live to VOD harvest capability to create a VOD asset for later use.

Q1. 3 inputs
Can you elaborate on the requirement of 3 cameras? Do you mean that for a single MediaLive channel you would like to switch between 3 different cameras, or that you want to create 3 MediaLive channels each with a single camera? If 3 cameras to a single MediaLive channel then this is not possible for push type inputs such as RTMP Push, RTP inputs etc. MediaLive has a current limit of a maximum of 2 Push inputs that can be attached to a MediaLive channel at any given time. A workaround would be to use something upstream of MediaLive such as OBS. With OBS you would select the active camera that is then sent via RTMP to the MediaLive channel.

Q2 & Q3
Easier to answer questions 2 & 3 at the same time. MediaPackage can create multi output formats, e.g. DASH, HLS , CMAF. This will allow for the broader device coverage. As previously mentioned MediaPackage also has Live to VOD capability ( that can create the VOD assets for you to easily archive the events.

IVS and MediaLive have somewhat different customer bases and therefore have different feature sets. The MediaLive / MediaPackage workflow gives you many different output formats, and destinations that the content can be routed to. Therefore it is a bit more complex to configure. IVS is more built for interactive solutions, and therefore has that functionality that isn't available in MediaLive. See for some info describing the difference between an IVS workflow and a workflow using the MediaServices, e.g. MediaLive -> MediaPackage -> CloudFront. As for pricing the pricing page of each of these describes the cost of each service.

See also the new MediaLive Workflow Wizard that was recently added to the MediaLive console. This is an easy 4 stop process to stand up a workflow that can span multiple AWS service, e.g. RTMP in to MediaLive to MediaPackage to CloudFront. Using the Wizard you can easily select the output rates you want for your channel. Once the workflow is configured you can still edit the services to tailor the workflow to better suite your needs, e.g. add an additional output to the MediaLive channel, or add another output endpoint in the MediaPackage channel.

answered 3 years ago

Thank you for all these informations

answered 3 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions