Database Autonomy Service:Connect an ECS-hosted self-managed database instance

Connection types

DAS supports three connection types for ECS-hosted self-managed databases. Choose the type that matches your environment and feature requirements.

Connection type details:

• Direct connection -- Connect by entering your database account and password. No DBGateway deployment is required. Configure security group rules to allow DAS access.

• Centralized mode -- Deploy DBGateway on at least one ECS instance. For disaster recovery, deploy DBGateway on two or more ECS instances. DBGateway automatically discovers database instances by scanning CIDR blocks. Do not use this mode for ECS instances in a classic network.

• Host mode -- Deploy DBGateway on each ECS instance. DBGateway automatically discovers database instances. This mode supports all DAS features, including full SQL analysis, SQL response time, and security audit.

Direct connection

1. Log on to the DAS console.

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

3. Click Access Instance in the upper-right corner of the page.

4. Click DB Instances on ECS.

5. Click Direct connection.

6. Select a region.

7. In the Add DAS access rules column for the target security group, select Private Network and then click Save.

   Note

   • DAS automatically adds the IP addresses of the DAS service in the selected region to the security group rules of your ECS instance. For a list of DAS service IP addresses by region, see DAS service IP address list.

   • You must add the DAS service IP address to the private network rules of at least one security group.

8. Select the ECS instances that you want to connect and then click Next.

9. Enter the logon information for your database.

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

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

   Note

   The database account must have the required permissions. For more information, see Permissions.

   Parameter	Description
   Select engine	Select your ECS-hosted self-managed database engine. Supported engines include MySQL, PostgreSQL, MongoDB, and Redis.
   Port	The port of your ECS-hosted self-managed database.
   Database account	The account for your ECS-hosted self-managed database.
   Password	The password for your ECS-hosted self-managed database.

10. Click Authorize. After you click Authorize, the status changes to Connection normal if the authorization is successful. Otherwise, an error message is displayed:

    • Unauthorized: You did not enter a username or password.

    • Cannot connect: The network or the instance may be down.

    • Authentication failed: The username or password is incorrect.

    • Insufficient permissions: You can connect to the instance, but the account lacks the required permissions. For more information, see Permissions.

11. Click Complete.

Centralized mode

1. Log on to the DAS console.

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

3. Click Access Instance in the upper-right corner of the page.

4. Click DB Instances on ECS.

5. Click Use database gateway in centralized mode.

6. Select a connection method:

   • If you have not deployed DBGateway in the target VPC, select Deploy a new DAS DBGateway and search for instances..

     1. Select the ECS instances in the target region and then click Generate Deployment Command.

     2. Copy the deployment command and run it on the selected ECS instance. If the command line returns successfully, the program is deployed. If the deployment fails, see Troubleshoot DBGateway deployment issues to resolve the issue and then redeploy.

     3. After the deployment is successful, DAS automatically discovers the gateway. If the Current status is Normal, click Next.

   • If you have already deployed DBGateway in the target VPC, select Use existing DAS DBGateway to scan for new instances .

     1. On the Select DBGateway page, select the DBGateway.

     2. Click Discover Instance.

7. On the Discover Instance page, specify the instances to discover. DAS can discover database instances in two ways: After DAS discovers the instances, click Next.

   • Select Auto-scan:

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

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

     3. Click Start probing.

   • Select Enter instance list:

     1. In the Instance list text box, enter the instances according to the on-screen instructions.

     2. Click Start probing.

8. Enter the logon information for your database.

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

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

   Note

   The database account must have the required permissions. For more information, see Permissions.

   Parameter	Description
   Select engine	Select your ECS-hosted self-managed database engine. Supported engines include MySQL, PostgreSQL, MongoDB, and Redis.
   Database account	The account for your ECS-hosted self-managed database.
   Password	The password for your ECS-hosted self-managed database.
   Database IP	Select the database IP address to authorize.

9. Click Authorize. After you click Authorize, the status changes to Connection normal if the authorization is successful. Otherwise, an error message is displayed:

   • Unauthorized: You did not enter a username or password.

   • Cannot connect: The network or the instance may be down.

   • Authentication failed: The username or password is incorrect.

   • Insufficient permissions: You can connect to the instance, but the account lacks the required permissions. For more information, see Permissions.

10. Click Complete.

Host mode

1. Log on to the DAS console.

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

3. Click Access Instance in the upper-right corner of the page.

4. Click DB Instances on ECS.

5. Click Use database gateway in host mode.

6. Select the ECS instances in the target region and then click Generate Deployment Command.

7. Copy the deployment command and run it on each selected ECS instance. If the command line returns successfully, the program is deployed. If the deployment fails, see Troubleshoot DBGateway deployment issues to resolve the issue and then redeploy.

8. After the deployment is successful, DAS automatically discovers the gateway. If the Current status is Normal, click Next.

9. Enter the logon information for your database.

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

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

   Note

   The database account must have the required permissions. For more information, see Permissions.

   Parameter	Description
   Select engine	Select your ECS-hosted self-managed database engine. Supported engines include MySQL, PostgreSQL, MongoDB, and Redis.
   Database account	The account for your ECS-hosted self-managed database.
   Password	The password for your ECS-hosted self-managed database.
   Database IP	Select the database IP address to authorize.

10. Click Authorize. After you click Authorize, the status changes to Connection normal if the authorization is successful. Otherwise, an error message is displayed:

    • Unauthorized: You did not enter a username or password.

    • Cannot connect: The network or the instance may be down.

    • Authentication failed: The username or password is incorrect.

    • Insufficient permissions: You can connect to the instance, but the account lacks the required permissions. For more information, see Permissions.

11. Click Complete.

Related API operation