Configuration Item | Required | Configuration Description |
Trigger type | - | By default, "Tencent Cloud COS" is selected, indicating that the bucket that triggers the orchestration belongs to Tencent COS. When "AWS" is selected, the trigger bucket belongs to AWS S3. This option can be selected if the bucket is configured on AWS services. Refer to Using Amazon S3 Buckets with MPS for detailed information. |
Orchestration name | Yes | You can enter a combination of letters, digits, underscores, and hyphens (_). The length cannot exceed 128 characters. Example: "MPS". |
Trigger bucket | Yes | You can select a bucket created under this APPID as the trigger bucket. Once the orchestration is enabled, video file upload to this bucket will automatically trigger the orchestration execution. |
Trigger directory | No | The directory should end with a forward slash (/). If left unspecified, all directories of the trigger bucket can trigger the orchestration execution. |
Output bucket | Yes | By default, the output bucket is the same as the trigger bucket. You can also select another bucket in the same region corresponding to the specified APPID as the output bucket. Newly generated video files will be stored in the selected bucket once the service orchestration is completed. |
Output directory | No | The directory should end with a forward slash (/). If left unspecified, the trigger directory will be taken as the output directory. |
Enable event notifications | - | Once enabled, the transcoding process and result data will be sent through the selected notification method. |
Off-peak transcoding | - | If this feature is enabled, initiated transcoding tasks will be executed during off-peak hours of resource usage. The timeliness of the transcoding process dynamically changes based on Tencent Cloud's resource utilization. (High timeliness of transcoding cannot be guaranteed.) If this feature is enabled, the transcoding costs will be billed according to the billing logic of "off-peak transcoding packs" or off-peak transcoding, which is different from that of non-off-peak transcoding. For more details, please refer to the General Transcoding Resource Pack, TSC Transcoding Resource Pack, Off-Peak General Transcoding Resource Pack, and Off-Peak TSC Transcoding Resource Pack sections in relevant documents. This feature applies to scenarios involving massive file processing with low requirements for real-time transcoding. |
Actions | - | You can quickly build a process by defining process nodes and templates of the service orchestration. |
Associate Resource | No | This configuration option will only appear if cost allocation has been enabled in the General Management > General Settings.
After resources are associated, cost allocation can be performed for the bill related to this orchestration based on the resource-bound tags. If you need to modify resources, go to Cost Allocation Management. |
Callback Type | Configuration Description |
TDMQ-CMQ callbacks | To enable TDMQ-CMQ callback, go to the TDMQ console to activate the CMQ service and create a model. Once enabled, the specified CMQ service will receive event notifications from MPS. You need to fill in the following information: TDMQ-CMQ model: Queue model is selected by default. TDMQ-CMQ region: You can select Guangzhou, Shanghai, Beijing, Shanghai Finance, Shenzhen Finance, Hong Kong (China), Chengdu, North America, or West US. Queue name: Custom. |
HTTP callbacks | When calling the event notification configuration API TaskNotifyConfig, specify the NotifyType parameter to URL and fill in the HTTP callback address in the NotifyUrl parameter. |
SCF callbacks | 1. SCF can rapidly process and operate on callback events triggered by MPS. The overall data processing workflow is shown in the following figure: 2. Events are sent to SCF through the MPS trigger. SCF adopts a serverless architecture and can process and respond to callback events. 3. You can click Go to SCF console to configure a function. For specific configuration method, please refer to MPS Task Callback Notification. Note: The SCF callback configuration applies to all orchestrations but is not saved specifically for the current orchestration. Corresponding computing fees will incur after the data is sent to SCF. For more information, refer to Billing Overview. |
Was this page helpful?