Deletes a listener.
Operation description
- You can call this operation up to 100 times per second per account.
- You can call this operation up to 10 times per second per user.
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 |
|---|---|---|---|---|
| ens:DeleteLoadBalancerListener | delete | *All Resources * |
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| ListenerPort | integer | Yes | The frontend port that is used by the Edge Load Balance (ELB) instance. Valid values: 1 to 65535. | 8080 |
| LoadBalancerId | string | Yes | The ID of the ELB instance. | lb-5snthcyu1x10g7tywj7iu**** |
| ListenerProtocol | string | No | The frontend protocol that is used by the ELB instance. Note
This parameter is required if the same port is used by listeners that use different protocols.
Valid values:
| tcp |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "473469C7-AA6F-4DC5-B3DB-A3DC0DE3C83E"
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | ens.interface.error | An error occurred while call the API. | - |
| 400 | Invalid%s | The specified parameter %s is invalid. | - |
| 400 | Missing%s | You must specify the parameter %s. | - |
| 400 | LoadBalancerNotFound | The input parameter loadBalancerId that is not found. | The load balancing instance does not exist. |
| 400 | IncorrectInstanceStatus | The current status of the resource does not support this operation. | The current operation is not supported. The disk is being reset. |
| 400 | ListenerNotFound | The input parameter listener that is not found. | - |
| 400 | IncorrectListenerStatus | The current status of the resource does not support this operation. | The listener status is incorrect. |
| 400 | TooManyListeners | More than 1 listener is found, please be more specified. | - |
| 400 | NoPermission | Permission denied. | - |
| 400 | InvalidParameter.%s | The specified field %s invalid. Please check it again. | - |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|
No change history