Permissions

If you need to assign different permissions to personnel in your enterprise to access your cloud 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 securely access your Huawei Cloud resources.

With IAM, you can create IAM users for your employees, and assign permissions to the users to control their access to specific resource types. For example, if you need to grant some users the permissions to view TMS resources, but do not want these users to delete predefined tags, you can create users using IAM and assign TMS ReadOnlyAccess permissions to these users.

If your Huawei Cloud account does not require IAM for permissions management, you can skip 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.

TMS Permissions

New IAM users do not have any permissions assigned by default. You need to first add them to one or more groups and attach policies or roles to these groups. The users then inherit permissions from the groups and can perform specified operations on cloud services based on the permissions they have been assigned.

TMS is a global service deployed for all regions. When you set the authorization scope to Global services, users have permission to access TMS resources in all regions.

You can grant permissions by using roles and policies.

Roles: A coarse-grained authorization strategy provided by IAM to assign permissions based on users' job responsibilities Only a limited number of service-level roles are available for authorization. When using roles to grant permissions, you must also assign other roles which the permissions depend on to take effect. Roles are not ideal for fine-grained authorization and least privilege access.
Policies: A fine-grained authorization strategy that defines permissions required to perform operations on specific cloud resources under certain conditions. This type of authorization is more flexible and is ideal for least privilege access. The administrator can restrict a user to only specified operations on TMS using IAM policies. For example, if the user is granted a fine-grained permission to only view predefined tags, the user cannot perform other operations on predefined tags (such as creating or deleting predefined tags) with this permission. A majority of fine-grained policies contain permissions for specific APIs. For the API actions supported by TMS, see Permissions Policies and Supported Actions.

Table 1 lists all TMS system-defined policies and roles. Some TMS policies depend on the policies of other services to take effect. When you assign TMS permissions to users, you also assign dependent policies for the TMS permissions to take effect.

**Table 1** TMS system-defined permissions
Role/Policy Name	Description	Type	Dependencies
TMS FullAccess	Full permissions for TMS.	System-defined policy	-
TMS ReadOnlyAccess	Read-only permissions for TMS.	System-defined policy	-
TMS Administrator	Full permissions for TMS. Users with these permissions can query, create, delete, import, or export predefined tags, and create, delete, modify, or query resource tags.	System-defined role	Dependent on the following policies: Tenant Guest: a global/project-level policy that grants read-only permissions for all cloud services (except IAM). Server Administrator: A project-level policy, which must be assigned in the same project as the TMS Administrator policy. Tenant Administrator: A global/project-level policy that grants permissions of all cloud service administrators (except the IAM administrator permissions). IMS Administrator: a project-level policy, which must be assigned in the same project as the TMS Administrator policy AutoScaling Administrator: a project-level policy, which must be assigned in the same project as the TMS Administrator policy VPC Administrator: a project-level policy, which must be assigned in the same project as the TMS Administrator policy VBS Administrator: a project-level policy, which must be assigned in the same project as the TMS Administrator policy

Table 2 lists the common operations supported by TMS system-defined permissions.

**Table 2** Common operations supported by system-defined permissions
Operation	TMS FullAccess	TMS ReadOnlyAccess	TMS Administrator
Querying the cloud resource list	Supported (permissions of corresponding services for querying resources required)	Supported (permissions of corresponding services for querying resources required)	Supported (Tenant Guest required)
Creating a key	Supported	Not supported	Supported (Tenant Guest required)
Viewing resource tags	Supported	Supported	Supported (Tenant Guest required)
Creating resource tags	Supported (permissions of corresponding services for creating tags required)	Not supported	Supported (Tenant Guest and corresponding project policies of cloud resources required. For example, if you need to manage VPC tags, select Tenant Guest in the same project.)
Modifying resource tags	Supported (permissions of corresponding services for creating, deleting, and viewing tags required)	Not supported	Supported (Tenant Guest and corresponding project policies of cloud resources required. For example, if you need to manage VPC tags, select Tenant Guest in the same project.)
Deleting resource tags	Supported (permissions of corresponding services for deleting tags required)	Not supported	Supported (Tenant Guest and corresponding project policies of cloud resources required. For example, if you need to manage VPC tags, select Tenant Guest in the same project.)
Querying predefined tags	Supported	Supported	Supported
Creating predefined tags	Supported	Not supported	Supported
Deleting predefined tags	Supported	Not supported	Supported
Exporting predefined tags	Supported	Supported	Supported
Importing predefined tags	Supported	Not supported	Supported

If you need to perform operations on tags of cloud resources on TMS console, you must have related permissions for viewing, creating, and deleting resource tags and required permissions for the services to which the resources belong. Modify a resource tag involves a process of deleting the old tag and then creating a new tag (with the same tag key but different tag values). So, to modify a cloud resource tag, you must have both related TMS permissions and service permissions to delete and create tags.

For system-defined permissions: If you need to add or delete tags for ECS resources on TMS console, both TMS FullAccess permissions and ECS FullAccess permissions are required.
For custom permissions: If you need to view ECS resources and tags on the TMS console, not only tms:resourceTags:list permissions, but ecs:servers:getTags and ecs:servers:get permissions are required.

For details about all system-defined permissions of services supported by IAM, see System-defined Permissions. For more information about fine-grained permissions of each service, see corresponding documentations of each service.

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot

Permissions

TMS Permissions

Related Documents

Feedback

Was this page helpful?