CreateHoneypot - Security Center - Alibaba Cloud Documentation Center

Creates a honeypot.

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:CreateHoneypot	create	All Resources ``	none	none

Request parameters

Parameter	Type	Required	Description	Example
HoneypotImageName	string	Yes	The name of the honeypot image. Note You can call the ListAvailableHoneypot operation to query the names of images from the HoneypotImageName response parameter.	HoneyPotImageName
HoneypotName	string	Yes	The custom name of the honeypot.	ruoyi
NodeId	string	Yes	The ID of the management node. Note You can call the ListHoneypotNode operation to query the IDs of management nodes.	a882e590-b87b-45a6-87b9-d0a3e5a0****
HoneypotImageId	string	Yes	The ID of the honeypot image. Note You can call the ListAvailableHoneypot operation to query the IDs of images from the HoneypotImageId response parameter.	sha256:ebc4c102ac407d53733c2373e8888a733ddce86f163ccbe7492ae1cbf26****
Meta	string	No	The custom configuration of the honeypot in the JSON format. The value contains the following fields: trojan_git: Git-specific Defense. Valid values: zip: Git Source Code Package web: Git Directory Leak close: Disabled trojan_git_addr: Git Trojan Address. trojan_git.zip: Git Trojan. burp: Burp-specific Defense. Valid values: open: Enable close: Disable portrait_option: Source Tracing Configuration. Valid values: false: Disable true: Enable	{\"trojan_git\":\"close\",\"burp\":\"close\",\"portrait_option\":\"false\"}

Response parameters

Parameter	Type	Description	Example
	object	PlainResult
Data	object	The information about the honeypot.
HoneypotId	string	The ID of the honeypot.	9bf8cd373112263d4bc102fc5dba9d9f812ee05d4d35c487d330d52e937f****
HoneypotName	string	The custom name of the honeypot.	ruoyi
ControlNodeName	string	The name of the management node.	managerNodename
HoneypotImageName	string	The name of the honeypot image.	tcp_proxy
PresetId	string	The ID of the custom configuration for the honeypot.	ddh3731641137fe4b72b245346a2721d4b6tdgg3731641137fe4b72b245346a2721***
State	array	An array that consists of the status information about the honeypot.
State	string	The status of the honeypot. Value: starting: starting running: normal exited: closed upgrade: updating deleting: deleting resetting: resetting created: created stopping: stopping	starting
HoneypotImageDisplayName	string	The display name of the honeypot image.	HoneyDisplayName
NodeId	string	The ID of the management node.	a882e590-b87b-45a6-87b9-d0a3e5a0****
Success	boolean	Indicates whether the request was successful. Valid values: true: The request was successful. false: The request failed.	true
Code	string	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
Message	string	The error message returned.	successful
RequestId	string	The ID of the request, which is used to locate and troubleshoot issues.	29874225-EAAC-5415-8501-32DD20FD29F6
HttpStatusCode	integer	The HTTP status code returned.	200

Examples

Sample success responses

JSONformat

{
  "Data": {
    "HoneypotId": "9bf8cd373112263d4bc102fc5dba9d9f812ee05d4d35c487d330d52e937f****",
    "HoneypotName": "ruoyi",
    "ControlNodeName": "managerNodename",
    "HoneypotImageName": "tcp_proxy",
    "PresetId": "ddh3731641137fe4b72b245346a2721d4b6tdgg3731641137fe4b72b245346a2721***",
    "State": [
      "starting"
    ],
    "HoneypotImageDisplayName": "HoneyDisplayName",
    "NodeId": "a882e590-b87b-45a6-87b9-d0a3e5a0****"
  },
  "Success": true,
  "Code": "200",
  "Message": "successful",
  "RequestId": "29874225-EAAC-5415-8501-32DD20FD29F6",
  "HttpStatusCode": 200
}

Error codes

HTTP status code	Error code	Error message	Description
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.