You can upload media files from application servers to OSS buckets allocated by ApsaraVideo VOD. This method is suitable for scenarios where you require automated upload or want to upload a large amount of video files or network media files. To upload network media files, you must download the files to an application server and then upload the files from the application server. This topic describes the features, process, prerequisites, and three methods for uploading files from servers.
You can upload multiple types of media files including video, audio, and image files from local application servers or over the Internet. The following features are provided:
- Upload local audio or video files: By default, multipart upload is used. A single file to upload can be up to 48.8 TB in size. Resumable upload is supported.
- Upload network audio or video files: After you specify the URL of a file, the system automatically downloads the file from the URL and uploads it. A single file to upload can be up to 5 GB in size.
- Upload local images: After you specify the path of a local file, the system automatically uploads the file.
- Upload network images: After you specify the URL of a file, the system automatically downloads the file from the URL and uploads it.
- Upload progress bar: You can configure default and custom progress callbacks.
- For other upload settings, see Overview.
The following figure shows the process of uploading files from servers.
- An Alibaba Cloud account is created on the Create Your Alibaba Cloud Account page, real-name verification is completed, and ApsaraVideo VOD is activated.
- An AccessKey pair to access ApsaraVideo VOD is obtained. You can create an AccessKey
pair for your Alibaba Cloud account on the AccessKey Management page in the Alibaba Cloud Management Console. Alternatively, you can create a RAM
user in the RAM console and grant the user the permission (such as
AliyunVODFullAccess) to access ApsaraVideo VOD. For more information, see Create and grant permissions to a RAM user.
To upload media files from application servers, you can deploy upload scripts on the servers, use server upload SDKs or OSS SDKs, or call upload API operations.
Use server upload SDKs
ApsaraVideo VOD provides server upload SDKs and demos of how to use them. Server upload
SDKs encapsulate the logic to obtain upload URLs and credentials so that you do not
need to obtain them separately. You need only to specify the AccessKey pair (
AccessKeySecret) and the file URL to upload a file.
The following SDKs are provided:
Use OSS SDKs
ApsaraVideo VOD does not provide server upload SDKs for all programming languages. If the server upload SDK for a programming language is unavailable, you can use OSS SDKs. You can perform the following steps to upload files by using OSS SDKs:
- Access ApsaraVideo VOD and obtain the upload URL and credential. For more information,
see Upload URLs and credentials.
Note Information about the media file and a media ID (such as a video ID or an Image ID) are returned in this step. Keep the media ID for subsequent operations such as video playback, management, and AI processing.
- Decode the upload URL (UploadAddress) and upload credential (UploadAuth) in Base64 to obtain the URL and credential for uploading the media file to OSS. For more information, see Upload URLs and credentials.
- Use an OSS SDK to upload the media file to the specified bucket. In this case, use
STS Authmethod and use UploadAddress and UploadAuth for initialization. Do not use your AccessKey pair.
In addition to OSS SDKs for Java, Python, and PHP, the following OSS SDKs are provided:
- OSS SDK for .NET: Installation.
- OSS SDK for Go: Installation.
- OSS SDK for Ruby: Installation.
- OSS SDK for C: Installation.
For more information about OSS SDKs for major programming languages, see Introduction. For more information about how to use OSS SDKs to upload media files, see Upload videos by using the OSS native SDK.
Call API operations (not recommended)
You can use ApsaraVideo VOD and OSS APIs to upload media files by following procedures similar to those used when OSS SDKs are used for uploads. The only difference is that in Step 3, you must use OSS API to complete the upload. For more information, see Upload OSS objects.