Overview
This document describes how to use the live stream moderation feature of COS in the console to check live streams for pornographic, illegal, and advertising information. After you enable this feature, whenever a new video stream is generated by the specified live streaming domain name, it will be moderated automatically, and you can view the real-time moderation result through the console or callback.
Restrictions
Supported live stream duration: No more than 5 hours.
Supported live stream resolutions: Up to 1920x1080 (1080p).
Supported live streaming protocols: RTMP, HLS, HTTP, HTTPS.
Directions
1. Log in to the COS console. On the Bucket List page, click the target bucket to enter the bucket details page. 2. On the left sidebar, select Sensitive Content Moderation > Automatic Moderation Configuration and click Live Stream Moderation.
3. Click Add Live Stream Moderation Configuration and set the following configuration items:
Moderation Policy: Select a moderation policy. You can create different policies for refined moderation. Moderation scene options include Pornographic, Illegal, and Advertisement, and you can select one or multiple options. For detailed directions on how to configure a moderation policy, see Setting Moderation Policy. Risk Library Associated: The risk library associated with the moderation policy.
Moderation Scene: You can select one or more scenes configured in the moderation policy, such as pornography or advertising.
Playback Domain: The playback domain name used in your live streaming business, from where video streams will be pulled for moderation.
Authentication Key: If playback authentication is configured in your live streaming business, you need to enter the authentication key corresponding to the playback domain name.
Callback: After callback is enabled, you will receive live stream moderation results. You need to select the moderation type and callback content and set the callback URL. For more information, see Live Stream Moderation Callback Content. Dedicated Callback Security Configuration: In order to ensure the security of the callback information received by CI, a default moderation authentication token will be generated to verify the source of the callback information. You can also customize the token.
4. If you already have a running live streaming business, in order to ensure that your existing push and interruption callbacks will not be affected, you need to enter existing callbacks in the configuration items. If you are launching the live streaming business for the first time, skip this step:
Original Push Callback: Enter your original "live stream push callback", and the system will forward the callback information for you.
Original Interruption Callback: Enter your original "live stream interruption callback", and the system will forward the callback information for you.
5. Click Save. The system will generate a dedicated callback address for live stream moderation. Enter this address for live stream push and interruption callbacks in your CSS product. Then, the system will automatically start and stop moderation based on the push and interruption callbacks respectively.
6. After the above steps are completed, the pushed live stream will be automatically moderated.