Kaltura's Remote Storage Configuration and Information Guide

Kaltura’s Remote Storage – Configuration Options

While the majority of Kaltura’s customers choose the Kaltura-hosted SaaS solution for its many benefits, some customers are required to comply with specific regulations, have unique architecture considerations, or, have other needs that propel them towards deploying parts of the solution locally in  “hybrid variations”. These variations allow customers to meet their unique requirements while providing a cost effective alternative to a fully customer-hosted solution. These variations use the Kaltura SaaS management component to manage video assets and account settings, while storage and delivery components are hosted by the customer.

This article specifies which assets can be stored and served locally, or from the customer’s own CDN, as well as few limitations that are associated with hybrid solution.

Remote Storage – What can be exported and stored on the customer’s storage of choice?

Storing the Source File

Kaltura recommends keeping the source file stored on Kaltura’s cloud (and not to export and delete it). If you choose not to do so, the following features will not be available:

  • Re- transcoding / adding new flavors –retranscoding the entry in case of any issues, or generating additional flavors (formats) in the future. If the source is kept on the remote storage, the source must be re-ingested in order to re-transcode to additional flavors . The source can then be deleted afterwards.

  • Distribution connectors - Some distribution connectors require pushing the physical file to an API or to an FTP end point. Setting up those distribution connectors won’t be possible without keeping the relevant physical files in Kaltura. 

Remote Storage Configuration Workflow

The following diagram illustrates a few of the ramifications for the chosen selections:

In This Article