Database Autonomy Service:Connect external self-managed databases to DAS

Usage notes

DAS is accessible over the public network only on port 80. The DAS gateway (DBGateway) communicates with DAS over this port. Data is encrypted in transit with gRPC and Transport Layer Security (TLS) to ensure its security.

Connection modes

DAS supports three modes for connecting an external self-managed database:

• Direct mode: This mode connects directly to your database over the public network and does not require a DAS gateway (DBGateway). You only need to provide the database account and password to add the instance. This mode currently supports MySQL, MongoDB, and Redis.

• Centralized mode: Deploy a DAS gateway (DBGateway) on at least one server. The gateway automatically discovers your database instances by scanning a CIDR block. For high availability, deploy the gateway on two or more servers.

• Host mode: Deploy a DAS gateway (DBGateway) on each server that hosts a database. The gateway automatically discovers the database instance on its host. This mode enables all DAS features, including full request analysis, SQL response time, and security audit. For a detailed feature comparison, see Feature comparison of connection modes.

Feature comparison of connection modes

Direct connection

1. Log on to the DAS console.

2. In the left-side navigation pane, choose Intelligent O&M Center > Instance Monitoring.

3. In the upper-right corner of the page, click Access Instance.

4. Click Other On-premise and Cloud Databases.

5. Click Direct mode.

6. Configure the database connection information.

   Parameter	Description
   Instance location	Select the region that is closest to your database.
   Select Engine:	Select the engine type of the database that you want to connect.
   Database Account	Enter the database account.
   Password	Enter the password for the database account.
   Instances	Enter the instances that you want to connect in the Address:port format.

7. Click Test Connection.

8. If the Status is Verified, click Save Instance. Otherwise, if the status is not Verified, ensure that the login information is correct and click Test Connection again.

9. To add more databases, click Add More.

Centralized connection

1. Log on to the DAS console.

2. In the left-side navigation pane, choose Intelligent O&M Center > Instance Monitoring.

3. In the upper-right corner of the page, click Access Instance.

4. Click Other On-premise and Cloud Databases.

5. Click Use a centralized DBGateway.

6. Choose an access method.

   Note

   If you have not deployed a DAS gateway in the target VPC, click Deploy a new DAS DBGateway and search for instances.. If you have already deployed a DAS gateway in the target VPC, click Use existing DAS DBGateway to scan for new instances .

   • Deploy a new DAS DBGateway and search for instances.:

     1. Click Deploy a new DAS DBGateway and search for instances..

     2. Select a network type and click Generate Deployment Command.

        Note

        • Network Type: Select a value based on how the host that runs DBGateway connects to Alibaba Cloud. For example:

          • For a self-managed database on the public network, select Public Network (Classic Network).

          • For a database in an on-premises data center or on another cloud connected to an Alibaba Cloud VPC by a leased line, select Proprietary Network (VPC/Leased Line).

        • Network Domain: You can use this parameter to manage different environments, such as on-premises data centers and self-managed databases on other cloud providers, for isolation.

     3. Copy the deployment command. Then, log on to the target device and run it.

        Note

        If the command line returns successfully, the DAS gateway is deployed. DAS automatically discovers the gateway. If the deployment fails, see Troubleshoot DBGateway deployment, resolve the issue, and try again.

     4. If the Current Status shows Normal, click Next.

   • Use existing DAS DBGateway to scan for new instances :

     1. Click Use existing DAS DBGateway to scan for new instances .

     2. On the Select DBGateway page, select the DAS gateway to use and click Discover Instance.

7. On the Discover Instance page, scan for the database instances that you want to connect.

   1. DAS provides two discovery methods:

      • Select Automatic scan:

        1. In the Scan address text box, enter the CIDR block to scan.

        2. In the Port range text box, enter the port range.

        3. Click Scan.

      • Select Enter Instances:

        1. Follow the on-screen instructions to enter the Instances.

        2. Click Scan.

           Note

           The DAS gateway automatically scans for and discovers the database instances.

   2. Click Next.

8. Enter the login credentials for the database.

   Parameter	Description
   Select Engine:	Select the engine type of the database that you want to connect.
   Database Account	Enter the database account.
   Password	Enter the password for the database account.
   Database IP	Select the database IP address to authorize.

   Note

   The account for the self-managed database requires specific permissions. For more information, see Required permissions.

   • If an account with the required permissions already exists, enter the database account and password, and then click Authorize.

   • If an account with the required permissions does not exist, enter the account and password, click Generate Authorization Command, copy and run the generated command on the database, and then click Authorize.

9. Click Authorize. After you click Authorize, the status may show Normal Connection or one of the following common errors:

   • Unauthorized: No account or password is configured.

   • Failed to access.: The network is unreachable or the instance is down.

   • Failed to verify.: The username or password is incorrect.

   • Insufficient Permissions: The instance is reachable, but the account lacks the required permissions. For more information, see Required permissions.

10. Click Complete.

Host mode connection

1. Log on to the DAS console.

2. In the left-side navigation pane, choose Intelligent O&M Center > Instance Monitoring.

3. In the upper-right corner of the page, click Access Instance.

4. Click Other On-premise and Cloud Databases.

5. Click Use a host-mode DBGateway.

6. Select a network type and click Generate Authorization Command.

   Note

   • Network Type: Select a value based on how the host that runs DBGateway connects to Alibaba Cloud. For example:

     • For a self-managed database on the public network, select Public Network (Classic Network).

     • For a database in an on-premises data center or on another cloud connected to an Alibaba Cloud VPC by a leased line, select VPC.

   • Network Domain: You can use this parameter to manage different environments, such as on-premises data centers and self-managed databases on other cloud providers, for isolation.

7. Copy the deployment command. Then, log on to the target device and run it.

   Note

   If the command line returns successfully, the DAS gateway is deployed and DAS automatically discovers the gateway. If the Current Status shows Normal, click Next. If the deployment fails, see Troubleshoot DBGateway deployment, resolve the issue, and try again.

8. Enter the login credentials for the database.

   Parameter	Description
   Select Engine:	Select the engine type of the database that you want to connect.
   Database Account	Enter the database account.
   Password	Enter the password for the database account.
   Database IP	Select the database IP address to authorize.

   Note

   The account for the self-managed database requires specific permissions. For more information, see Required permissions.

   • If an account with the required permissions already exists, enter the database account and password, and then click Authorize.

   • If an account with the required permissions does not exist, enter the account and password, click Generate Authorization Command, copy and run the generated command on the database, and then click Authorize.

9. Click Authorize. After you click Authorize, the status may show Normal Connection or one of the following common errors:

   • Unauthorized: No account or password is configured.

   • Failed to access.: The network is unreachable or the instance is down.

   • Failed to verify.: The username or password is incorrect.

   • Insufficient Permissions: The instance is reachable, but the account lacks the required permissions. For more information, see Required permissions.

10. Click Complete.

API reference