Skip to main content
Skip table of contents

How to connect Glacier storage to Vidispine API-NEW [HT GEN]

Applies to 

AWS offers different kind of storages. AWS Glacier is a storage for longtime archiving where the files are not available at the same speed as the S3 bucket. Some workflow requires Vidispine API / Vidinet to connect to AWS Glacier “ long time storage “


Learn how to configure the AWS Glacier Storage with IAM permissions allowing reading and writing files using the Vidispine API

This article require the following pre-requisites and tools

  • An AWS account with the necessary administrative role to administer the required permissions

  • knowledge and understanding of AWS IAM service

  • a verified Vidispine API / Vidinet workflow

  • basic knowledge how to configure Vidispine API ( using Postman or similar )

Configuring the AWS Glacier Storage

Vidispine can archive files on Amazon Glacier. There are two different ways this can be achieved:

  • Creating a separate Glacier storage and move files from other storages there for archival.

  • Using an S3 storage and transition objects to the Glacier storage class

The XML document you should post looks like this:

<StorageDocument xmlns="">
      <value>{vault name}</value>

The rest of the details including how it relates to S3 are descrived in the API documentation for setting up Glacier.

Note, you should have a file under glassfish3/glassfish/domains/domain1 with format:

secretKey=yourkey accessKey=yourkey

How to connect Glacier storage to Vidispine

How to fix Java encryption error when adding S3 Storage to VidiCore

Configuring AWS S3 bucket policy for the AWS Elemental Media Convert service

AWS Elemental MediaConvert

How to setup auto-import rules on S3 storage

Supported transcoding presets for AWS Elemental MediaConvert

Using S3 as Storage in Vidispine

Configuring and adding a S3 bucket to VidiNet

Send VidiCore service logs to an AWS S3 bucket

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.