# Create Streaming Resource

The **Live Streaming CDN Resource** allows you to deliver live events, satellite broadcasts, and webcasts through the Medianova CDN. Configuration is completed in the [**Medianova Control Panel**](https://cloud.medianova.com), where you select the Live Streaming resource type and define how your stream is sourced, either from an origin server or via RTMP push from an encoder.

{% stepper %}
{% step %}

#### Open the CDN Resource creation page

From the left-hand navigation menu in the Medianova Control Panel, select **CDN → Create CDN Resource**.

<figure><img src="/files/c7XkxY1Zsr3DY6Pk0jbu" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Select Live Streaming as the CDN Resource type**

Under **Select CDN Resource Type**, choose **Live Streaming**.

This option is designed for real-time media delivery and supports protocols such as HLS, MPEG-DASH, and Smooth Streaming.
{% endstep %}

{% step %}
**Configure the Streaming CDN Resource**

**a. CDN Resource Name**

Enter a name for the CDN Resource.\
This name is used as part of the CDN delivery URL.

**b. Source of Your Files**

Choose how your live stream is delivered to Medianova.

<figure><img src="/files/CMl31Kxhv3wGBIkJuE8i" alt=""><figcaption></figcaption></figure>

**My Origin**

Select **My Origin** to pull the stream from your own server.

* **Origin URL**\
  Enter the URL where the streaming content is hosted\
  Example: `https://assets.domain.com`
* **CDN Resource Label**\
  Enter a descriptive label for the resource

<figure><img src="/files/NRvLh4Q8O8KsOreOVPDc" alt=""><figcaption></figcaption></figure>

**RTMP Push**

Select **RTMP Push** to push live streams directly from an encoder.

* **RTMP Username**\
  Username used by the streaming encoder
* **RTMP Password**\
  Password used by the streaming encoder
* **CDN Resource Label**\
  Enter a descriptive label for the resource

RTMP streams pushed to Medianova servers are delivered via HTTP-based streaming protocols.

<figure><img src="/files/cRzjgD6qeX4Nd26vnslr" alt=""><figcaption></figcaption></figure>

**Stream FLV**

<figure><img src="/files/I0x7yGTyBWiAdqaSQuw1" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/UjA9XozFOGuWwhGGjlOD" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Create the CDN Resource**

Click **Create CDN Resource** to complete the configuration.

The Live Streaming CDN Resource is created and becomes active.
{% endstep %}
{% endstepper %}

### Supported streaming capabilities

#### Supported formats and protocols

The Streaming CDN Resource supports the following formats and protocols:

* **HLS**
* **MPEG-DASH**
* **Smooth Streaming**
* **LL-HLS** for low-latency live streaming
* **FLV** (legacy format support)
* **MP4** for audio and video delivery

#### Origin pull and push methods

Streaming content can be delivered using pull or push-based workflows:

* **Origin Pull** using HTTP
* **RTMP Push** from encoders such as OBS, Wirecast, or Flash Live Encoder
* Supported protocols include **HTTP**, **RTMP**, **HLS**, and **SRT**

#### Security features

The Streaming CDN Resource supports the following security controls:

* Token authentication
* DRM support
* AES-128 encryption
* TLS 1.3
* IP whitelisting and blacklisting
* Geo-blocking
* Domain verification

#### Additional features

* **nDVR** support for pause, rewind, and playback of live streams
* Dockerized and software-defined CDN architecture
* **Anycast DNS** for global traffic distribution
* **Real User Monitoring (RUM)**
* **Multi-CDN and Hybrid-CDN** support
* API-based management and automation


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://clients.medianova.com/products/performance-cdn/streaming-content-delivery/create-streaming-resource.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.