All Products
Search
Document Center

Security Center:UpdateHoneypotNode

Last Updated:Nov 13, 2024

Modifies the configuration of a specified management node.

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:UpdateHoneypotNodeupdate
  • All Resources
    *
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
NodeNamestringYes

The name of the management node.

HoneypotNodeTest
NodeIdstringYes

The ID of the management node.

Note You can call the ListHoneypotNode operation to query the IDs of management nodes.
67ab3f4c-3db5-4fc3-b51f-00f8bfabfa08
SecurityGroupProbeIpListarrayNo

The CIDR blocks that are allowed to access the management node.

stringNo

The CIDR block that is allowed to access the management node.

10.0.0.0/24
AvailableProbeNumintegerYes

The number of available probes.

20

Response parameters

ParameterTypeDescriptionExample
object

The data returned.

Successboolean

Indicates whether the request was successful. Valid values:

  • true: The request was successful.
  • false: The request failed.
true
Codestring

The status code returned. 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 message returned.

successful
RequestIdstring

The ID of the request, which is used to locate and troubleshoot issues.

753D92B3-A062-544F-8E7B-C813AA9FA9FC
HttpStatusCodeinteger

The HTTP status code returned.

200

Examples

Sample success responses

JSONformat

{
  "Success": true,
  "Code": "200",
  "Message": "successful",
  "RequestId": "753D92B3-A062-544F-8E7B-C813AA9FA9FC",
  "HttpStatusCode": 200
}

Error codes

HTTP status codeError codeError messageDescription
400InvalidParamThere was an error with your request.An error occurred while processing your request. Try again later.
400NeedBuyThis service shoule be purchased first.-
400AuthorizedProbeCannotReduceThe number of authorized probes cannot be reduced.-
400InvalidProbeNumInvalid number of probes.-
400ProbeNumInsufficientThe number of probes remaining is insufficient.-
400NodeNotExistThe control node does not exist.-
403NoPermissioncaller has no permissionYou are not authorized to do this operation.
500ServerErrorService error, please try again later.-
500ServerErrorServerError-

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