Amazon Elastic Transcoder

Provider Type ID: aws

Amazon Elastic Transcoder can be configured in Cloud CMS in association with your S3 storage. Before configuring here, be sure that you have an S3 bucket configured and at least one transcoder pipeline setup.


The following options can or must be specified for a transcoding:

Property Type Default Read-Only Description
pipelineId string ID of the transcoder pipeline to use for this transcoding. You can find this in your AWS Management Console.
presetIds array Array of strings. Each string is the ID of a preset, defining how a transcoding is to be performed. You can define your own preset in the AWS Management Console, or use one of the System Presets.
inputPropertyName string inputKey (Optional) Name of a property in your content model which will contain an S3 file path. This file will be used as the input for transcoding.
outputPropertyName string outputKeys (Optional) Name of a property in your content model which will contain a list of S3 file paths. These paths are where transcoding outputs will be located, and the number of outputs should be the same as the number of preset ids provided.

Setup with Service Descriptor

  1. Login with a user with Manager rights over the platform.

  2. Select Manage Platform at the top, and then Services from the left menu.

  3. Click the "Add a Service Descriptor" button a the top of the page.

  4. A popup should appear, allowing you to configure your new descriptor. Give your descriptor a title and a unique key, set the Descriptor Type to "Amazon Elastic Transcoder" and Descriptor Family to "Transcoder Service".

  5. Configure the accessKey, secretKey, region, and bucketName properties for your descriptor. The form should look something like this:

  1. Click "Create", and your Amazon Elastic Transcoder will be usable in Cloud CMS.

Setup in API

If you have an onsite installation of Cloud CMS, you can configure Amazon Elastic Transcoder directly in the API. To do this:

  1. Edit the file gitana/gitana-platform-aws/src/main/resources/

  2. Ensure the following properties are set:

  3. Save, rebuild, and restart your API.