UnbindNlb - Serverless App Engine - Alibaba Cloud Documentation Center

Calls the UnbindNlb operation to delete an NLB listener bound for application access

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Debug

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:
- For mandatory resource types, indicate with a prefix of * .
- If the permissions cannot be granted at the resource level, All Resources is 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
sae:UnbindNlb	none	All Resources ``	none	none

Request syntax

DELETE /pop/v1/sam/app/nlb HTTP/1.1

Request parameters

Parameter	Type	Required	Description	Example
AppId	string	No	A short description of struct	7171a6ca-d1cd-4928-8642-7d5cfe69****
NlbId	string	No	The ID of NLB instance.	nlb-7z7jjbzz44d82c9***
Protocol	string	No	The type of the protocol. Valid values: TCP. UDP. TCPSSL.	TCP
Port	integer	No	The listener port of the instance. Valid values: 0 to 65535.	3306

Response parameters

Parameter	Type	Description	Example
	object	Schema of Response
RequestId	string	Id of the request	91F93257-7A4A-4BD3-9A7E-2F6EAE6D****
Message	string	The message returned. Valid values: If the request was successful, success is returned. If the request failed, an error code is returned.	success
TraceId	string	The ID of the trace. The ID is used to query the details of a request.	0a981dd515966966104121683d****
Data	object	The returned data.
ChangeOrderId	string	The ID of the change order. The ID can be used to query the status of the change task.	ba386059-69b1-4e65-b1e5-0682d9fa****
ErrorCode	string	The status code. Valid values: If the request was successful, ErrorCode is not returned. If the request failed, ErrorCode is returned. For more information, see Error codes section of this topic.
Code	string	The HTTP status code. Valid values: 2xx: The request was successful. 3xx: The request was redirected. 4xx: The request failed. 5xx: A server error occurred.	200
Success	boolean	Indicates whether the internal-facing or Internet-facing NLB instance was disassociated. Valid values: true: The NLB instance was disassociated. false: The NLB instance failed to be disassociated.	true

Examples

Sample success responses

JSONformat

{
  "RequestId": "91F93257-7A4A-4BD3-9A7E-2F6EAE6D****",
  "Message": "success",
  "TraceId": "0a981dd515966966104121683d****",
  "Data": {
    "ChangeOrderId": "ba386059-69b1-4e65-b1e5-0682d9fa****"
  },
  "ErrorCode": "",
  "Code": 200,
  "Success": true
}

Error codes

For a list of error codes, visit the Service error codes.