You can see Outputs on the Routes page. An Output can be in a different AWS region from the receiving Source, enabling global transportation of broadcast quality transport streams. As a single entity within M2A CONNECT, an Output can even have multiple AWS Regions from which streams may be delivered to Destinations. Outputs may be assigned to separate receiving organisations (ie Subscribers), or they may be hand-off points to your own organisation. When used with Subscriptions, a Distributor’s control of Output allows the content, its delivery mechanism and hand-off point to be easily controlled.

A Destination is a location external to M2A CONNECT, which may be represented by an IP address or, in the case of an AWS Entitlement, the AWS Account of the receiving organisation.

Outputs and Destinations may be set-up and configured as part of the onboarding process, but new Destinations can also be created and managed by the receiving organisation.

The “plus” button enables authorised users to add a Destination to an Output. The options for Destinations are defined on the Output, and they include the choice of AWS Regions from which the stream is sent, whether encryption is set, the method of stream delivery (i.e. transport protocol or AWS Entitlement) and the number of Destinations allowed.

A Destination can be named by the receiving organisation, and its name and delivery method remain visible on the Destination entity. The key specifications of the Destination are available by clicking on the entity; for example, the URL of an SRT stream and the ARN of the outputting resource both necessary for the receiver are provided.

A Destination can be removed by an authorised user, and can be edited within the bounds of the configured Output constraints, i.e. to an allowed region, to an allowed transport method. Please note, changes to Destination names result in new ARNs and outputting IP Address.

Current limitations

• Encryption set up and key exchange are managed by your M2A Media representative.