Queries anti-ransomware policies.
Debugging
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:DescribeBackupPolicies | list |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
Name | string | No | The name of the anti-ransomware policy that you want to query. | SecurityStrategy-20200303 |
MachineRemark | string | No | The information that you want to use to identify the servers protected by the anti-ransomware policy. You can enter the IP address or ID of a server. | 1.1.XX.XX |
Status | string | No | The status of the anti-ransomware policy. Valid values:
| enabled |
PageSize | integer | Yes | The number of entries to return on each page. Default value: 10. | 10 |
CurrentPage | integer | Yes | The number of the page to return. Default value: 1. | 1 |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "BE120DAB-F4E7-4C53-ADC3-A97578ABF384",
"PageInfo": {
"CurrentPage": 1,
"PageSize": 10,
"TotalCount": 30,
"Count": 3
},
"Policies": [
{
"ClientErrorCount": 2,
"Status": "enabled",
"PolicyVersion": "2.0.0",
"Policy": "{\"Exclude\":[\"/bin/\",\"/usr/bin/\",\"/sbin/\",\"/boot/\",\"/proc/\",\"/sys/\",\"/srv/\",\"/lib/\",\"/selinux/\",\"/usr/sbin/\",\"/run/\",\"/lib32/\",\"/lib64/\",\"/lost+found/\",\"/var/lib/kubelet/\",\"/var/lib/ntp/proc\",\"/var/lib/container\",\"Windows\\\\\",\"Python27\\\\\",\"Program Files (x86)\\\\\",\"Program Files\\\\\",\"Boot\\\\\",\"$RECYCLE.BIN\",\"System Volume Information\\\\\",\"Users\\\\Administrator\\\\NTUSER.DAT*\",\"ProgramData\\\\\",\"pagefile.sys\",\"Users\\\\Default\\\\NTUSER.DAT*\",\"Users\\\\Administrator\\\\ntuser.*\"],\"ExcludeSystemPath\":true,\"Include\":[],\"IsDefault\":1,\"Retention\":7,\"Schedule\":\"I|1630689360|PT24H\",\"Source\":[],\"SpeedLimiter\":\"\",\"UseVss\":true}",
"UpgradeStatus": "Upgrading",
"ServiceErrorCount": 2,
"PolicyRegionId": "ch-hangzhou",
"ClientStatus": "running",
"Name": "SecurityStrategy-20200303",
"HealthClientCount": 2,
"Id": 11,
"ClientErrorUuidList": [
"[\"3bb30859-b3b5-4f28-868f-b0892c98****\",\"3bb30859-b3b5-4f28-868f-b0892c98****\"]"
],
"RemarkedUuidList": [
"[\"3bb30859-b3b5-4f28-868f-b0892c98****\",\"3bb30859-b3b5-4f28-868f-b0892c98****\"]"
],
"UuidList": [
"[\"3bb30859-b3b5-4f28-868f-b0892c98****\",\"3bb30859-b3b5-4f28-868f-b0892c98****\"]"
],
"ServiceErrorUuidList": [
"[\"3bb30859-b3b5-4f28-868f-b0892c98****\",\"3bb30859-b3b5-4f28-868f-b0892c98****\"]"
],
"HealthClientUuidList": [
"[\"3bb30859-b3b5-4f28-868f-b0892c98****\",\"3bb30859-b3b5-4f28-868f-b0892c98****\"]"
],
"ServerType": "OUT_CLOUD",
"LastStatusSyncTime": 1719488535027,
"PreStatus": "disabled"
}
]
}
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 |
---|---|---|
2024-06-27 | The response structure of the API has changed | View Change Details |