Deletes the configuration of edge node stream relay.
Operation description
You can call the DeleteLiveEdgeTransfer operation to delete the configuration of edge node stream relay for a specific domain name. Ingested streams that are relayed based on the configuration are not affected. The following table describes the scenarios in which edge node stream relay takes effect or not.
| Scenario | Analysis | Result |
|---|---|---|
| 1. You ingest a stream after you call the SetLiveEdgeTransfer operation to configure edge node stream relay. Then, you call the DeleteLiveEdgeTransfer operation to delete the configuration. | The configuration of edge node stream relay is available when you ingest the stream. | The ingested stream is not affected, and stream relay is not interrupted. |
| 2. You call the DeleteLiveEdgeTransfer operation to delete the configuration of edge node stream relay after you ingest a stream. Then, you disconnect and resume the ingested stream. | The configuration of edge node stream relay is not available after you resume the ingested stream. | Edge node stream relay does not take effect. |
| 3. You call the DeleteLiveEdgeTransfer operation before you ingest a stream. | The configuration of edge node stream relay is not available. | Edge node stream relay does not take effect. |
QPS limit
You can call this API operation up to 100 times per second per account. Requests that exceed this limit are dropped and you will experience service interruptions. We recommend that you take note of this limit when you call this operation. For more information, see QPS limit on an API operation in ApsaraVideo Live.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resourcesis used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
| Operation | Access level | Resource type | Condition key | Associated operation |
|---|---|---|---|---|
| live:DeleteLiveEdgeTransfer | delete | *All Resources * |
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| DomainName | string | Yes | The ingest domain. Only one stream relay configuration can be set for an ingest domain. | demo.aliyundoc.com |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "16A96B9A-F203-4EC5-8E43-CB92E68F4CD8"
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | InvalidParam | Parameter invalid. | Illegal input parameters |
| 500 | InternalError | The request processing has failed due to backend service exception. | - |
For a list of error codes, visit the Service error codes.