Media Acceleration Live Broadcast lets you deliver live video through the Atomile content delivery network (CDN). To start using the product, create at least one live streaming domain, connect the domain to the assigned CNAME record, and then configure the domain features required by your live streaming workflow.

This guide walks you through the initial setup process: understanding live streaming roles, planning the domain role, adding an ingest or delivery domain, configuring DNS routing, and identifying the essential settings to review before handling production traffic.

Before You Begin

Make sure you have:

• Access to Media Acceleration Live Broadcast > Configuration in the Atomile console
• An active live streaming contract item
• The domain names that you want to use for ingest or delivery
• Origin server information, such as IP addresses or an origin hostname, if you plan to use Origin Pull
• Permission to add CNAME records at your DNS provider

Important: Configure access controls, such as Referer rules, IP access control, or token authentication, before using the domain for production traffic.

Understand Live Streaming Roles

Live streaming delivery usually includes three parts:

• Broadcaster or encoder: Produces the live stream and sends it into the streaming workflow
• CDN: Receives or retrieves the stream, then delivers it through CDN edge servers
• Viewer or player: Requests and plays the stream through a playback URL

In Media Acceleration Live Broadcast, different domain roles describe where a domain sits in this workflow:

• Ingest domain: The entry point for a live stream. Broadcasters, encoders, or streaming applications use this domain to publish a stream into the CDN.
• Delivery domain: The playback entry point for viewers. Players and playback applications use this domain to request and play the stream from the CDN. Delivery domains support two common delivery patterns:
  • Origin Pull: Your origin server provides the live stream. The CDN uses a delivery domain to pull the stream from your origin, and viewers play the stream from the delivery domain.
  • Ingest via Publish: The broadcaster publishes the stream to the CDN through an ingest domain. Viewers play the stream through a delivery domain associated with that ingest workflow.

After the domain is created, Atomile assigns a CNAME record. Adding this CNAME record at your DNS provider routes requests for your ingest or delivery domain to Atomile.

Plan Your Live Streaming Domain

Before adding a domain, use the domain role and delivery pattern to decide what to create.

Domain Role	Used By	Purpose
Ingest	Broadcasters, encoders, or streaming applications	Publishes a live stream into the CDN.
Delivery	Viewers, players, or playback applications	Requests and plays the live stream from the CDN.

If you create a delivery domain, select the live streaming mode that matches how the CDN obtains the live stream.

Live Streaming Mode	Behavior	Use When
Origin Pull	The CDN pulls live streams from your origin server.	You already have an origin that hosts or produces the live stream.
Ingest via Publish	Broadcasters publish streams to the CDN, and viewers pull streams through the delivery domain.	You want to pair an ingest domain with one or more delivery domains.

Add a Live Streaming Domain

Adding a domain creates the CDN configuration entry that you use for live ingest or live delivery.

1. Go to Media Acceleration Live Broadcast > Configuration.
2. Choose New Domain.
3. Configure the basic domain information.

Field	Required	Description
Contract-item	Yes	Select the contract item for the new domain.
Custom Control Group	No	Associate the domain with an existing control group. You can leave this blank and configure it later.
Domain Role	Yes	Select Ingest or Delivery.

4. If Domain Role is Ingest, enter the domain names in Ingest Domain.
5. If Domain Role is Delivery, select the Live Streaming Mode.
6. Configure the delivery domain settings for the selected live streaming mode.

For Origin Pull, configure the following fields:

Field	Required	Description
Origin Protocol	Yes	Select the protocol used to pull streams from the origin. Supported options are RTMP, HTTP-FLV, HLS, and DASH.
Domain	Yes	Enter the delivery domain name.
Bring Your Own Origin	Conditional	Use your own origin server. Enter the origin IP address or hostname in the origin field. Separate multiple IP addresses with semicolons.
Object Storage	Conditional	Use Atomile Object Storage as the origin source.

For Ingest via Publish, configure the following fields:

• Ingest Domain: Select an existing ingest domain to associate with the new delivery domain. If no ingest domain is available, select Do not associate and associate one later.
• Delivery Domain(s): Enter the delivery domain names.

7. Configure the remaining domain settings.

• Application Name: Enter the application names used in stream URLs, such as rtmp://domain.com/AppName/StreamName. Separate multiple names with semicolons. Leave this field blank to allow all application names.
• Notes: Add internal notes for this domain.

8. In Acceleration Configuration, choose how to create the domain configuration:

   • Custom Configuration: Create the domain with the default configuration. You can adjust the settings later.
   • Copy from Existing Domain: Copy the configuration from an existing domain, then select the source domain from the drop-down list.

9. Review the information and submit the domain.

After the domain is created, it appears in the domain list with an assigned CNAME record.

Configure DNS Routing

To route live streaming traffic through Atomile, add the assigned CNAME record at your DNS provider.

1. In the domain list, find the domain that you created.
2. Copy the assigned CNAME record.
3. At your DNS provider, add a CNAME record for your ingest or delivery domain.
4. Confirm that the domain record points to the assigned Atomile CNAME.

Example: Publish a Stream and Play It Back

The following example shows how an ingest domain and a delivery domain work together in an Ingest via Publish workflow. Replace the example domain names, application name, and stream name with your own values.

Item	Example Value
Ingest domain	publish.example.com
Delivery domain	play.example.com
Application Name	live
Stream Name	demo

In OBS Studio or another compatible encoder, configure the custom RTMP output:

• Server: rtmp://publish.example.com/live
• Stream Key: demo

With this configuration, the encoder publishes the stream to the ingest domain as live/demo. Atomile then makes the stream available through the associated delivery domain.

To test playback, open a compatible test player and use a playback URL that matches the delivery protocols enabled for the delivery domain. Common URL patterns include:

• RTMP: rtmp://play.example.com/live/demo
• HTTP-FLV: https://play.example.com/live/demo.flv
• HLS: https://play.example.com/live/demo/playlist.m3u8

If playback does not start, confirm that the ingest domain and delivery domain are associated, DNS routing is complete, the selected playback protocol is enabled, and any access control rules allow the test request.

Configure Essential Domain Settings

After DNS routing is ready, review the configuration areas that apply to your streaming workflow.

Configuration Area	When to Use It
Origin Settings	Configure origin pull settings, origin addresses, Host header behavior, and advanced origin routing.
Application Names and Delivery Protocols	Restrict allowed application names or control playback protocol output for delivery domains.
Access Control	Protect streams with IP access lists, Referer access lists, User-Agent access lists, token authentication, or remote authentication.
Cache Optimization	Configure cache rules and query string handling for origin-pull delivery domains.
HTTP Protocol Settings	Add, replace, or remove HTTP headers, or enable HTTP/2 for client connections.
Stream Status Callbacks	Send callback notifications for stream start and end events.
Client IP Header	Pass the original client IP address to your origin server.
Log Service	Review access log settings and configure log merge granularity.