Introducing Stored Transfer Credentials

Today we’re announcing public availability of stored transfer credentials, a new feature that makes it easier to manage login information and access to the servers and services you use with Zencoder. Before credentials you had to provide login information in the input and output URLs of your API requests or set up an S3 bucket policy so we could get your videos and put the new outputs back. Now you can securely store your credentials with Zencoder and remove it from the API request, simplifying access management and keeping passwords private. It works with all of our current file transfer options, and introduces some new capabilities that users have been asking for. This is a new way of of allowing Zencoder to access your files – if you’re already set up and don’t want to change anything you can continue using your existing implementation with no worries.

Adding credentials to your account is a quick process. Just create a new credential and decide if you want it to be the default for a compatible protocol. You could set a default S3 user and no longer need to worry about setting up a bucket policy when you make a new bucket again, or specify the FTP account you want to use by its nickname.

The release of credentials also allows for a few new things that we’ve seen a lot of requests for from our users. Using S3 credentials means that we’re using your account to write the files to your bucket, not ours, and that means that your account is the owner of the file, with full rights and control over the file. And using SSH credentials means you can provide an SSH key for access to your SFTP server, rather than relying on a user name and password.

Credentials are stored using AES 256 encryption, so they’re safe and secure. For added protection, we recommend creating a unique account just for Zencoder, with access only to the files and directories it needs.

You can read more about using credentials in our documentation. They can be used on inputs and outputs.

blog comments powered by Disqus