Adding an AWS MediaConnect Source

this source is configured on an aws mediaconnect that serves as the ingest object the stream originates from an aws elemental link device, which serves as the origin the origin is not managed by zen master however, since zen master is connected to aws mediaconnect and aws mediaconnect is connected to the aws elemental link, by enabling/disabling the source you are also starting/stoping the stream through zen master at the time of the source configuration the spcific aws mediaconnect component doesn't have to be necessarily running the aws mediaconnect component can be started at a later time and it may, in turn, start the stream, which is coming from the connected aws elemental link the following procedure describes how to add an aws elemental link mediaconnect source in addition, an explanation of each of the configuration parameters is given in the table below to create an aws elemental link mediaconnect source in the main navigation, click sources click + add the create new source window is displayed create new source window under aws media , click on aws mediaconnect the create new aws media source window opens in the info section, in the name field, type a logical name for the source in the tags field, select one or more of the predefined tags from the drop down list tags are used for access control by selecting a tag, you are relating this source to that tag tags are associated with certain roles (through the users & roles screen), and roles, in turn, are associated with users and user groups if you would like to create a new tag, see creating a tag docid\ ypm9tw81ap6nq8stkv4rd in the events configuration profile field, select from the dropdown list the profile that you would like to apply to this source by default, the default profile is applied events profiles consist of a series of rules that determine precisely how various types of events are logged and what results they trigger in the input section, under protocol , select the aws elemental link radio button under the source configuration section, in the aws account field, select from the drop down the aws account that matches the aws account of the aws mediaconnect channel that serves as the ingest object in the region field, select from the drop down list the aws region that matches the aws mediaconnect channel that serves as the ingest object in the aws elemental link field, select the aws elemental link device that serves as the origin the origin aws elemental link has to be registered to the aws account in the initial state section, select the muted checkbox if you would like to disable error/recovery notifications for this source upon initial configuration you can unmute the source at any time click save parameters table parameter description info name specify a name for the aws media source in zen master tags select one or more of the predefined tags from the drop down list tags are used for access control by selecting an tag, you are relating this source to that tag tags are associated with certain roles (through the users & roles screen), and roles, in turn, are associated with users and user groups if you would like to create a new tag, see creating a tag docid\ ypm9tw81ap6nq8stkv4rd events configuration profile select from the dropdown list the profile that you would like to apply to this source by default, the default profile is applied note events profiles consist of a series of rules that determine precisely how various types of events are logged and what results they trigger input aws elemental link radio button in the input section, under protocol, select the aws elemental link radio button source configuration aws account under the source configuration section, in the aws account field, select from the drop down the aws account that matches the aws account of the aws mediaconnect channel that serves as the ingest object region in the region field, select from the drop down list the aws region that matches the aws mediaconnect channel that serves as the ingest object initial state muted select this checkbox if you would like to disable error/recovery notifications for this source upon initial configuration