> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/performance-cdn/static-content-delivery/create-large-cdn-resource.md).

# Create Large CDN Resource

A Large CDN Resource is designed for large downloadable objects and live streaming workloads. It supports static large-file delivery from a customer origin or Stook Object Storage, as well as live stream delivery through an existing streaming origin or RTMP Push.

## When to Use a Large CDN Resource

Use a Large CDN Resource for:

* Large downloadable files such as video, audio, `.zip`, and `.exe` files
* Archives and software packages
* Existing HLS or DASH streams
* Live streams published through RTMP Push

{% hint style="info" %}
For images, CSS, JavaScript, web fonts, and other small static assets, use a [Small CDN Resource](/products/performance-cdn/static-content-delivery/create-small-cdn-resource.md).
{% endhint %}

{% hint style="info" %}
For prerecorded video that requires automatic adaptive bitrate packaging, use a [VOD Resource](/products/performance-cdn/static-content-delivery/create-vod-resource.md).
{% endhint %}

{% hint style="warning" %}
Large CDN Resources do **not** support the following file extensions.\
Requests for these file types return **HTTP** **403 Forbidden** responses.

`ashx, aspx, bmp, css, cur, eot, gif, htm, html, ico, jpeg, jpg, jpr, js, otf, pdf, php, png, psb, psd, svg, swf, swz, tif, tiff, ttf, txt, webp, woff, xml`
{% endhint %}

## Create a Large CDN Resource

