Query aggregation types of system defense rules by using ListSystemAggregationRules - Security Center

Queries the details about the aggregation types of system defense rules.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

yundun-sas:ListSystemAggregationRules

get

*All Resource

*

None

Request parameters

Parameter	Type	Required	Description	Example
Lang	string	No	The language of the content within the request and response. Default value: zh. Valid values: zh: Chinese en: English	zh
RuleName	string	No	The name of the rule.	Rule****
CurrentPage	integer	Yes	The number of the page to return.	1
PageSize	integer	Yes	The number of entries to return on each page.	20
RuleTypes	array	No	The types of the rules.
	integer	No	The type of the rules. Valid values: 1: alihips 2: alinet 3: alidetect 4: alisecguard	1
SystemType	integer	No	The type of the operating system. Valid values: 2: Windows 1: Linux 0: all	0
AggregationIds	array	No	The IDs of the aggregation types.
	integer	No	The ID of the aggregation type.	1

Response elements

Element	Type	Description	Example
	object	The data returned.
RequestId	string	The ID of the request, which is used to locate and troubleshoot issues.	6800B790-B10A-5C2F-BEB3-F1D5CE61****
PageInfo	object	The pagination information.
CurrentPage	integer	The page number of the returned page.	1
PageSize	integer	The number of entries returned per page.	20
TotalCount	integer	The total number of entries returned.	30
AggregationList	array<object>	An array that consists of the details about the aggregation types.
	object	The details about the aggregation type.
Id	integer	The ID of the aggregation type.	1
RuleCount	integer	The number of rules that are of the aggregation type.	0
Name	string	The name of the aggregation type.	Remote control****

Examples

Success response

JSON format

{
  "RequestId": "6800B790-B10A-5C2F-BEB3-F1D5CE61****",
  "PageInfo": {
    "CurrentPage": 1,
    "PageSize": 20,
    "TotalCount": 30
  },
  "AggregationList": [
    {
      "Id": 1,
      "RuleCount": 0,
      "Name": "Remote control****"
    }
  ]
}

Error codes

HTTP status code	Error code	Error message	Description
400	IdempotentParameterMismatch	The request uses the same client token as a previous, but non-identical request. Do not reuse a client token with different requests, unless the requests are identical.
500	ServerError	ServerError
403	NoPermission	caller has no permission	You are not authorized to do this operation.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.