Upload to signed URL

This integration allows you to upload a video file to a signed URL once a rendering is done successfully. This is useful for securely uploading files to any cloud-based storage that requires authentication, without providing direct access to the storage service.

Prerequisites

The signed URL should be generated by your backend service or cloud provider, such as AWS S3. When creating the URL please make sure about the following:

• The URL must allow PUT requests.
• The URL must be valid for the duration that is large enough to complete the video rendering and the upload. In case of batch rendering, it’s advised to set longer expiry time.
• Make sure that permissions for the signed URL are set correctly to allow uploading files, and deletion if you plan to overwrite files.
• If you specify content type when generating the signed URL, then it must match the target video output format. We recommend to avoid specifying content type in the signed URL, as it will be set automatically based on the video output format.

gcloud storage sign-url gs://your-bucket-name/your-object-key.mp4 \
  --http-verb=PUT \
  --duration=60m

Setup

1. URL - provide the signed URL where the video file will be uploaded.
2. Request headers - a JSON object where you can specify additional headers that will be sent with the upload request, like Content-MD5 or x-goog-*. Includes the Content-Type header by default.

How to use a different URL for each video?

Usually you want to use different signed URLs for each video, for example to control file names or to upload to different locations. To achieve this, you should set integration passthrough when triggering the render, and it should contain the signed URL that will be used for the upload.

Then, when setting up the integration you can use the + button next to the URL field to relate to a Integration Passthrough variable that will be replaced with the value you set when the video is uploaded.