Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

IAM-based Access Control

Updated on 2024-11-05 GMT+08:00

If you need to assign different permissions to employees 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 cloud resources. 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.

With IAM, you can control access to specific Huawei Cloud resources. For example, if you want some software developers in your enterprise to use CCI resources but do not want them to delete resources or perform any other high-risk operations, you can grant permission to use CCI resources but not permission to delete them.

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. Huawei Cloud services depend on each other. When you grant permissions using roles, you also need to attach any existing role dependencies. 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. For example, you can grant users only permission to manage ECSs of a certain type. A majority of fine-grained policies contain permissions for specific APIs, and permissions are defined using API actions. For the API actions supported by CCI, see Permissions Policies and Supported Actions.

IAM supports both role-based access control (RBAC) and attribute-based access control (ABAC).

RBAC is a role-based authorization model. By default, a new principal does not have any permissions. You need to assign a system-defined role, system-defined policy, or custom policy to the principal and select the authorization scope so that the principal can have the specified permissions.

ABAC is a policy-based authorization model, which offers more fine-grained, flexible access control. An administrator can tailor access control policies based on service requirements and then attach or grant the policies to a principal so that the principal can have the specified permissions The principal can then perform operations on specified cloud services.

The following table describes the differences between these two authorization models.

Table 1 Differences between RBAC and ABAC

Authorization Model

Authorization Using

Permissions

Authorization Method

Scenario

RBAC

Roles

  • System-defined roles
  • System-defined policies
  • Custom policies

Granting roles or policies to principals

It offers a simple approach to access management but is not always flexible enough. For more granular permissions control, administrators need to constantly add more roles, which may lead to role explosion. This model can work well for small and medium-sized enterprises where there is not too much work involved in maintaining roles and permissions.

ABAC

Policies

  • System-defined policies
  • Custom policies
  • Granting policies to principals
  • Attaching policies to principals

It gives you more granular, more flexible control of your resources. There is no need to modify existing rules to accommodate new users. All administrators need to do is assign relevant attributes to the new users. However, this model can be hard to set up. It requires a certain amount of expertise. ABAC is suitable for medium- and large-sized enterprises.

Assume that you want to grant IAM users permission to create ECSs in CN North-Beijing4 and OBS buckets in CN South-Guangzhou. With RBAC, the administrator needs to create two custom policies and attach both to the IAM users. With ABAC, the administrator only needs to create one custom policy, configure the condition key g:RequestedRegion for the policy, and then attach the policy to the users or grant the users the access permissions to the specified regions. ABAC is more flexible than RBAC.

Policies and actions in the two authorization models are not interoperable. You are advised to use the ABAC authorization model. For details about system-defined permissions, see System-defined Permissions in RBAC and System-defined Permissions in ABAC.

For more information about IAM, see IAM Service Overview.

System-defined Permissions in RBAC

CCI supports RBAC. 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.

CCI is a project-level service deployed for specific regions. When you set Scope to Region-specific projects and select the specified projects (for example, ap-southeast-2) in the specified regions (for example, AP-Bangkok), the users only have permissions for CCI resources in the selected projects. If you set Scope to All resources, the users have permissions for CCI resources in all region-specific projects. When accessing CCI, the users need to switch to the authorized region.

Table 2 lists all the system-defined permissions for CCI. System-defined policies in RBAC and ABAC are not interoperable.

Table 2 System-defined permissions for CCI

Role/Policy Name

Description

Type

CCI FullAccess

Full permissions for CCI. Users granted these permissions can create, delete, query, and update all CCI resources.

System-defined policy

CCI ReadOnlyAccess

Read-only permissions for CCI. Users granted these permissions can only view CCI resources.

System-defined policy

CCI CommonOperations

Common user permissions for CCI. Users granted these permissions can perform all operations except creating, deleting, and modifying role-based access control (RBAC) policies, networks, and resources in the namespaces.

System-defined policy

CCI Administrator

Administrator permissions for CCI. Users granted these permissions can create, delete, query, and update all CCI resources.

System-defined role

Table 3 lists the common operations supported by system-defined permissions for CCI.

Table 3 Common operations supported by system-defined permissions

Operation

CCI FullAccess

CCI ReadOnlyAccess

CCI CommonOperations

Creating a Deployment

x

Deleting a Deployment

x

Viewing a Deployment

Upgrading a workload

x

Scaling a workload

x

Deleting a pod

x

Viewing a pod

Creating a job

x

Deleting a job

x

Viewing a job

Creating a cron job

x

Deleting a cron job

x

Viewing cron jobs

Viewing the resource usage

Adding an EVS volume

x

Deleting an EVS volume

x

Viewing an EVS volume

Creating a ConfigMap

x

Deleting ConfigMaps

x

Viewing a ConfigMap

Creating a secret

x

Deleting a secret

x

Viewing a secret

Adding an SSL certificate

x

Deleting an SSL certificate

x

Viewing an SSL certificate

Adding log storage

x

Viewing logs

Installing an add-on

x

Deleting an add-on

x

Viewing an add-on

Viewing permissions

Granting permissions

x

x

Canceling permissions

x

x

Querying a specified namespace

Creating a namespace

x

x

Deleting a namespace

x

x

Creating a network

x

x

Deleting a network

x

x

Listing all networks

Viewing a network

System-defined Permissions in ABAC

CCI supports ABAC. Table 4 lists all the system-defined policies for CCI with ABAC. System-defined policies in RBAC and ABAC are not interoperable.

Table 4 System-defined policies for CCI

Policy Name

Description

Type

CCIFullAccessPolicy

Full permissions for CCI

System-defined policy

CCIReadOnlyPolicy

Read-only permissions for CCI

System-defined policy

Table 5 lists the common operations supported by system-defined policies for CCI.

Table 5 Common operations supported by system-defined permissions

Operation

CCIFullAccessPolicy

CCIReadOnlyPolicy

Creating a pod

x

Deleting a pod

x

Viewing a pod

Viewing the resource usage

Creating a ConfigMap

x

Deleting a ConfigMap

x

Viewing a ConfigMap

Creating a secret

x

Deleting a secret

x

Viewing a secret

Viewing logs

Querying a specified namespace

Creating a namespace

x

Deleting a namespace

x

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback