Permissions
If you need to assign different permissions to employees in your enterprise to access your EVS resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you securely access your cloud resources.
With IAM, you can control access to specific cloud service resources. For example, if you want some resource management personnel in your enterprise to view EVS resources but do not want them to delete EVS resources or perform any other high-risk operations, you can grant permission to view EVS resources but not permission to delete them.
If your account does not require IAM for permissions management, you can skip this section.
IAM is a free service. You only pay for the resources in your account. For more information about IAM, see section "Service Overview" in the Identity and Access Management User Guide.
EVS 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.
EVS is a project-level service deployed for specific regions. To assign EVS permissions to a user group, specify the scope as region-specific projects and select a project 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 EVS, users need to switch to a region where they have been authorized to use EVS.
- 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 ECS users only the permissions for managing a certain type of ECSs. Most policies define permissions based on APIs. For the API actions supported by EVS, see section "Permissions Policies and Supported Actions" in the Elastic Volume Service API Reference.
|
Role/Policy Name |
Description |
Type |
Dependency |
|---|---|---|---|
|
EVS FullAccess |
Full permissions for EVS. Users granted these permissions can create, attach, detach, query, and delete EVS resources, and expand capacity of EVS disks. |
System-defined policy |
None |
|
EVS ReadOnlyAccess |
Read-only permissions for EVS. Users granted these permissions can view EVS resource data only. |
System-defined policy |
None |
|
Operation |
EVS FullAccess |
EVS ReadOnlyAccess |
|---|---|---|
|
Creating disks |
√ |
x |
|
Viewing disk list |
√ |
√ |
|
Viewing disk details |
√ |
√ |
|
Attaching disks |
√ |
x |
|
Detaching disks |
√ |
x |
|
Deleting disks |
√ |
x |
|
Expanding disk capacities |
√ |
x |
|
Adding tags for disks |
√ |
x |
|
Modifying tags |
√ |
x |
|
Deleting tags |
√ |
x |
|
Searching for disks by tag |
√ |
√ |
|
Changing disk names |
√ |
x |
Related Links
- Permissions management sections in the Identify and Access Management User Guide
- Creating a User and Granting EVS Permissions
- Section "Permissions Policies and Supported Actions" in the Elastic Volume Service API Reference
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
