From 1f3e1fa49f3078473efbf1354af52cc07326326c Mon Sep 17 00:00:00 2001 From: "Ru, Li Yi" Date: Fri, 6 Sep 2024 11:03:49 +0000 Subject: [PATCH] dds_umn_20240816 Reviewed-by: Wagner, Fabian Co-authored-by: Ru, Li Yi Co-committed-by: Ru, Li Yi --- docs/dds/umn/dds_01_0017.html | 2 +- docs/dds/umn/dds_01_0019.html | 2 +- docs/dds/umn/dds_glossary.html | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/dds/umn/dds_01_0017.html b/docs/dds/umn/dds_01_0017.html index e5c11f3b..6a57880b 100644 --- a/docs/dds/umn/dds_01_0017.html +++ b/docs/dds/umn/dds_01_0017.html @@ -3,7 +3,7 @@

User Permissions

IAM provides two types of user permissions by default: user management and resource management.

  • User management refers to the management of users, user groups, and user group rights.
  • Resource management refers to the control operations that can be performed by users on cloud service resources.
-

For details, see Permissions.

+

For details, see Permissions Management.

diff --git a/docs/dds/umn/dds_01_0019.html b/docs/dds/umn/dds_01_0019.html index b5460b30..20370263 100644 --- a/docs/dds/umn/dds_01_0019.html +++ b/docs/dds/umn/dds_01_0019.html @@ -6,7 +6,7 @@

If your account does not need individual IAM users for permissions management, you may skip over this topic.

IAM can be used free of charge. You pay only for the resources in your account.

DDS 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.

-

DDS is a project-level service deployed and accessed in specific physical regions. To assign GaussDB NoSQL 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 DDS, users need to switch to a region where they have been authorized to use DDS.

+

DDS is a project-level service deployed and accessed in specific physical regions. To assign DDS 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 DDS, users need to switch to a region where they have been authorized to use DDS.

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. For example, you can grant DDS users only the permissions for managing a certain type of resources.

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

diff --git a/docs/dds/umn/dds_glossary.html b/docs/dds/umn/dds_glossary.html index 4fa53ba0..e5640cae 100644 --- a/docs/dds/umn/dds_glossary.html +++ b/docs/dds/umn/dds_glossary.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.