To deliver content to your broadcast partner, simply register them as a Subscriber via the M2A Console. M2A CONNECT supports delivery within and between AWS Regions and Availability Zones. The AWS account ID of your broadcast partner is required as the target address when creating a Subscriber.
Subscriptions tie your Subscribers to your schedule of content via the Labels set for Sources and Events. Each Subscription can target a curated selection of content. The Subscriber will be granted access to the Source’s content according to this Event schedule. This gives you complete control over which Events a Subscriber is entitled to receive. This allows Distributors to maximise utilisation of a single Source by carrying varying content throughout the day. It also replaces the need for operating event-by-event routing for both Subscribers and Distributors.
Subscriptions use a label query selector to determine which events in your schedule the associated Subscriber has access. Therefore, you will need to ensure that your scheduled Events use appropriate identifying labels.
Access to the Source and its Events is granted by the linking of Labels within Subscriptions, and Subscriptions to Subscribers. A valid Subscriber to a live Event will receive the Event when the Event starts.
Tip: You don’t have to schedule all of your events before you create a subscription. So long as the matching labels are applied to any newly created events, the subscription will continue to work.
This is useful when your content schedule is not fully known ahead of time or is likely to change at late notice.