Queries data assets such as MaxCompute, ApsaraDB RDS, and Object Storage Service (OSS) that you authorize Data Security Center (DSC) to access.
Operation description
When you call the DescribeInstances operation, you can specify parameters such as Name and RiskLevelId to query data assets that meet filter conditions.
Limits
You can call this operation up to 10 times per second per account. If the number of the calls per second exceeds the limit, throttling is triggered. As a result, your business may be affected. We recommend that you take note of the limit when you call this operation.
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-sddp:DescribeInstances | get |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
Lang | string | No | The language of the content within the request and response. Default value: zh_cn. Valid values:
| zh_cn |
Name | string | No | The keyword that is used to search for data assets. DSC searches for data assets based on the keyword that you specify in fuzzy match mode. For example, if you specify data, all data assets whose names contain data are queried. | data |
ProductId | long | No | The ID of the service to which the data asset belongs. You can call the DescribeDataAssets operation to query the ID of the service. | 1 |
RiskLevelId | long | No | The sensitivity level ID of the data asset. A higher sensitivity level indicates that the identified data is more sensitive. Valid values:
| 2 |
RuleId | long | No | The ID of the sensitive data detection rule that the data asset hits. You can call the DescribeRules operation and obtain the ID of the sensitive data detection rule from the Id response parameter. | 1111111 |
ServiceRegionId | string | No | The region where the data asset resides. For more information, see Supported regions. | cn-hangzhou |
FeatureType | integer | No | This parameter is deprecated. | 1 |
ProductCode | string | No | The name of the service to which the data asset belongs, such as MaxCompute, OSS, and ApsaraDB RDS. For more information about the types of data assets from which DSC can scan for sensitive data, see Supported data assets. | RDS |
PageSize | integer | No | The number of entries to return on each page. Default value: 10. | 10 |
CurrentPage | integer | No | The number of the page to return. Default value: 1. | 1 |
Response parameters
Examples
Sample success responses
JSON
format
{
"CurrentPage": 1,
"RequestId": "71064826-726F-4ADA-B879-05D8055476FB",
"PageSize": 10,
"TotalCount": 231,
"Items": [
{
"CreationTime": 1637226782000,
"LastFinishTime": 1637622793000,
"Owner": "dtdep-239-******",
"TenantName": "Tenant 1\n",
"Protection": false,
"DepartName": "***DemoCenter",
"Labelsec": true,
"RiskLevelId": 2,
"ProductId": "5",
"Name": "gxdata",
"TotalCount": 231,
"InstanceDescription": "Data asset Information 1\n",
"RuleName": "\\*\\*\\* rule\n",
"Sensitive": true,
"RiskLevelName": "Sensitive data at level 1\n",
"OdpsRiskLevelName": "1",
"SensitiveCount": 123,
"Id": 11111,
"ProductCode": "RDS",
"ModelTags": [
{
"Id": 101,
"Name": "personal sensitive data"
}
]
}
]
}
Error codes
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2024-09-18 | The response structure of the API has changed | View Change Details |
2023-12-06 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-12-06 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-12-06 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-12-06 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-12-06 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-12-06 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-12-06 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-12-06 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-12-06 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-12-06 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-12-06 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-12-06 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-12-06 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-12-06 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-12-06 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-12-06 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-12-06 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-12-06 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-12-06 | The internal configuration of the API is changed, but the call is not affected | View Change Details |