Use the TokBox Account to specify your own Amazon S3 bucket or Windows Azure container for completed archives to be uploaded to. (For more information on Amazon S3 see Using an Amazon S3 bucket with OpenTok archiving.)
You can create a Windows Azure account at
You will provide the following information to the TokBox Account:
- Your Azure account name
- Your Azure account key
- The container name
You can create an Azure container (or find names of existing containers) at the
Windows Azure portal. (See
this Microsoft documentation on creating an Azure storage account.
To obtain an Account Key:
At the Windows Azure portal, click
All Resources on the left-hand menu.
Click the storage account that you want to use for OpenTok archives,
and then click the Settings button.
Click Keys in the right-hand side of the page.
Make a record of the storage account name and one of the access keys (either
the primary access key or the secondary access key).
Click the Blobs button and record the blob (storage container) name
you will use to store OpenTok archives.
Now, log in to your TokBox Account
and complete the following steps:
Click on a Projects in the left nav that will contain sessions that you are archiving.
Click the Project Archives tab.
In the Archiving section, click the Set up your cloud storage now button, and then click on Micorsoft Azure.
Enter the following:
Account name — The Windows Azure storage account name
Account key — The Windows Azure storage account access key
Container — The Windows Azure blob (storage container) name
Then click the Connect to cloud storage button.
Note: You can also set an archive upload target using the
OpenTok REST API.
Recorded archives are uploaded to the Windows Azure container you specify.
All archives are saved to a subdirectory of your Azure container that has your OpenTok API
key as its name, and each archive is saved to a subdirectory that has the archive ID as its
name. The name of the archive file is archive.mp4 (for a composed archive) or archive.zip
(for an individual stream archive). (See
stream and composed archives.)
For example, consider an archive with the following API key and ID:
- API key -- 123456
- Archive ID -- ab0baa3d-2539-43a6-be42-b41ff1488af3
The file for this archive is uploaded to the following directory in your Azure container: