Create a Bitmovin OCI Object Storage Output

To create a Bitmovin OCI output configuration for use with the encoding service, gather the credentials and storage details above.

Use the Dashboard UI

Select the Encoding menu on the left and go to Outputs
Click on Create in the upper right corner of the Outputs overview
Select OCI Object Storage as the Output type
Enter all required fields:
1. Name: A descriptive name for this output
2. Description: An optional description
3. Namespace: Your Object Storage namespace
4. Bucket Name: Your OCI bucket name
5. Access Key: Your Customer Secret Key access key
6. Secret Key: Your Customer Secret Key secret key
7. Region: The OCI region where your bucket resides (e.g. us-ashburn-1)
8. Click on Create
Click on Create

Use a Bitmovin API SDK

Each of our Open API SDKs implements the Bitmovin API, making it easy to integrate with your project. Use the SDKs to create reusable output resources for your encodings.

Bitmovin API SDK - Output example:

  const output = new GenericS3Output({
    name: "my-oci-output-ts",
    bucketName: BUCKET_NAME,
    accessKey: ACCESS_KEY,
    secretKey: SECRET_KEY,
    host: `${NAMESPACE}.compat.objectstorage.${REGION}.oraclecloud.com`,
    ssl: true,
    port: 443,
    signatureVersion: S3SignatureVersion.V4,
  });

  console.log("Sending request to Bitmovin API...");
  const createdOutput =
    await bitmovinApi.encoding.outputs.genericS3.create(output);

See all available examples for each of our Bitmovin API SDKs in our GitHub Example Repository.

Using the Output in an Encoding

const encodingOutput = {
  outputId: 'YOUR_OCI_OUTPUT_ID',  // The ID returned when you created the output
  outputPath: '/my-encoding-job/output/'
};

OCI CDN vs. OCI Object Storage

Bitmovin outputs encoded files directly to OCI Object Storage, not to OCI CDN or any edge distribution layer.

To serve content via OCI CDN, configure your CDN origin to pull from the Object Storage bucket after encoding is complete. This is outside the scope of Bitmovin configuration and is managed through your OCI CDN settings.

Common Issues

Authentication failure on encoding:
The most common cause is an incorrectly formatted private key or mismatched fingerprint. Ensure the private key is in PEM format, includes the -----BEGIN RSA PRIVATE KEY----- header and footer, and corresponds to the fingerprint registered in OCI. Copy values directly from the OCI Console without introducing extra whitespace or line breaks.
Region mismatch error:
The region specified in your Bitmovin output configuration must exactly match the region where your OCI bucket resides. Using a region identifier in the wrong format (e.g., us-ashburn-1 vs iad) may cause resolution failures.
File transfer failure with special characters:
Filenames containing spaces or special characters (e.g., ProRes 8 channels.mov) may cause transfer failures. Best practice: use only alphanumeric characters, hyphens, and underscores in output paths and filenames.
Insufficient IAM permissions:
The OCI user associated with the API key must have the appropriate IAM policies to write objects to the bucket. Ensure a policy such as Allow group to manage objects in compartment where target.bucket.name='' is in place.

Setting up OCI Object Storage Output