All Products
Search
Document Center

Security Center:AddImageEventOperation

Last Updated:Oct 08, 2024

Creates an alert handling rule.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

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

Request parameters

ParameterTypeRequiredDescriptionExample
EventTypestringNo

The alert type.

  • Set the value to sensitiveFile.
sensitiveFile
OperationCodestringNo

The operation code.

  • Set the value to whitelist to add the alert item to the whitelist.
whitelist
ConditionsstringNo

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\"}]
ScenariosstringNo

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\"}
EventKeystringNo

The keyword of the alert item.

PEM
EventNamestringNo

The name of the alert item.

PEM

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.

  • Only sensitiveFile may be returned.
sensitiveFile
OperationCodestring

The operation code.

  • Only whitelist may be returned, which indicates that the alert item is 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.

0C8487EF-50C2-54BB-8634-10F8C35D****

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": "0C8487EF-50C2-54BB-8634-10F8C35D****"
}

Error codes

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

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