Updated on 2026-07-27 GMT+08:00

Adding and Authorizing Database Assets

To identify sensitive data, mask static data, or add/extract data watermarks for database assets, you must authorize DSC to access your databases.

  • User-built database

    If a user-built database is used, add the database instance to DSC, and then authorize DSC to access the database.

  • Cloud database

    If a cloud database is used, you do not need to add the database instance to DSC. You only need to enable the corresponding cloud service. After DSC is authorized to access cloud database assets, it automatically discovers your cloud database instances. You need to authorize DSC to access your databases by referring to Authorizing Access to a Database Asset.

Prerequisites

Table 1 Prerequisites for adding and authorizing database assets

Type

Prerequisites

User-built database

DWS cross-account or cross-VPC instance

  • You have created a VPC peering connection between two VPCs of the same account or different accounts. The peer VPC is the VPC where the DWS instance resides. For details about how to create a VPC peering connection, see VPC Peering Connection.
  • You have obtained the database version and host information.

Cloud database

  • To authorize DSC to access a cloud database, you must have enabled the RDS, DWS, DDS, or GaussDB service. For details, see Asset Management Overview. Ensure that you have the asset and there are available IP addresses in the corresponding subnet.
  • The database instance is in the available status.

Data Source Types and Versions Supported by DSC

For user-built databases, only data sources and versions supported by DSC can be added. For details, see the following table.

Data Source

Data Source Type

Version

  • Relational Database Service (RDS)
  • Databases built on ECS

MySQL

5.6, 5.7, 5.8, and 8.0

SQL Server

2017_SE, 2017_EE, and 2017_WEB

2016_SE, 2016_EE, and 2016_WEB

2014_SE and 2014_EE

2012_SE, 2012_EE, and 2012_WEB

2008_R2_EE and 2008_R2_WEB

PostgreSQL

15, 14, 13, 12, 11, 10, 9.6, 9.5, 9.4, 9.1, and 1.0

Databases built on ECS

TDSQL

10.3.x

Oracle

11, 12

KingBase

V8

GreenPlum

6.17.3 and 6.1.0

MongoDB

NOTICE:

DSC only supports MongoDB instances with the setting authSource=admin.

3.4, 4.0, 4.2

GaussDB

GaussDB

1.3, 1.4, and 2.7

Databases on Bare Metal Servers (BMSs)

DMDBMS

7 and 8

Data Warehouse Service (DWS)

DWS

9.1.0, 9.0, 8.3.0, 8.2.1, 8.2.0, 8.1.3, 8.1.1, 8.0.1, 8.0.0

Document Database Service (DDS)

DDS

4.0, 4.2, and 4.4

Adding a Database Asset

You can perform the following operations to add user-built database assets to DSC for management.

Database Scan

DSC supports detection through IP address and port and returns possible database assets, facilitating adding cloud self-built databases.

  1. Log in to the DSC console.
  2. Click in the upper left corner and select a region or project.
  3. In the navigation pane on the left, choose Asset Center > Asset Management.
  4. Choose Databases > Self-built databases.
  5. Click the Database Scan tab and click Create Scan Task.
  6. In the Database Scan dialog box, select a VPC, subnet, security group, and scan targets (database engine and port). You can also click Add and enter ports to be detected.
  7. Click Start.

    When the Status of the scan task is Scanned, click View Details in the Operation column to view the database scan result. If the Suspected DB Engine column returns a database type, the asset is suspected to be a database asset. You can click Add Asset in the Operation column to add the database instance to DSC for management.

Authorizing Access to a Database Asset

The following uses the RDS database type as an example to describe how to authorize access to database assets in an RDS database instance. To authorize access to other types of database instances, click the corresponding database type (for example, DWS or Self-built databases) and perform the following steps.

When you authorize access to a database asset, the metadata task can be automatically enabled.

Related Operations

  • Deleting a DB instance

    Only user-built DB instances can be deleted. You can delete an instance only when there are no authorized databases and metadata under it.

    Select multiple user-built database instances and click Batch Delete in the upper left corner of the instance list to delete the instances. You can also click Delete in the Operation column of the instance list to delete a single DB instance.

  • Editing the database instance information

    Only information about user-built database instances can be edited.

    Choose Self-built databases > Database Instances, locate the row that contains the target database instance, and click Edit in the Operation column. In the displayed Edit Database Instance dialog box, edit the database instance information.

  • Editing the database information

    Select a database type. On the Databases page, locate the row that contains the target database and click Edit in the Operation column. In the displayed Edit Database dialog box, edit the database information. The database name and asset name cannot be modified.

  • Obtaining metadata of an instance
    • If the number of authorized databases of a cloud database instance is greater than 0, click Refresh in the Operation column of the instance list to obtain the database, table, and column information of the instance.

      Cloud databases that do not support metadata collection are excluded. For details, see Creating a Metadata Scanning Task.

    • If you enable the function of automatically creating a metadata task when adding a user-built database instance, the system automatically creates a metadata task to obtain all metadata of the instance after the instance is created.

      User-built databases that do not support metadata collection, such as SQL Server, are excluded. For details, see Creating a Metadata Scanning Task.

    • You can manually create a metadata task by referring to section Creating a Metadata Scanning Task.
  • Creating an identification task

    In the Databases tab, locate the target asset and click Create Identification Task in the Operation column to classify and grade the asset. For details, see Creating an Identification Task.

  • Testing connectivity in batches

    For user-built databases, you can select multiple databases to test connectivity in batches.

    Choose Self-built databases to go to the Databases tab page. Select multiple databases and click Test Connectivity in the upper left corner to test the connectivity of the databases.

    • DSC can access the added database normally if the Connection Status of the database is Succeeded.
    • DSC cannot access the added database normally if the Connection Status of the database is Failed. Hover the cursor over Failed to view the failure cause or rectify the fault by referring to How Do I Troubleshoot the Failure in Connecting to the Added Database?
  • Viewing the node IP address scan scope

    On the Databases tab page, locate the target asset and click View Node IP Address Scan Range in the Operation column.