Create and manage **Large CDN Resources** from the [**Medianova Control Panel**](https://cloud.medianova.com). 

Navigate to **CDN** and select **Create CDN Resource** to launch the **Create CDN** wizard.

{% stepper %}
{% step %}

### Select the Resource Type

Navigate to **CDN** and click **Create CDN Resource**.

The **Create CDN** wizard opens.

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

Select **Large CDN**, then click **Create** to continue.
{% endstep %}

{% step %}

### Select the Delivery Mode and Enter the Resource Name

Choose the delivery mode that matches your workload.

#### **Static Large Files**

Use **Static Large Files** for software packages, archives, downloads, audio files, video files, and other large objects that do not require transcoding.

#### **Live Streaming**

Use **Live Streaming** for RTMP ingest or for packaged live streams retrieved from an existing origin.

#### **Resource Name**

Enter a unique resource name.

The resource name becomes part of the default CDN hostname.

For example:

```
example.lg.mncdn.com
```

#### **Internal Label**

Optionally assign a private label to help your team identify and manage the resource.

Internal labels are used only within the Control Panel and for API filtering. They do not affect the public CDN hostname.

Click **Next**.
{% endstep %}

{% step %}

### Configure Your Source

Select where Medianova should retrieve or receive the content.

The available source options depend on the delivery mode selected in the previous step.

**Static Large Files**

Choose one of the following source types.

**Customer Origin**

Select **Customer Origin** to retrieve content from your own web server, application server, storage endpoint, or load balancer.

Click **Add Origin** to configure one or more origin servers.

The origin list displays:

<table><thead><tr><th width="175">Field</th><th>Description</th></tr></thead><tbody><tr><td><strong>Host</strong></td><td>Hostname or IP address of the origin server.</td></tr><tr><td><strong>Protocol</strong></td><td>HTTP or HTTPS used for CDN-to-origin connections.</td></tr><tr><td><strong>Priority</strong></td><td>Determines the order in which configured origins are selected.</td></tr><tr><td><strong>Weight</strong></td><td>Distributes requests between origins with the same priority.</td></tr></tbody></table>

Multiple origins can be configured with priority and weight settings for availability and traffic distribution.

**Stook Object Storage**

Select **Stook Object Storage** to retrieve content from an existing Stook Bucket.

Configure the following fields:

<table><thead><tr><th width="172.333251953125">Field</th><th>Description</th></tr></thead><tbody><tr><td><strong>Storage Bucket</strong></td><td>Select the Stook Bucket containing the files to be delivered.</td></tr><tr><td><strong>Subfolder</strong></td><td>Optionally restrict the source to a specific path within the selected bucket.</td></tr></tbody></table>

**Live Streaming**

Choose one of the following source types.

**Customer Origin**

Select **Customer Origin** to retrieve packaged live streaming content from your own origin server.

This option is suitable for existing HLS or DASH streaming origins.

Click **Add Origin** to configure one or more origin servers.

**RTMP Push**

Select **RTMP Push** to publish live streams directly to Medianova through RTMP ingest.

Configure the following credentials:

<table><thead><tr><th width="127">Field</th><th>Description</th></tr></thead><tbody><tr><td><strong>Username</strong></td><td>Username used by the streaming encoder to authenticate the RTMP publishing connection.</td></tr><tr><td><strong>Password</strong></td><td>Password used by the streaming encoder to authenticate the RTMP publishing connection.</td></tr></tbody></table>

Configure these credentials in your streaming encoder, such as OBS Studio, Wirecast, or FFmpeg.

After creating the resource, use [Stream Management](/products/performance-cdn/static-content-delivery/stream-management.md) to configure SMIL streams and quality profiles.

Click **Next**.
{% endstep %}

{% step %}

### Configure SSL/TLS

Choose how HTTPS should be configured for the Large CDN Resource.

Available options are:

* **Use Existing SSL**
* **Add Own SSL**
* **Free SSL**
* **Skip for Now**

**Use Existing SSL**

Assign an SSL certificate that already exists in your account.

Only certificates available in the current account are listed. To create a certificate during this workflow, select **Add Own SSL** or **Free SSL**.

**Add Own SSL**

Upload or paste your own certificate and private key.

Configure the following fields:

* **SSL Certificate Name**
* **Certificate Format**
* **Domain**

Supported certificate input methods include:

* Domain SSL
* Paste `.crt` / `.key`
* `.pfx` / PKCS#12
* Upload Files

For certificate upload and domain configuration details, see [**CNAME & SSL**](/products/performance-cdn/static-content-delivery/advanced-configuration/cname-and-ssl.md).

**Free SSL**

Request a free Let’s Encrypt certificate through DNS validation.

Configure the following fields:

* **SSL Certificate Name**
* **Domain**
* **Coverage**
  * Single Domain
  * Wildcard

Wildcard certificates require CNAME-based domain validation.

For the complete provisioning and validation process, see [**Use Free SSL Certificates**](/products/security/ssl-tls-encryption/use-free-ssl-certificates.md).

**Skip for Now**

Continue without assigning a dedicated certificate.

Medianova serves the default CDN hostname over HTTPS using its shared SSL certificate. A dedicated certificate can be assigned later from **Settings →** [**SSL & TLS**](/products/security/ssl-tls-encryption.md) when configuring a custom domain.

Click **Next**.
{% endstep %}

{% step %}

### Review & Activate

Review the configuration before creating the resource.

The summary includes:

* Resource information
* Origin configuration
* SSL/TLS configuration
* CDN endpoint information

When the configuration is valid, click **Create Resource**.

{% hint style="success" %}
New CDN resources are typically provisioned within **30 seconds**.
{% endhint %}
{% endstep %}
{% endstepper %}

## Validate CDN Delivery

After creating the resource, send a request to an existing object through the CDN hostname:

```
curl -svo /dev/null "https://example.lg.mncdn.com/path/to/file.zip" --compressed
```

Replace `example.lg.mncdn.com` with the Large CDN Resource hostname and `/path/to/file.zip` with a valid object path.

For live streaming resources, validate an existing HLS or DASH manifest URL after the stream is available.

```c
curl -svo /dev/null "https://example.lg.mncdn.com/path/to/manifest.m3u8" --compressed
```

The command sends an HTTP `GET` request to the CDN, displays connection details and HTTP request and response headers, and discards the response body.

Use a path that returns **HTTP 200 OK**. If a custom CNAME is configured, test the custom hostname instead of the default MNCDN hostname.

## Troubleshooting

If the resource does not serve content correctly:

* Verify that the origin server is reachable.
* Confirm that the configured origin port is accessible.
* Ensure that the requested object exists in the configured origin path or Stook subfolder.
* Confirm that the selected Stook Bucket is accessible from the current account.
* Verify the RTMP username and password configured in the streaming encoder.
* Confirm that custom CNAME records have propagated before testing the custom hostname.
* Verify that the assigned SSL certificate is active and covers the requested domain.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.