Permissions Management
If you need to assign different permissions to employees in your enterprise to access your DAS resources, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you to securely access your cloud resources.
With IAM, you can use your account to create IAM users for your employees, and assign permissions to the users to control their access to specific resource types. For example, some software developers in your enterprise need to use DAS but must not delete DAS resources or perform any high-risk operations. To achieve this result, you can create IAM users for the software developers and grant them only the permissions required for using DAS resources.
If your account does not need individual IAM users for permissions management, you may skip over this section.
IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see IAM Service Overview.
DAS 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 they belong to and can perform specified operations on cloud services.
DAS is a project-level service deployed in specific physical regions. To assign DAS 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 DAS, you need to switch to a region where you have been authorized to use this service.
You can grant users permissions by using roles and policies.
- Roles: A type of coarse-grained authorization mechanism that defines permissions related to users responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you also need to assign other roles on which the permissions depend to take effect. However, roles are not ideal 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 and meets secure access control requirements. For example, you can grant IAM users only the permissions for managing a certain type of database resources.
Table 1 lists all the system-defined roles and policies supported by DAS.
Policy Name | Description | Type | Dependency |
|---|---|---|---|
DAS Administrator | DAS administrator, who has full permissions of DAS | System-defined role | This role depends on the Tenant Guest role. The DAS Administrator and Tenant Guest roles must be assigned in the same project. |
DAS FullAccess | Full permissions for DAS | System-defined policy | None |
- DAS depends on other services to implement the management and O&M of databases.
- If you authorize IAM users in fine-grained mode and want to use DAS to manage DB instances, add the DAS FullAccess system policy during authorization.
- With DAS, IAM users can view and manage the DB instances configured in the corresponding services.
By default, users with fine-grained authorization have the permissions to view the database login list in the Standard Edition, delete database login information, and access Cloud DBA on DAS. The instances viewed by these users are the same as those configured in the corresponding services.
Table 2 describes the common operations supported by each system-defined policy or role of DAS. Select the policy or role you need according to the following tables.
Operation | DAS Administrator | DAS FullAccess |
|---|---|---|
Logging in to a database | Supported | Supported |
Adding a login | Supported | Supported |
Modifying login information | Supported | Supported |
Deleting a login | Supported | Supported |
Viewing the login list in the Standard Edition | Supported | Supported |
Accessing Cloud DBA | Supported | Supported |
Operation | Action | Remarks |
|---|---|---|
Logging in to a database | das:connections:login | Configure the permissions for other services to query instances based on the instance type.
|
Obtaining the login information list | das:connections:list | Configure the permissions for other services to query instances based on the instance type.
|
Deleting login information | das:connections:delete | Configure the permissions for other services to query instances based on the instance type.
|
Adding a login | das:connections:create | Configure the permissions for other services to query instances based on the instance type.
|
Modifying a login | das:connections:modify | Configure the permissions for other services to query instances based on the instance type.
|
Policy Name | Description | Type | Dependency |
|---|---|---|---|
Tenant Administrator | Operation permissions:
Configure the OBS policies globally. | System-defined role | None |
OBS OperateAccess | Operation permissions: Users with this permission can view buckets, obtain basic bucket information, obtain bucket metadata, view objects, upload objects, download objects, delete objects, and obtain object ACLs. Configure the OBS policies globally. | System-defined policy | None |
DAS import and export features require the usage of OBS buckets. You need to obtain required OBS policies before using these features.
- Typically, it is recommended that you configure the Tenant Administrator policy that allows you to perform operations on OBS resources.
- If you do not want employees to have the high-risk permission for creating and deleting buckets, you can configure the OBS OperateAccess policy for the employees so that they can use the DAS features but cannot create and delete OBS buckets.
- DAS Permissions