Create Small CDN Resource

Learn how to create a Small CDN Resource in the Medianova Control Panel for static content delivery.

A Small CDN Resource is designed for delivering static web assets such as images, CSS, JavaScript, and web fonts.

Content is cached and served from Medianova's global edge network to reduce latency, improve website performance, and offload requests from your origin infrastructure.

You can configure a Small CDN Resource to:

• Fetch content from your own infrastructure (Customer Origin)

• Serve content stored in Stook Object Storage (Origin Push)

The Create CDN wizard provides a guided workflow for selecting the resource type, configuring the source and SSL settings, reviewing the configuration, and deploying the resource.

Configuration is saved automatically as a draft until the resource is created or discarded.

When to use a Small CDN Resource

Use a Small CDN Resource for static website assets, including:

• Images

• CSS files

• JavaScript files

• Web fonts

• Other static website resources

If your content includes any of these extensions, create a Large CDN Resource (for large downloads or live streaming) or a VOD Resource (for on-demand video) instead.

Unsupported file extensions Small CDN Resources do not support the following file extensions. Requests for these file types return HTTP 403 Forbidden responses. 3gp, 3gpp, aac, asf, asx, avi, f4v, flv, m2p, m4a, m4v, midi, mov, mp3, mp4, mpeg, mpg, ogg, ogv, wav, wm

Create a Small CDN Resource

Create and manage Small CDN Resources from the Medianova Control Panel.

Navigate to CDN and select Create CDN Resource to launch the resource creation wizard.

The Create CDN wizard opens as an overlay without leaving the current page.

1

Select the Resource Type

Navigate to CDN and click Create CDN Resource.

The Create CDN wizard opens.

Select Small CDN, then click Create to continue.

2

Enter the Resource Name

Provide the information required to identify the CDN Resource.

Resource Name

Enter a unique resource name.

The resource name is used to generate the default CDN hostname.

Example:

example.sm.mncdn.com

Internal Label (Optional)

Enter an internal label to help identify the resource.

Optionally assign a private label to help your team identify and manage the resource. Internal labels are used only within the Control Panel and API filtering and do not affect the public hostname.

Click Next.

3

Configure Your Source

Select where the CDN should retrieve content from. You can use your own origin infrastructure or content stored in Medianova Stook Object Storage.

Customer Origin

Select Customer Origin to use your own web server, application server, load balancer, or storage endpoint as the origin.

Click Add Origin.

The Add Origin dialog opens.

Configure the following fields:

Field	Description
Protocol	Select the protocol used for connections from the CDN to the origin. Available options are HTTP, HTTPS, and Same as Request. Same as Request uses the protocol of the incoming client request.
Domain or IP Address	Enter the hostname or IP address of the origin server. Do not include the protocol or a URL path.
HTTP Port	Enter the port used for HTTP origin connections. The default value is 80.
HTTPS Port	Enter the port used for HTTPS origin connections. The default value is 443.
Host Header (Optional)	Specify the value sent in the HTTP Host request header. Leave this field blank to use the configured origin domain.
Origin SNI Request (Optional)	Specify the hostname sent through Server Name Indication during the TLS handshake with an HTTPS origin. Leave this field blank to use the configured origin domain.
Priority	Set the origin priority. Select Primary for an origin that should actively receive requests.
Weight	Define how traffic is distributed between origins with the same priority. Supported values range from 1 to 100; a higher value receives a larger proportion of traffic.
S3 Presigned Authentication	Enable this option when the origin requires S3 presigned authentication for CDN-to-origin requests.

The Host Header and Origin SNI Request fields serve different purposes:

• Host Header identifies the virtual host in the HTTP request.

• Origin SNI Request identifies the requested hostname during the TLS handshake.

For HTTPS origins, ensure that the Origin SNI hostname matches a domain covered by the origin server's SSL certificate.

Click Save Origin.

The configured origin is added to the resource. Repeat this process to configure additional origin servers.

Click Add Origin to configure one or more origin servers.

Stook Object Storage

Select Stook Object Storage to use an existing Stook bucket as the origin for this CDN resource.

Configure the following fields:

Field	Description
Storage Bucket	Select the Stook bucket that contains the content to be served through the CDN.
Subfolder (Optional)	Restrict the origin to a specific folder within the selected bucket. Only objects under this path are served by the CDN.

4

Configure SSL/TLS

Choose how HTTPS should be configured for your CDN resource.

Select one of the following certificate options:

• Use Existing SSL

• Add Own SSL

• Free SSL

• Skip for Now

Use Existing SSL

Assign an SSL certificate that already exists in your account.

Configuration

• Select a certificate from the list.

• Continue to the next step.

Only certificates available in your account are listed. To create a new certificate, select Add Own SSL or Free SSL.

Add Own SSL

Create a new certificate by uploading your own certificate files.

For detailed certificate upload instructions, see CNAME & SSL.

Required fields

• SSL Certificate Name

• Certificate format

• Domain

Supported formats:

• Domain SSL

• Paste .crt / .key

• Upload Files

• .pfx / PKCS#12

Free SSL

Provision a free Let's Encrypt certificate. See Use Free SSL Certificates

Required fields

• SSL Certificate Name

• Domain

• Coverage

  • Single Domain

  • Wildcard

Wildcard certificates require DNS (CNAME) validation.

Skip for Now

Continue without assigning a dedicated certificate.

The CDN is created using Medianova's shared SSL certificate for the default MNCDN hostname.

If you later configure a custom domain, you can assign a dedicated certificate from Settings → SSL & TLS.

5

Review & Activate

Review your resource configuration before creating the CDN resource. All settings can be modified later from the Control Panel.

The summary includes:

Section	Description
Resource	Displays the selected resource type, CDN hostname, and internal label.
Source	Shows the selected origin type, primary origin, and origin protocol.
SSL / TLS	Displays the selected certificate method and assigned certificate, if applicable.
Propagation	Shows the CDN hostname that will be provisioned and the protocol that will be served.

If the configuration is valid, a confirmation message indicates that the resource is ready to deploy.

Click Create Resource to provision the CDN resource.

New CDN resources are typically provisioned within 30 seconds.

Validate CDN Delivery

After the resource is created, verify that the CDN is serving content.

curl -svo /dev/null "https://example.mncdn.com/" --compressed

Replace example.mncdn.com with your CDN hostname or custom CNAME.

The requested URL should return HTTP 200 OK.

This command:

• Sends an HTTP GET request to the CDN endpoint.

• Displays the remote IP address.

• Displays the HTTP request and response headers.

• Discards the response body.

If validation fails:

• Verify that the origin server is reachable.

• Verify that the configured origin port is accessible.

• Verify that the requested path exists on the origin.

Troubleshooting

• Verify that the origin server is reachable from the CDN.

• Confirm that the configured origin port is open.

• Ensure DNS changes have propagated before testing a custom CNAME.

• Verify that the assigned SSL certificate matches the requested hostname.

• Confirm that the origin serves the requested content and returns the expected response.