From d0d66eeb7354504c225731dcaea7033cf42b8aa7 Mon Sep 17 00:00:00 2001 From: wangdengke2 Date: Thu, 23 Apr 2026 10:06:18 +0000 Subject: [PATCH] rds_umn Reviewed-by: Wagner, Fabian Co-authored-by: wangdengke2 Co-committed-by: wangdengke2 --- docs/rds/umn/rds_01_0017.html | 9 ++++++++- docs/rds/umn/rds_02_0016.html | 4 ++-- docs/rds/umn/rds_02_0047.html | 4 ++-- docs/rds/umn/rds_05_0140.html | 5 ++--- docs/rds/umn/rds_08_0026.html | 2 +- docs/rds/umn/rds_08_0033.html | 3 ++- docs/rds/umn/rds_09_0065.html | 2 +- docs/rds/umn/rds_faq_0055.html | 3 +-- docs/rds/umn/rds_glossary_0001.html | 2 +- docs/rds/umn/rds_pg_05_0084.html | 5 ++--- docs/rds/umn/rds_sqlserver_05_0050.html | 6 +++--- 11 files changed, 25 insertions(+), 20 deletions(-) diff --git a/docs/rds/umn/rds_01_0017.html b/docs/rds/umn/rds_01_0017.html index 413e30791..9376c38ef 100644 --- a/docs/rds/umn/rds_01_0017.html +++ b/docs/rds/umn/rds_01_0017.html @@ -8,7 +8,7 @@

RDS Permissions

By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

RDS is a project-level service deployed and accessed in specific physical regions. To assign RDS permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing RDS, users need to switch to a region where they have been authorized to use RDS.

You can grant users permissions by using roles and policies.
  • Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you need to also assign other roles on which the permissions depend to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
-
  • Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control.
+
  • Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control.

Table 1 lists all the system-defined roles and policies supported by RDS.

@@ -131,6 +131,8 @@

vpc:subnets:get

vpc:securityGroups:get

To create an encrypted instance, configure the KMS Administrator permission for the project.

+
If storage autoscaling is required, you need to create an agency and grant the IAM user the following actions:
  • iam:agencies:listAgencies
  • iam:agencies:createAgency
  • iam:permissions:listRolesForAgencyOnProject
  • iam:permissions:grantRoleToGroupOnProject
  • iam:permissions:grantRoleToAgencyOnProject
  • iam:roles:listRoles
  • iam:roles:createRole
+

Changing DB instance specifications

@@ -727,6 +729,11 @@
+

Creating an Agency

  1. Log in to the IAM console.
  2. Click Agencies. On the displayed page, click Create Agency.
    If storage autoscaling and autoscaling of vCPUs and memory are required, perform the following operations:
    1. On the displayed page, set the following parameters and click OK. Then, click Authorize in the displayed dialog box.
      • Agency Name: Enter RDSAccessProjectResource.
      • Agency Type: Select Cloud service.
      • Cloud Service: Select Database Service (DBS).
      • Validity Period: Select Unlimited.
      • Description: Enter RDSAccessProjectResource allows RDS to access user's project resource.
      +
    2. Enter DBS in the search box to start a search, select DBS AgencyPolicy, and click Next.
    3. By default, the permissions apply to all resources. Click OK.
    +
    +
+
diff --git a/docs/rds/umn/rds_02_0016.html b/docs/rds/umn/rds_02_0016.html index dc08687b2..bab8a00e8 100644 --- a/docs/rds/umn/rds_02_0016.html +++ b/docs/rds/umn/rds_02_0016.html @@ -92,8 +92,8 @@

Enter the password of the database account if the following information is displayed:

Password:

For example, to connect to a DB instance through an SSL connection as user root, run the following command:

-

psql --no-readline -h 192.168.0.44 -p 5432 "dbname=postgres user=root sslmode=verify-ca sslrootcert=/root/ca.pem"

-

Password:

