Help Center> Web3 Node Engine Service> Service Overview> Permissions Management
Updated on 2023-12-05 GMT+08:00
View PDF

Permissions Management

If you need to assign different permissions to employees in your enterprise to access your NES 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 secure 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 details about permission configurations, see Permissions Management.

You can skip this section if you do not need fine-grained permissions management.

IAM is free of charge. You pay only for the resources in your account.

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 also need to 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 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 Elastic Cloud Server (ECS) users only the permissions for managing a certain type of ECSs.

NES Permissions

By default, new IAM users do not have any permissions assigned. You must add them to user groups and assign permissions policies or roles to these groups. Users then inherit permissions from the groups. This process is called authorization. Users can perform specified operations on cloud services based on their assigned permissions.

NES is a project-level service deployed for specific regions. To assign NES 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 NES, the users need to switch to the authorized region.

The following table lists all system-defined policies supported by NES.

Table 1 NES system permissions

Role/Policy Name

Description

Permission Type

Dependency

BCS Administrator

Full operation permissions for enhanced Hyperledger Fabric BCS

System-defined role

Tenant Guest, Server Administrator, ELB Administrator, SFS Administrator, SWR Admin, APM FullAccess, AOM FullAccess, CCE Administrator, VPC Administrator, EVS Administrator, and CCE Cluster Admin

BCS NES FullAccess

Full permissions for NES

System-defined policy

None

BCS NES ReadOnlyAccess

Read-only permissions for NES

System-defined policy

None

BCS NES FullAccess Content

{
    "Version": "1.1",
    "Statement": [
        {
            "Action": [
                "bcs:nes*:*"
            ],
            "Effect": "Allow"
        }
    ]
}

BCS NES ReadOnlyAccess Content

{
    "Version": "1.1",
    "Statement": [
        {
            "Action": [
                "bcs:nes*:get*",
                "bcs:nes*:list*"
            ],
            "Effect": "Allow"
        }
    ]
}