CreateHoneypotProbeBind - Security Center - Alibaba Cloud Documentation Center

Creates a monitoring or forwarding service for a probe.

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:
- The required resource types are displayed in bold characters.
- 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
yundun-sas:CreateHoneypotProbeBind	create	All Resources *	none	none

Request parameters

Parameter	Type	Required	Description	Example
ProbeId	string	No	The probe ID. Note You can call the ListHoneypotProbe operation to query the IDs of probes.	36bad711-d1ac-4419-ac68-c1aa280f****
HoneypotId	string	No	The honeypot ID. Note You can call the ListHoneypot operation to query the IDs of honeypots.	dba7d44775be8e0e5888ee3b1a62554a93d2512247cabc38ddeac17a3b3f****
ServiceIpList	array	No	The IP addresses that are monitored.
ServiceIpList	string	No	The IP address that is monitored.	0.0.0.0
BindPortList	array<object>	No	The ports that are bound to the probe.
BindPortList	object	No
TargetPort	integer	No	The destination port.	8080
StartPort	integer	No	The start port on which the probe monitors.	80
EndPort	integer	No	The end port on which the probe monitors.	80
Fixed	boolean	No	Specifies whether the port is a fixed port. Valid values: true false	false
BindPort	boolean	No	Specifies whether to bind the port. Valid values: true false	false
Proto	string	No	The type of the protocol. Valid values: tcp udp	tcp
Lang	string	No	The language of the content within the request and response. Default value: zh. Valid values: zh: Chinese en: English	zh

Response parameters

Parameter	Type	Description	Example
	object	The returned data.
Success	boolean	Indicates whether the request was successful. Valid values: true false	true
Code	string	The response code. The status code 200 indicates that the request was successful. Other status codes indicate that the request failed. You can identify the cause of the failure based on the status code.	200
Message	string	The returned message.	successful
RequestId	string	The request ID.	E10BAF1C-A6C5-51E2-866C-76D5922E****
HttpStatusCode	integer	The HTTP status code that is returned.	200

Examples

Sample success responses

JSONformat

{
  "Success": true,
  "Code": "200",
  "Message": "successful",
  "RequestId": "E10BAF1C-A6C5-51E2-866C-76D5922E****",
  "HttpStatusCode": 200
}

Error codes

HTTP status code	Error code	Error message	Description
400	BindPortAlreadyExist	The specified service port already exists.	-
403	NoPermission	caller has no permission	You are not authorized to do this operation.
500	ServerError	ServerError	-

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

Change history

Change time	Summary of changes	Operation

No change history