On this page

Getting Started with Qencode S3


Getting starting with Qencode Media Storage

Outcome Upon completing this tutorial, you'll be able to configure a destination object to save files to Qencode Media Storage, with an understanding of the URL structure and optional security parameters.

Accessing Files via HTTP

To access your files via HTTP, use the format:


For the example above, it would be:


Supported Protocols

s3://S3 Protocol

Destination Object Structure

"destination": {
  "url": "s3://[region].s3.qencode.com/bucket/path"
  • Note: Specifying key and secret parameters for destination object is optional when saving outputs to Qencode Media Storage. It’s recommended not to provide the key and secret in the destination object, as this enhances the security of your integration.Saving to Qencode Media Storage: Details and Examples

URL Structure for Qencode S3

The Qencode S3 url consists of bucket, path, and region.


Components of URL
regionChoose between us-west or eu-central.
bucketYour specific bucket name.
pathPath within your bucket where the file will be saved.

Destination Object Example

"destination": {
  "url": "s3://us-west.s3.qencode.com/my-bucket/folder/output.mp4"

When saving ABR outputs like HLS or DASH, please specify the path to a folder where the contents of the HLS or DASH stream should be located:

"destination": {
  "url": "s3://us-west.s3.qencode.com/my-bucket/folder"

Considerations for S3 Storage

  • Service Selection: Different S3-compatible services may offer varying features and pricing models.

  • Security and Access Control: Manage your keys and access permissions appropriately.

  • Connectivity Issues: Ensure the endpoint, bucket name, and path are correctly specified in the URL.

  • Authentication Errors: Double-check your access and secret keys for accuracy.

  • Explore advanced functionalities and integration possibilities of your chosen S3-compatible service.