Process video straight from your S3 bucket
Rendobar reads job inputs from your bucket and writes every output back to it. A CloudFormation stack creates the IAM role it uses, so no access key is stored.
Overview
Jobs read objects in the bucket as storage:// paths and deliver outputs to a folder you name. The IAM role can get, put and list objects and has no delete permission, and Read only also removes write access. The dashboard creates the role with one CloudFormation stack, and the S3 docs cover Terraform, access keys and encrypted buckets.
Questions
Can Rendobar delete files in my S3 bucket?
No. The role can get, put and list objects, abort an unfinished multipart upload, and read bucket names and regions in the account. None of that deletes.
Why does an S3 input link stop working after an hour?
The role session that signed the link caps it. The stack sets the role's maximum session to 12 hours, but a role you made by hand with AWS's default one-hour maximum gives jobs input links that last one hour.
Can I connect S3 with access keys instead of a role?
Yes. Create an IAM user with the policy the connect dialog shows under IAM policy for this bucket, then pick Access keys and paste the key pair. Use it when you can't create stacks, or when one-click connect doesn't reach the bucket's region.
How do I revoke Rendobar's access to S3?
Delete the stack in CloudFormation. That deletes the role, and Rendobar removes the connection. The OpenID Connect provider and any bucket the stack created stay in your account.
Related
- Cloudflare R2 Keep your media in R2 and process it without moving it first.
- Supabase Storage Process files in your Supabase bucket and land the results next to them.
- S3-compatible Point Rendobar at MinIO, Wasabi, Backblaze B2 or any bucket that speaks S3.
