1. Home
  2. Integrations
  3. AWS S3 upload credentials

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:

  • In the left panel menu, click to expand “Publication settings”;
  • Click “Upload credentials”
  • Click “New key”


Admin permissions required

Admin permissions are required to manage S3 access keys. If you lack the necessary permissions please contact your account’s admin user or send an email to support@bluebillywig.com.

  • Enter a “Label”. The label cannot contain contain empty characters
  • Click “save” in the right lower corner to generate the S3 upload credentials in AWS. This process can take up to 10 seconds.

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

Secret access key only shown once

Please note that S3 secret access keys are only shown once due to security purposes. As these security access keys are inaccessible for Blue Billywig as well, new credentials need to be generated all together when lost

  • 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 existing upload credentials:

  • 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;

Was this article helpful?

Related Articles

Contact Support
Can't find the answer you're looking for?
Contact Support