Rate this page:

S3-compatible cloud storage

Voximplant allows developers to use custom S3-compatible cloud storage to store call and conference records.

Contents

Copy URL

How to use an S3-compatible storage

Copy URL

To use cloud storage, you need to add it to your Voximplant account and attach it to an application. To add storage:

  1. Open the Voximplant control panel.
  2. Go to SettingsS3 storages.
Control panel settings
  1. Click the Add storage button at the center of the screen or the top right corner.
Add a storage
  1. Enter your S3-compatible storage credentials and click Add.

To add new S3-compatible storage, you need the following credentials: host, region, bucket name, key_id, and secret_key.

  1. Go to the Applications section, find the necessary application, click the three dots menu, and choose Edit.
Edit an application
  1. Choose your newly created S3 storage from the dropdown list and click Save.
Attach the storage

Now all call and conference records will be saved in your custom S3-compatible storage instead of the Voximplant cloud.

How to test an S3-compatible storage before usage

Copy URL

If you need to check if your cloud storage works correctly, you can test file uploading before you start recording calls or conferences.

To test your cloud storage, log in to your control panel, go to SettingsS3 storages, and find the necessary storage. Then click on the three dots menu and choose Test.

Test the storage

This starts uploading the test to the custom storage and provides a result in a short time.

What permissions do I need on the provider side

Copy URL

To use an S3-compatible storage with Voximplant, you need to set up storage permissions on the provider side. These permissions differ depending on the provider.

Refer to the S3 storage provider documentation to find out what permissions you need and how to set them up. Here are the instructions for the most popular storage providers. If your provider is not on the list, refer to your provider's documentation.

Amazon Web Services

To set up the AWS storage provider, do the following:

  1. Create an IAM user at AWS.
  2. Create an access key for that user. Store the access and secret keys.
Warning

Save your secret key to a file, because you cannot restore it after you close the window.

  1. Grant the s3:PutObject permission to the user.
  2. Set up the storage in the Voximplant control panel with the following host: https://s3.amazonaws.com/.

For more information, refer to the Amazon AWS documentation via the links below.

Google Cloud

To set up the Google storage provider, do the following:

  1. Create a service account at Google cloud.
  2. Grant the Storage Object Creator permission to the created account in the project where the target storage bucket is.
  3. Create a HMAC key for the service account.
  4. Store the access and secret keys.
Warning

Save your secret key to a file, because you cannot restore it after you close the window.

  1. Set up the storage in the Voximplant control panel with the following host: https://storage.googleapis.com,

For more information, refer to the Google documentation via the links below.

Yandex Cloud

To set up the Yandex storage provider, do the following:

  1. Create a service account at Yandex.
  2. Create a new static access key for the service account and save it.
  3. Grant the storage → uploader role to the service account
  4. Set up the storage in the Voximplant control panel with the following host: https://storage.yandexcloud.net

For more information, refer to the Yandex documentation via the links below.

MinIO

To set up the MinIO storage provider, do the following:

  1. Create an account at MinIO
  2. Grant the readwrite or writeonly rights in the settings.
  3. Use the account's username and password as an access key and secret key in Voximplant's control panel.

For more information, refer to the MinIO documentation via the links below.

Cloud storage errors

Copy URL

When you try to access the existing records, you can get the following errors:

Error

Description

403

The link to the record is broken (Invalid URI)

401

Authorization failed

416

Requested range not satisfiable

404

File not found (e.g. the file is deleted)

When you try to access the record in the S3-compatible storage, you can get another S3-specific errors.