To demonstrate solutions, you must register ApsaraDB RDS for MySQL instances that simulate development and production environments with Data Management (DMS). You must also create a DMS administrator account and a regular user account.

Prerequisites

  • Two ApsaraDB RDS for MySQL instances are created. One instance is used to simulate the development environment, and the other is used to simulate the production environment. For more information, see Create an ApsaraDB RDS for MySQL instance.
    Note The ApsaraDB RDS for MySQL instance that simulates the development environment is named POC_dev, and the ApsaraDB RDS for MySQL instance that simulates the production environment is named POC_prod.
  • A database named poc_dev is created in the POC_dev instance, and a database named poc_prod is created in the POC_prod instance. For more information, see Create accounts and databases for an ApsaraDB RDS for MySQL instance.
  • A DMS administrator account is created.
    Note DMS administrators can manage the system, manage permissions, configure development standards, and approve processes. If you are a first-time user of DMS, DMS uses your Alibaba Cloud account as the DMS administrator account.
  • Optional. A regular user account is created. For more information, see Add a user.
    Note Regular users can apply for permissions on databases and query or update schemas. Regular users can be the employees of enterprises, such as R&D staff, testers, product staff, operations staff, and data analysts.

Procedure

  1. Log on to the DMS console as a DMS administrator.
    Note To switch to the previous version of the DMS console, click the Return to old version icon in the lower-right corner of the page. For more information, see Switch to the previous version of the DMS console.
  2. Create two security rule sets named Security Rules for POC Development Databases and Security Rules for POC Production Databases, and set the Engine Type parameter to mysql for the rule sets. DMS applies default settings to security rules in the rule sets. For more information, see Create security rules.
    Note Security rules use a domain-specific language (DSL) to implement fine-grained control over databases. You can use security rules to manage the development standards, permissions, and data changes of instances.
  3. Register the POC_dev and POC_prod instances with DMS. For more information, see Register an ApsaraDB instance.
    Note For the POC_dev instance, select Security Collaboration as the control mode and Security Rules for POC Development Databases as the security rule set. For the POC_prod instance, select Security Collaboration as the control mode and Security Rules for POC Production Databases as the security rule set. If your instances are registered with DMS, you can change the control mode and security rule sets of the instances. For more information, see Change the security rules of a database instance.
    • Security Collaboration is the most secure control mode provided by DMS and gives you access to all DMS features, such as customization of development standards, fine-grained permission control, and secure and stable data change.
    • The ApsaraDB RDS for MySQL instances in Security Collaboration mode are billed on a pay-as-you-go or subscription basis. For more information, see Pricing.
  4. Grant the regular user the permissions to query and change data in the poc_dev and poc_prod databases. For more information, see Manage the permissions of a user as a DMS administrator.