Permissions Management
If you need to assign different permissions to employees in your enterprise to access your AS resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you securely access to your HUAWEI CLOUD 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 AS resources but should not be allowed to delete the resources or perform any other high-risk operations. In this scenario, you can create IAM users for the software developers and grant them only the permissions required for using AS resources.
If your HUAWEI CLOUD account does not need individual IAM users for permissions management, 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.
AS 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.
AS is a project-level service deployed and accessed in specific physical regions. To assign AS 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 AS, the users need to switch to a region where they 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 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 AS users only the permissions for managing a certain type of ECSs. Most policies define permissions based on APIs. For the API actions supported by AS, see Permissions Policies and Supported Actions.
Table 1 lists all the system policies supported by AS.
Table 1 System-defined permissions supported by AS Policy Name
Description
Category
AutoScaling FullAccess
All operation permissions on all AS resources
System-defined policy
AutoScaling ReadOnlyAccess
Read-only permissions on all AS resources
System-defined policy
AutoScaling Administrator
All operation permissions on all AS resources
System role
Table 2 lists the common operations supported by each system-defined policy of AS. Select the policies as required.
Table 2 Common operations supported by each system-defined policy of AS Operation
AutoScaling FullAccess
AutoScaling ReadOnlyAccess
AutoScaling Administrator
Creating an AS group
√
x
√
Modifying an AS group
√
x
√
Querying details about an AS group
√
√
√
Deleting an AS group
√
x
√
Creating an AS configuration
√
x
√
Creating an AS policy
√
x
√
Creating a bandwidth scaling policy
√
x
√
Last Article: AS and Other Services
Next Article: Basic Concepts
Did this article solve your problem?
Thank you for your score！Your feedback would help us improve the website.