Authorizing Access to a Database Asset

Prerequisites

• RDS, GaussDB(DWS), DDS, or GaussDB service has been enabled, you have assets on them, and there are available IP addresses in the corresponding subnets.
• The Status of the database instance is Normal, and the number of security groups is 1.

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 instance, click the corresponding database type (for example, DWS or Self-built databases) and perform the following steps:

1. Log in to the management console.
2. Click in the upper left corner and select a region or project.
3. In the navigation tree on the left, click . Choose Security & Compliance > Data Security Center .
4. In the navigation tree on the left, choose Asset Management > Asset Center. The Asset Center page is displayed.
5. Click RDS. The RDS Databases tab page.
   Figure 1 RDS database instances
   

6. Click the Database Instances tab. The Database Instances tab page is displayed. Authorization can be performed in either of the following ways:
   • Method 1: Click Authorize in the Operation column of the database instance list, and enter the database information for authorization.
     Figure 2 Authorizing access to databases
     
     • Grant the read-only permission: Only the sensitive data identification function can be used.
     • Grant the read and write permission: The sensitive data identification and data anonymization functions can be used.
       

       • After the RDS read-only permission is authorized, DSC creates an account dsc_readonly in RDS.
         • After the password of the dsc_readonly account is reset in RDS, it will not be automatically synchronized to DSC. As a result, the sensitive data identification task fails. Therefore, do not reset the password of this account.
         • If you have reset the password of dsc_readonly in RDS, delete the authorized RDS DB instance in DSC and re-authorize the instance.
       • DSC cannot scan and mask sensitive data in MySQL databases which SSL has been enabled for on the RDS DB instance.
   • Method 2: Click an instance name to go to the instance details page. In the Operation column, click Authorize to authorize access to a database.
     Figure 3 Instance details
     

7. After the authorization is complete, click the Databases tab to view the connection status of the authorized database.
   After the asset authorization is complete, the Connection Status of the asset is Checking, which means DSC is checking the database connectivity.

   • 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. Move the cursor to Failed to view the failure cause or rectify the fault by referring to section How Do I Troubleshoot the Failure in Connecting to the Added Database?

Related Operations

• Deleting a DB instance

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

  Select multiple self-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.

• Drawing 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, such as DDS, are excluded. For details, see section Creating a Metadata Collection Task.

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

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

  • Manually create a metadata task by referring to section Creating a Metadata Collection Task.
• Creating an identification task

  On the Databases tab page, click Create Identification Task in the Operation column of the asset list to create an identification task for an asset. For details, see section Creating an Identification Task.

• Testing connectivity in batches

  You can select multiple database instances and data instances to perform connectivity tests in batches.