+
psql --no-readline -h 192.168.0.44 -p 5432 "dbname=postgres user=root  sslmode=verify-ca sslrootcert=/root/ca.pem"
+Password:

  • The SSL connection is established if information similar to the following is displayed after you log in to the database:

    SSL connection (protocol: TLSv1.2, cipher: ECDHE-RSA-AES256-GCM-SHA384, bits: 256, compression: off)

    • diff --git a/docs/rds/umn/rds_02_0047.html b/docs/rds/umn/rds_02_0047.html index 05ecfec92..1ac149e77 100644 --- a/docs/rds/umn/rds_02_0047.html +++ b/docs/rds/umn/rds_02_0047.html @@ -62,7 +62,7 @@

    For details, see section How Can I Identify the Validity Period of an SSL Root Certificate?

  • You can also download the certificate bundle, which contains both the new certificate provided since April 2017 and the old certificate.
    • -

  • Connect to the RDS DB instance. The Linux OS is used as an example.

    mysql -h <host> -P <port> -u <userName> -p --ssl-ca=<caDIR>

    +

  • Connect to the RDS DB instance. The Linux OS is used as an example.

    mysql -h <host> -P <port> -u <userName> -p --ssl-ca=<caDIR>
    @@ -94,7 +94,7 @@
    Table 2 Parameter description

    Parameter

    For example, to connect to a DB instance through an SSL connection as user root, run the following command:

    -

    mysql -h 172.16.0.31 -P 3306 -u root -p --ssl-ca=ca.pem

    +
    mysql -h 172.16.0.31 -P 3306 -u root -p --ssl-ca=ca.pem

    Enter the password of the database account if the following information is displayed:

    Enter password:

    If the connection fails, see What Should I Do If an ECS Cannot Connect to an RDS DB Instance Through a Private Network?

    diff --git a/docs/rds/umn/rds_05_0140.html b/docs/rds/umn/rds_05_0140.html index 2d37353d9..09f850b25 100644 --- a/docs/rds/umn/rds_05_0140.html +++ b/docs/rds/umn/rds_05_0140.html @@ -89,9 +89,8 @@

    Procedure

    1. Log in to the management console.
    2. Click in the upper left corner and select a region and a project.
    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
    4. On the Instances page, locate a DB instance using cloud SSD and choose More > Change Instance Class in the Operation column.

      Alternatively, click the instance name to go to the Summary page. Under Instance Class, click Configure.

      -

    5. On the displayed page, select a target Storage Type, for example, Extreme SSD for Storage Type and click Next.

      If the target storage type is Flexible SSD, click Disk QoS under Change Type and enter the IOPS and throughput.

      -
      • IOPS: Flexible SSD decouples capacity from performance and allows for tailored IOPS for your business requirements with fixed capacity.

        This parameter is available only for Flexible SSD. The value range is from 3000 to 128000. The IOPS is limited by the disk size and must be no greater than 500 times the disk capacity.

        -
      • Throughput: Flexible SSD decouples capacity from performance and allows for tailored throughput for your business requirements with fixed capacity.

        This parameter is available only for Flexible SSD. The value ranges from 125 to 1000 (in MiB/s) and must also be no greater than the IOPS divided by 4.

        +

      • On the Change Instance Class page, select a new storage type and click Next.

        If you select Flexible SSD, select Instance Specifications or Disk QoS for Change Type as needed.

        +
        • To change instance specifications, click Instance Specifications under Change Type and select the new specifications.
        • To change disk QoS, click Disk QoS under Change Type and enter the new IOPS and throughput.
          • IOPS: The value range is from 3000 to 128000. The IOPS is limited by the disk size and must be no greater than 500 times the disk capacity.
          • Throughput: The value range is from 125 to 1000 (in MiB/s) and must also be no greater than the IOPS divided by 4.

      • Confirm the configurations and Click Submit.
      • Check the results.

        Return to the Instances page. A few minutes later, click the instance name and check the new storage type on the displayed Summary page.

    diff --git a/docs/rds/umn/rds_08_0026.html b/docs/rds/umn/rds_08_0026.html index a319b3a28..c60ae33d5 100644 --- a/docs/rds/umn/rds_08_0026.html +++ b/docs/rds/umn/rds_08_0026.html @@ -3,7 +3,7 @@

    Managing Real-Time Sessions

    Scenarios

    You can view current session statistics of your instance, identify abnormal sessions, and kill the sessions.

    -

    Setting Slow Session Threshold

    1. Log in to the management console.
    2. Click in the upper left corner and select a region and a project.
    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
    4. On the Instances page, click the DB instance name.
    5. In the navigation pane, choose Sessions under DBA Assistant.
    6. On the Sessions page. You can perform the following operations on this tab page:

      • Viewing session statistics

        In the sessions statistics, you can view statistics on the slow sessions, active sessions, total sessions, long transaction sessions by user, access host, and database.

        +

        Setting Slow Session Threshold

        1. Log in to the management console.
        2. Click in the upper left corner and select a region and a project.
        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
        4. On the Instances page, click the DB instance name.
        5. In the navigation pane, choose Sessions under DBA Assistant.
        6. On the Sessions page, you can perform the following operations on this tab page:

          • Viewing session statistics

            In the sessions statistics, you can view statistics on the slow sessions, active sessions, total sessions, long transaction sessions by user, access host, and database.

          • Setting a slow session threshold

            Click next to the Slow Session Threshold field. In the displayed dialog box, set a slow session threshold and click OK. Sessions whose execution durations are greater than this threshold are automatically displayed.

          • Killing abnormal sessions

            In the session list, you can view session details. You can also select the abnormal session you want to end and click Kill Session to recover the database.

            A maximum of 100 sessions can be killed at a time.

            diff --git a/docs/rds/umn/rds_08_0033.html b/docs/rds/umn/rds_08_0033.html index 5f0eeb5ae..e1144965e 100644 --- a/docs/rds/umn/rds_08_0033.html +++ b/docs/rds/umn/rds_08_0033.html @@ -151,7 +151,8 @@

            Max. Concurrent Requests

            -

            If the number of concurrent SQL statements matching the keyword exceeds this limit, the SQL statements will not be executed. The value ranges from 0ms to 1,000,000,000ms.

            +

            If the number of concurrent SQL statements matching the keyword exceeds this limit, the SQL statements will not be executed. The value ranges from 0 to 1,000,000,000.

            +

            The value 0 indicates that SQL statements matching the keywords cannot be executed.

            Kill existing sessions that match this rule

            diff --git a/docs/rds/umn/rds_09_0065.html b/docs/rds/umn/rds_09_0065.html index 21ca08e62..79085effe 100644 --- a/docs/rds/umn/rds_09_0065.html +++ b/docs/rds/umn/rds_09_0065.html @@ -88,7 +88,7 @@ ResultSet resultSet = preparedStatement.executeQuery();

            -1

            -

            The number of SQL statements that can be concurrently executed (its priority is higher than that of concurrency control rules). If the value is less than or equal to 0, the number of SQL statements is not limited.

            +

            The number of SQL statements that can be concurrently executed (its priority is higher than that of SQL throttling rules). If the value is less than or equal to 0, the number of SQL statements is not limited.

            diff --git a/docs/rds/umn/rds_faq_0055.html b/docs/rds/umn/rds_faq_0055.html index cd46dcf61..9b5352bdf 100644 --- a/docs/rds/umn/rds_faq_0055.html +++ b/docs/rds/umn/rds_faq_0055.html @@ -2,8 +2,7 @@

            What Is the Maximum Number of Connections to an RDS DB Instance?

            RDS does not have constraints on the number of connections. This number is determined by the default value and value range of the DB engine. For example, you can set max_connections and max_user_connections in a parameter template to configure the maximum number of connections for an RDS for MySQL DB instance.

            -

            Changing the Maximum Number of Connections

            .

            -

            You can change the maximum number of connections using commands.

            +

            Changing the Maximum Number of Connections

            You can change the maximum number of connections using commands.

            1. Query the maximum number of connections.

              show global variables like 'max_connections';

            2. Change the value of max_connections under mysqld in the my.cnf file.

              [mysqld]

              max_connections = 1000

              diff --git a/docs/rds/umn/rds_glossary_0001.html b/docs/rds/umn/rds_glossary_0001.html index 482b365a2..c9fa733b7 100644 --- a/docs/rds/umn/rds_glossary_0001.html +++ b/docs/rds/umn/rds_glossary_0001.html @@ -1,7 +1,7 @@

              Glossary

              -

              For details about the glossaries in this document, see Glossary.

              +

              For details about the glossaries in this document, see Glossary.

              diff --git a/docs/rds/umn/rds_pg_05_0084.html b/docs/rds/umn/rds_pg_05_0084.html index 9172181d3..ff42bf94c 100644 --- a/docs/rds/umn/rds_pg_05_0084.html +++ b/docs/rds/umn/rds_pg_05_0084.html @@ -66,9 +66,8 @@

        Procedure

        1. Log in to the management console.
        2. Click in the upper left corner and select a region and a project.
        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
        4. On the Instances page, locate the target DB instance and choose More > Change Instance Class in the Operation column.

          Alternatively, click the target DB instance to go to the Summary page. Under Instance Class, click Configure.

          -

        5. On the displayed page, select a target Storage Type, for example, Extreme SSD for Storage Type and click Next.

          If the target storage type is Flexible SSD, click Disk QoS under Change Type and enter the IOPS and throughput.

          -
          • IOPS: Flexible SSD decouples capacity from performance and allows for tailored IOPS for your business requirements with fixed capacity.

            This parameter is available only for Flexible SSD. The value range is from 3000 to 128000. The IOPS is limited by the disk size and must be no greater than 500 times the disk capacity.

            -
          • Throughput: Flexible SSD decouples capacity from performance and allows for tailored throughput for your business requirements with fixed capacity.

            This parameter is available only for Flexible SSD. The value ranges from 125 to 1000 (in MiB/s) and must also be no greater than the IOPS divided by 4.

            +

          • On the Change Instance Class page, select a new storage type and click Next.

            If you select Flexible SSD, select Instance Specifications or Disk QoS for Change Type as needed.

            +
            • To change instance specifications, click Instance Specifications under Change Type and select the new specifications.
            • To change disk QoS, click Disk QoS under Change Type and enter the new IOPS and throughput.
              • IOPS: The value range is from 3000 to 128000. The IOPS is limited by the disk size and must be no greater than 500 times the disk capacity.
              • Throughput: The value range is from 125 to 1000 (in MiB/s) and must also be no greater than the IOPS divided by 4.

          • Confirm the configurations and Click Submit.
          • Check the results.

            Return to the Instances page. A few minutes later, click the instance name and check the new storage type on the displayed Summary page.

        diff --git a/docs/rds/umn/rds_sqlserver_05_0050.html b/docs/rds/umn/rds_sqlserver_05_0050.html index 9025e2871..ba35ef5ef 100644 --- a/docs/rds/umn/rds_sqlserver_05_0050.html +++ b/docs/rds/umn/rds_sqlserver_05_0050.html @@ -34,10 +34,10 @@

    Procedure

    1. Log in to the management console.
    2. Click in the upper left corner and select a region and a project.
    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
    4. On the Instances page, locate the target DB instance and choose More > Change Instance Class in the Operation column.

      Alternatively, click the target DB instance to go to the Summary page. Under Instance Class, click Configure.

      -

    5. On the displayed page, select a target Storage Type, for example, Extreme SSD for Storage Type and click Next.

      If the target storage type is Flexible SSD, click Disk QoS under Change Type and enter the IOPS and throughput.

      -
      • IOPS: Flexible SSD decouples capacity from performance and allows for tailored IOPS for your business requirements with fixed capacity.

        This parameter is available only for Flexible SSD. The value range is from 3000 to 128000. The IOPS is limited by the disk size and must be no greater than 500 times the disk capacity.

        -
      • Throughput: Flexible SSD decouples capacity from performance and allows for tailored throughput for your business requirements with fixed capacity.

        This parameter is available only for Flexible SSD. The value ranges from 125 to 1000 (in MiB/s) and must also be no greater than the IOPS divided by 4.

        +

      • On the Change Instance Class page, select a new storage type.

        If you select Flexible SSD, select Instance Specifications or Disk QoS for Change Type as needed.

        +
        • To change instance specifications, click Instance Specifications under Change Type and select the new specifications.
        • To change disk QoS, click Disk QoS under Change Type and enter the new IOPS and throughput.
          • IOPS: The value range is from 3000 to 128000. The IOPS is limited by the disk size and must be no greater than 500 times the disk capacity.
          • Throughput: The value range is from 125 to 1000 (in MiB/s) and must also be no greater than the IOPS divided by 4.
        +

      • Specify Scheduled Time and click Next.

        • Immediate: The change is applied immediately after the request is submitted.
        • During maintenance window: If you select this option, set the maintenance window to off-peak hours.

      • Confirm the configurations and Click Submit.
      • Check the results.

        Return to the Instances page. A few minutes later, click the instance name and check the new storage type on the displayed Summary page.