All Products
Search
Document Center

Security Center:UpdateHoneypotProbeBind

Last Updated:Nov 14, 2024

Modifies a probe service.

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.

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.
OperationAccess levelResource typeCondition keyAssociated operation
yundun-sas:UpdateHoneypotProbeBindupdate
  • All Resources
    *
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
IdlongNo

The port ID of the probe service.

1906
ProbeIdstringNo

The probe ID.

Note You can call the ListHoneypotProbe operation to query the IDs of probes.
36bad711-d1ac-4419-ac68-c1aa280f****
BindIdstringNo

The unique ID of the honeypot to which the probe is bound.

f52e8624-e43c-473c-8312-e0fed384****
BindTypestringNo

The operation that the probe performs. Valid values:

  • forward_honey: forward traffic to a honeypot
  • scan_port: monitor and scan
forward_honey
HoneypotIdstringNo

The honeypot ID.

Note You can call the ListHoneypot operation to obtain the IDs of honeypots.
dba7d44775be8e0e5888ee3b1a62554a93d2512247cabc38ddeac17a3b3f****
ServiceIpListarrayNo

The IP addresses that are monitored.

ServiceIpListstringNo

The IP address that is monitored.

0.0.0.0
PortsstringNo

The ports that are monitored.

{\"tcp\":\"1-65535\",\"udp\":\"1-65535\"}
SetStatusintegerNo

The status of the port.

0
BindPortListarray<object>No

The ports that are bound to the probe.

BindPortListobjectNo
IdlongNo

The UUID of the port.

3183
TargetPortintegerNo

The destination port.

80
StartPortintegerNo

The start port on which the probe monitors.

81
EndPortintegerNo

The end port on which the probe monitors.

81
FixedbooleanNo

Specifies whether the port is fixed. Valid values:

  • 0: no
  • 1: yes
0
BindPortbooleanNo

Specifies whether to bind a port. Valid values:

  • true
  • false
false
ProtostringNo

The type of the protocol. Valid values:

  • tcp
  • udp
tcp
LangstringNo

The language of the content within the request and response. Valid values:

  • zh: Chinese
  • en: English
zh
CurrentPageintegerNo

The page number. Pages start from page 1. Default value: 1.

1
PageSizeintegerNo

The number of entries per page. Default value: 20. If you leave this parameter empty, 20 entries are returned per page.

Note We recommend that you do not leave this parameter empty.
20

Response parameters

ParameterTypeDescriptionExample
object

The response parameters.

Successboolean

Indicates whether the request was successful. Valid values:

  • true
  • false
true
Codestring

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
Messagestring

The returned message.

successful
RequestIdstring

The request ID.

425D9617-4F4F-571E-A9CF-0245C9FC****
HttpStatusCodeinteger

The HTTP status code.

200

Examples

Sample success responses

JSONformat

{
  "Success": true,
  "Code": "200",
  "Message": "successful",
  "RequestId": "425D9617-4F4F-571E-A9CF-0245C9FC****",
  "HttpStatusCode": 200
}

Error codes

HTTP status codeError codeError messageDescription
400ProbeNotExistProbe does not exist.-
400BindPortAlreadyExistThe specified service port already exists.-
403NoPermissioncaller has no permissionYou are not authorized to do this operation.
500ServerErrorServerError-

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

Change history

Change timeSummary of changesOperation
2023-10-07The Error code has changedView Change Details