All Products
Search
Document Center

Security Center:GetImageEventOperation

Last Updated:Nov 14, 2024

Queries alert handling rules.

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

Request parameters

ParameterTypeRequiredDescriptionExample
IdlongNo

The primary key of the alert handling rule.

814163
LangstringNo

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

  • zh: Chinese
  • en: English
zh

Response parameters

ParameterTypeDescriptionExample
object

The response parameters.

Dataobject

The returned data.

Idlong

The primary key of the alert handling rule.

443496
EventTypestring

The alert type. Valid values:

  • sensitiveFile
sensitiveFile
OperationCodestring

The operation code. Valid values:

  • whitelist: added to the whitelist.
whitelist
Conditionsstring

The rule conditions. The value is in the JSON format. Valid values of keys:

  • condition: the matching condition.
  • type: the matching type.
  • value: the matching value.
[{\"condition\": \"MD5\", \"type\": \"equals\", \"value\": \"0083a31cc0083a31ccf7c10367a6e783e\"}]
Scenariosstring

The application scope of the rule. The value is in the JSON format. Valid values of keys:

  • type
  • value
{\"type\": \"repo\", \"value\": \"test-aaa/shenzhen-repo-01\"}
EventKeystring

The keyword of the alert item.

PEM
EventNamestring

The name of the alert item.

PEM
Successboolean

Indicates whether the request was successful. Valid values:

  • true
  • false
true
Codestring

The HTTP status code.

200
Messagestring

The returned message.

successful
RequestIdstring

The request ID.

5861EE3E-F0B3-48B8-A5DC-A5080BFB****

Examples

Sample success responses

JSONformat

{
  "Data": {
    "Id": 443496,
    "EventType": "sensitiveFile",
    "OperationCode": "whitelist",
    "Conditions": "[{\\\"condition\\\": \\\"MD5\\\", \\\"type\\\": \\\"equals\\\", \\\"value\\\": \\\"0083a31cc0083a31ccf7c10367a6e783e\\\"}]\n",
    "Scenarios": "{\\\"type\\\": \\\"repo\\\", \\\"value\\\": \\\"test-aaa/shenzhen-repo-01\\\"}\n",
    "EventKey": "PEM",
    "EventName": "PEM"
  },
  "Success": true,
  "Code": "200",
  "Message": "successful",
  "RequestId": "5861EE3E-F0B3-48B8-A5DC-A5080BFB****"
}

Error codes

HTTP status codeError codeError messageDescription
400DataNotExistsdata not exist-
403NoPermissioncaller has no permissionYou are not authorized to do this operation.
500ServerErrorServerError-

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