OperateVirusEvents - Security Center - Alibaba Cloud Documentation Center

Handles alert events that are generated by the antivirus feature. You can perform in-depth detection and removal, add alert events to the whitelist, ignore alert events, or manually handle alert events.

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:OperateVirusEvents	update	All Resources ``	none	none

Request parameters

Parameter	Type	Required	Description	Example
OperationCode	string	Yes	The operation that you want to perform on the alert events. Valid values: default: performs in-depth detection and removal ignore: ignores the alert event advance_mark_mis_info: adds the alert events to the whitelist manual_handled: marks the alert events as manually handled	default
OperationRange	string	No	The handling scope.	[{\"type\":\"machine\",\"list\":[\"xxxxxxxxx-4cbf-4ca6-a1b7-8a09d1f86ab0\"]}]
OperationAll	integer	Yes	Specifies whether to handle all alert events. Valid values: 1: yes 0: no	0

Response parameters

Parameter	Type	Description	Example
	object
TaskId	long	The ID of the task to handle multiple alert events at a time.	1
RequestId	string	The ID of the request.	B72BEC03-001C-5C77-A4BB-1E6XXXXXXX

Examples

Sample success responses

JSONformat

{
  "TaskId": 1,
  "RequestId": "B72BEC03-001C-5C77-A4BB-1E6XXXXXXX"
}

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.

Change history

Change time	Summary of changes	Operation

No change history