Archiving a Live Event (Server-Side Archiving)

Both Encrypted HLS and Encrypted Key Rotation are incompatible with Server-Side Archiving.

A live event can be recorded as it is being streamed and then archived to CDN storage. This process is known as Server-Side Archiving (SSA). This allows a live event to be streamed as on-demand content.

In this topic, we will learn:

Server-Side Archiving Activation

The Server-Side Archiving capability must be activated on the desired instance before the live streams generated from it will be archived. This feature can be activated by marking the Enable SSA option when creating an instance.

The Enable SSA option is only available when the Server-Side Archiving feature has been activated on your account. If this option is not available when creating an instance, please contact your CDN account manager to activate this feature.

If SSA has been enabled on an instance, then all of its live streams will be automatically archived.

Archived Content

If a live stream is being published to an instance on which SSA has been enabled, then a new file will be generated whenever any of the following conditions are true:

A live event is always archived as an MP4 file.

It typically takes approximately 15 minutes to generate archived content. However, longer live events may experience a delay.

Storage Location

This file will be stored in CDN storage within a folder named after the live event's instance name. This folder is located in the root folder of your CDN storage account.

For example, if you set your encoder to output encoded media to:

Then the live stream would be archived to the following relative path on CDN storage:


Manage content stored on CDN storage via a third-party FTP client.

Naming Convention

The naming convention for archived content is described below.