Permissions
If you need to assign different permissions to employees in your enterprise to access your cloud resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your resources.
With IAM, you can use your Huawei Cloud account to create IAM users, and assign permissions to the users to control their access to specific resources. For example, some software developers in your enterprise need to use resources but cannot delete them or perform any high-risk operations. To achieve this result, you can create IAM users for the developers and grant them only the permissions for using resources.
You can skip this section if you do not need fine-grained permissions management.
IAM is a free service. You only pay for the resources in your account.
For more information about IAM, see IAM Service Overview.
GeminiDB Permissions
By default, new IAM users do not have any permissions assigned. To assign permissions to these new users, you need to add them to one or more groups, and attach permissions policies or roles to these groups.
GeminiDB is a project-level service deployed in specific physical regions. When assigning GeminiDB permissions to a user group, you need to specify region-specific projects where the permissions will take effect. If you select All projects, the permissions will be granted for all region-specific projects. To access GeminiDB, you need to switch to the region where you are authorized.
You can grant users permissions using roles and policies.
- Roles: A type of coarse-grained authorization mechanism that provides only a limited number of service-level roles. When using roles to grant permissions, you also need to assign other dependent roles. Roles are not ideal for fine-grained authorization and secure access control.
- Policies: A 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 more secure access control. For example, you can grant ECS users only the permissions for managing a certain type of ECSs. For API actions supported by GeminiDB, see Permissions Policies and Supported Actions.
Table 1 lists all the system-defined roles and policies supported by GeminiDB.
Policy Name/System Role |
Description |
Type |
Dependency |
---|---|---|---|
GeminiDB FullAccess |
All permissions for GeminiDB |
System-defined policy |
To create a yearly/monthly instance, you need to configure the following CBC actions:
To unsubscribe from a yearly/monthly instance, you need to configure the following CBC action:
To use storage autoscaling, configure the following actions for IAM users:
GeminiDB FullAccess already contains the iam:agencies:listAgencies, iam:roles:listRoles, and iam:agencies:pass permissions. GeminiDB is a region-level service, and IAM is a global service. If you want to grant GeminiDB FullAccess to a project, grant BSS ServiceAgencyReadPolicy (global service) to it as well. Granting GeminiDB FullAccess to all projects eliminates the need for additional configuration when using IAM actions. BSS ServiceAgencyCreatePolicy contains the following permissions:
|
GeminiDB ReadOnlyAccess |
Read-only permissions for GeminiDB |
System-defined policy |
None |
Table 2 lists the common operations supported by each system-defined policy or role of GeminiDB. Select the policies or roles as required.
Operation |
GeminiDB FullAccess |
GeminiDB ReadOnlyAccess |
---|---|---|
Creating an instance |
√ |
x |
Querying instances |
√ |
√ |
Querying details of an instance |
√ |
√ |
Querying tasks |
√ |
√ |
Deleting an instance |
√ |
x |
Restarting an instance |
√ |
x |
Resetting a password |
√ |
x |
Changing a security group |
√ |
x |
Changing a database port |
√ |
x |
Binding or unbinding an EIP |
√ |
x |
Scaling up storage space |
√ |
x |
Changing specifications |
√ |
x |
Adding nodes |
√ |
x |
Deleting nodes |
√ |
x |
Modifying a backup policy |
√ |
x |
Renaming an instance |
√ |
x |
Creating a manual backup |
√ |
x |
Querying backups |
√ |
√ |
Restoring data to a new instance |
√ |
x |
Deleting a backup |
√ |
x |
Creating a parameter template |
√ |
x |
Querying parameter templates |
√ |
√ |
Modifying a parameter template |
√ |
x |
Deleting a parameter template |
√ |
x |
Querying enterprise project quotas |
√ |
√ |
Modifying enterprise project quotas |
√ |
x |
Enabling or disabling SSL |
√ |
x |
Stopping a backup |
√ |
x |
Table 3 lists common GeminiDB operations and corresponding actions. You can refer to this table to customize permission policies.
Operation |
Actions |
Authorization Scope |
Remarks |
---|---|---|---|
Accessing the instance creation page |
|
Supported:
|
The VPC, subnet, and security group are displayed on the instance creation page. |
Creating an instance |
|
Supported:
|
If the default VPC, subnet, and security group are used, the vpc:*:create permission must be configured. To create an encrypted instance, you need to configure the KMS Administrator permission for the project. |
Querying instances |
nosql:instance:list |
Supported:
|
- |
Querying details of an instance |
nosql:instance:list |
Supported:
|
If the VPC, subnet, and security group need to be displayed on the instance details page, add the vpc:*:get and vpc:*:list actions. |
Querying tasks |
nosql:task:list |
Supported:
|
- |
Deleting an instance |
nosql:instance:delete |
Supported:
|
When deleting an instance, you need to delete the IP address on the data side. |
Restarting an instance |
nosql:instance:restart |
Supported:
|
- |
Resetting a password |
nosql:instance:modifyPasswd |
Supported:
|
- |
Changing a security group |
nosql:instance:modifySecurityGroup |
Supported:
|
- |
Changing a database port |
nosql:instance:modifyPort |
Supported:
|
- |
Binding an EIP |
nosql:instance:bindPublicIp |
Supported:
|
When binding an EIP, you need to query the created EIP.
For details, see Floating IP Address. |
Unbinding an EIP |
nosql:instance:unbindPublicIp |
Supported:
|
For details, see Floating IP Address. |
Scaling up storage space |
nosql:instance:modifyStorageSize |
Supported:
|
- |
Changing specifications |
nosql:instance:modifySpecification |
Supported:
|
- |
Adding nodes |
|
Supported:
|
- |
Deleting nodes |
nosql:instance:reduceNode |
Supported:
|
Deleting nodes from a cluster |
Modifying a backup policy |
nosql:instance:modifyBackupPolicy |
Supported:
|
- |
Renaming an instance |
nosql:instance:rename |
Supported:
|
- |
Creating a manual backup |
nosql:backup:create |
Supported:
|
- |
Querying backups |
nosql:backup:list |
Supported:
|
- |
Downloading a backup file |
nosql:backup:download |
Supported:
|
- |
Restoring data to a new instance |
|
Supported:
|
The KMS Administrator permission needs to be configured for the encrypted instance in the project. |
Restoring data to an existing instance |
nosql:backup:restoreToExistInstance |
Supported:
|
- |
Deleting a backup |
nosql:backup:delete |
Supported:
|
- |
Creating a parameter template |
nosql:param:create |
Supported:
|
- |
Querying parameter templates |
nosql:param:list |
Supported:
|
- |
Changing parameter values in a parameter template |
nosql:param:modify |
Supported:
|
- |
Changing parameter settings of an instance node |
nosql:instance:modifyParameter |
Supported:
|
- |
Deleting a parameter template |
nosql:param:delete |
Supported:
|
- |
Performing an operation on tags |
|
Supported:
|
- |
Tag list |
|
Supported:
|
- |
Querying enterprise project quotas |
nosql:quota:list |
Supported:
|
- |
Modifying enterprise project quotas |
nosql:quota:modify |
Supported:
|
- |
Enabling or disabling local log auditing |
nosql:instance:switchAuditLog |
Supported:
|
- |
Downloading audit logs |
nosql:instance:downloadAuditLog |
Supported:
|
- |
Deleting audit logs |
nosql:instance:deleteAuditLog |
Supported:
|
- |
Enabling or disabling the display of slow query logs in plaintext |
nosql:instance:modifySlowLogPlaintextSwitch |
Supported:
|
- |
Enabling or disabling SSL |
nosql:instance:switchSSL |
Supported:
|
- |
Changing a private IP address |
nosql:instance:modifyPrivateIp |
Supported:
|
- |
Switching between primary and standby instances |
nosql:instance:switchover |
Supported:
|
- |
Upgrading the minor version of an instance |
nosql:instance:upgradeDatabaseVersion |
Supported:
|
- |
Stopping a backup |
nosql:backup:stop |
Supported:
|
- |
Querying a log group |
lts:groups:get |
Supported:
|
- |
Querying a log stream |
lts:topics:get |
Supported:
|
- |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot