ApsaraVideo VOD:Overview of the multi-application service

Procedure

If you have activated ApsaraVideo VOD, you can perform the following steps to use the multi-application service:

1. Apply for activation

2. Create an application

3. Grant permissions to the identity entity

4. Upload media assets

5. Manage media assets for each application separately

Or:

1. Apply for activation

2. Create an application

3. Grant permissions to the identity entity

4. Configure callbacks

5. Configure callbacks for each application separately

Apply for activation

• Prerequisites

  The multi-application service is in the public preview stage and unavailable in the ApsaraVideo VOD console. Before you apply to activate the multi-application service, make sure that the following requirement is met:

  The peak bandwidth for acceleration traffic in the last seven days is 500 Mbit/s or higher. To view the peak bandwidth, go to the Resource Consumption page in the ApsaraVideo VOD console.

• Impacts

  • Online services may be affected when you disable the default application. Do not disable the default application.

  • Only the resources of the default application can be managed or queried in the ApsaraVideo VOD console. The resources include media assets, reviews, and media processing configurations.

  • For new applications, you must call API operations to configure transcoding and callbacks.

  Note

  • If you want to test the callback feature, you can specify callback URLs in different environments when you upload media assets.

  • If you want to isolate media assets, you can use the media asset category module.

• Activation method

  If you meet the requirements to activate the multi-application service and accept the preceding impacts, submit a ticket.

  Note

  You must include your Alibaba Cloud account ID in the application and declare that you acknowledge and accept the impacts of activating the multi-application service.

Create an application

You can call the CreateAppInfo operation to create applications. Up to 10 applications can be created within a single account. Application names must be unique. For more information, see Create an application.

Grant permissions to the identity entity

You can call the AttachAppPolicyToIdentity operation to grant permissions to an identity entity before the identity entity can manage resources in applications. The identity entity is a RAM user or role. For more information, see AttachAppPolicyToIdentity. For more information about the policies, see Overview.

Use the multi-application service

The AppId parameter is added for services that support the multi-application service. You can specify this parameter when you create resources or add settings. When you query data, only resources in the applications that you are authorized to access are returned. When you modify or delete data, permissions must be verified before you can proceed.

Only callbacks and media asset services support the multi-application service. The media asset services include media asset uploads, playback, and management.

• Callbacks

  You can set a separate callback method and URL for each application. You can use the AppId parameter in the SetMessageCallback operation.

  • If the AppId parameter is specified, you can configure callbacks for the application.

  • If the AppId parameter is not specified, the default application is used.

  After the settings are complete, callbacks are performed for event notifications for video and image uploads in different applications based on the settings. You can also call the GetMessageCallback operation to query related settings.

  Note

  After you activate the multi-application service, you can manage the callback configurations only for the default application in the ApsaraVideo VOD console. The ApsaraVideo VOD console will be updated to allow you to manage the callback configurations for the other applications.

• Media asset operations

  • Media upload: If you have access permissions on a specific application, you can specify the AppId parameter in upload operations such as CreateUploadVideo and CreateUploadImage to upload media files to the application. If you do not have access permissions on the application, the upload fails. If you leave the AppId parameter empty, media files are uploaded to the default application.

  • Media playback: You can obtain playback information such as playback credentials and URLs only from applications on which you have access permissions.

  • Media modification and deletion: You can modify and delete only the media assets in applications on which you have access permissions.

  • Media query: When you call API operations to query the details of media assets, you can obtain only information about media assets in applications on which you have access permissions. Batch queries return only the data of media assets in applications on which you have access permissions. The IDs of media assets in applications on which you do not have access permissions are displayed in the NonExistMediaIds field. The name of the field may vary.

  • Media search: You can specify one or more application IDs to search for media assets. Only the data of media assets in applications on which you have access permissions is returned.

  Note

  After you activate the multi-application service, you can manage only media assets in applications on which you have access permissions in the ApsaraVideo VOD console. Management of other applications will be supported in the future.

FAQ

For more information about commonly asked questions and solutions that are related to the usage of the multi-application service, see FAQ.