The ABCs of AWS Elemental Video Processing - AWS Elemental Conductor Live 3

This is version 3.17 of the AWS Elemental Conductor Live 3 documentation. This is the latest version. For prior versions, see the Previous Versions section of AWS Elemental Conductor Live 3 Documentation.

The ABCs of AWS Elemental Video Processing

Both AWS Elemental Conductor Live 3 and AWS Elemental Live work on the same entities: channels (events), profiles, and nodes.

Channels and Events

A “channel” is a session that decodes and encodes a stream of video (from a network location) or a video file. Video input comes into the channel and video output is the final outcome of the channel. All the encoding activity occurs within a channel.

If you are familiar with AWS Elemental Conductor Live 3 version 2.5 or earlier, note that channels were referred to as events in those earlier versions. Channels and events are virtually identical; for a discussion of the key differences, see Where to Work – AWS Elemental Conductor Live 3 or a Worker Node?.


The encoding activity is defined in a “profile”: the information contained in the profile includes the source of the video input, the kinds of processing that the video will undergo, the types of output protocols to produce (for example, Archive or UDP/TS), and the types of outputs (the containers).


The physical computer where the video activity is handled is called a “node”. When you are deploying AWS Elemental Conductor Live 3, nodes are grouped into a cluster: by adding a node to a cluster, you make it known to Conductor. If a node is not in a cluster, it is not being managed by Conductor.

Channel – Profile – Node Association

When you create a channel, you associate it with one profile and one node. So the associations between these three entities is via the channel.

    Image file diagram-ncp.png

In addition, keep the following in mind:

  • One profile can be used by multiple channels: so profiles are multi-use.

      Image file diagram-cp.png
  • One node can handle multiple channels: so nodes are multi-taskers.

       Image file diagram-nc.png