Using IAM Identity Policies to Grant Access to IEF
System-defined permissions in Permissions Management provided by Identity and Access Management (IAM) let you control access to IEF resources. With IAM, you can:
- Create IAM users or user groups for personnel based on your enterprise's organizational structure. Each IAM user has their own identity credentials for accessing IEF resources.
- Grant users only the permissions required to perform a given task based on their job responsibilities.
- Entrust a Huawei Cloud account or a cloud service to perform efficient O&M on your IEF resources.
If your Huawei Cloud account meets your permissions requirements, you can skip this section.
Figure 1 shows the process flow of identity policy-based authorization.
Prerequisites
Before granting permissions, learn about system-defined permissions supported by IEF in Permissions Management. To grant permissions for other services, learn about all system-defined permissions supported by IAM.
Process Flow
- On the IAM console, create an IAM user or create a user group.
Create a user or user group on the IAM console.
- Attach a system-defined identity policy (ASMReadOnlyPolicy as an example) to the user or user group.
Grant the permissions defined in the system-defined identity policy IEFReadOnlyPolicy to the user or user group, or attach the system-defined identity policy to it.
- Log in as the IAM user and verify permissions.
In the authorized region, perform the following operations:
- Choose Service List > Intelligent EdgeFabric. On the IEF console, click Register Edge Node to register an edge node. If the registration fails (assume that the current permission contains only IEFReadOnlyPolicy), IEFReadOnlyPolicy has already taken effect.
- Choose any other service from Service List. If a message appears indicating that you have insufficient permissions to access the service, IEFReadOnlyPolicy has already taken effect.
Example Custom Identity Policies
You can create custom identity policies to supplement the system-defined identity policies of IEF. For details about actions supported in custom identity policies, see .
To create a custom identity policy, choose either visual editor or JSON.
- Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy grammar.
- JSON: Create a JSON policy or edit an existing one.
For details, see Creating a Custom Identity Policy and Attaching It to a Principal.
When creating a custom identity policy, use the Resource element to specify the resources the identity policy applies to and use the Condition element (service-specific condition keys) to control when the identity policy is in effect. For details about the supported resource types and condition keys, see . The following provides examples of custom identity policies.
- Example 1: Grant permission to register and delete an edge node.
{ "Version": "5.0", "Statement": [ { "Effect": "Allow", "Action": [ "ief:node:create", "ief:node:delete" ] } ] } - Example 2: Create a custom identity policy containing multiple actions.
A custom identity policy can contain the actions of one or more services. Example identity policy containing multiple actions:
{ "Version": "5.0", "Statement": [ { "Effect": "Allow", "Action": [ "ief:node:create", "ief:node:delete" ] }, { "Effect": "Allow", "Action": [ "evs:volumes:create", "evs:volumes:list" ] }, { "Effect": "Allow", "Action": [ "ecs:cloudServers:createServers", "ecs:cloudServers:listServersDetails" ] } ] }
What is your overall rating for this page?
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.
For any further questions, feel free to contact us through the chatbot.
Chatbot
