AWS S3 upload credentials

Blue Billywig uses AWS S3 to store all files on your account. The Online Video Platform (OVP) provides an easy-to-use interface for uploading video and audio content, however, it’s also possible to programmatically upload content directly to your account’s S3 bucket using a library or SDK of your own choosing (see AWS upload SDK documentation).

Regardless of the selected implementation, the following details will be required:

• S3 access key id;
• S3 secret access key;
• S3 bucket name

1.0 | Create S3 Upload Credentials

To generate the required S3 upload credentials:

• Go to the Publication settings;

• Select “Upload Credentials” in the left menu panel and click “ + New Key”;

• Enter the key “Label” (the label cannot contain contain empty characters).
• Clicking “save” in the right lower corner will trigger the S3 upload credentials to be generated in AWS. This process can take up to 10 seconds.

• A popup will appear displaying a new secret access key.

• Click “OK” to access the AWS access key id and the S3 bucket url:

2.0 | Edit / Delete S3 Access Keys

2.1 | Edit S3 Upload Credentials

To edit existing upload credentials:

• Click the ‘edit’ icon in the credentials library:

• Change the label of the existing access key and click “save”

2.2 | Delete S3 Upload Credentials

To delete upload credentials, simply click the ‘trash can’ icon in the credentials library:

3.0 | AWS Key Management: Best Practices

Proper access key management is recommended to keep your account secure. We would specifically recommend the following best practices:

• Create separate AWS upload credentials for each implementation;
• To avoid exposure to the public, beware not to embed upload credentials directly in your code or to store upload credentials in files that are part of your application’s source tree.
• Delete unused upload credentials;
• Periodically renew upload credentials;