Permissions
If you need to assign different permissions to employees in your enterprise to access your Cloud Eye resources, you can use IAM to manage fine-grained permissions. IAM provides identity authentication, permissions management, and access control, helping you secure access to your Huawei CloudHuawei 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 Cloud Eye resources but should not be allowed to delete the resources of other cloud services 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 Cloud Eye resources.
If your Huawei Cloud account does not require 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 What Is IAM?
Cloud Eye Permissions
By default, IAM users do not have permissions. To assign permissions to IAM users, add them to one or more groups, and attach policies or roles to these groups. The users then inherit permissions from the groups to which the users belong, and can perform specific operations on cloud services.
Cloud Eye is a project-level service deployed and accessed in specific physical regions. Cloud Eye permissions are assigned to users in specific regions (such as CN-Hong Kong) and only take effect in these regions. To make the permissions take effect in all regions, assign the permissions to users in each region. When users access Cloud Eye, they 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 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 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 Cloud Eye users only the permissions for managing a certain type of Cloud Eye resources.
A majority of fine-grained policies contain permissions for specific APIs, and permissions are defined using API actions. For the API actions supported by Cloud Eye, see Permissions Policies and Supported Actions.
Table 1 lists the system-defined permissions supported by Cloud Eye.
System-defined Role/Policy Name |
Description |
Type |
Dependency |
---|---|---|---|
CES FullAccessPolicy |
All permissions for Cloud Eye. Users granted these permissions can perform all operations on Cloud Eye. |
System-defined policies |
Cloud Eye monitoring involves querying resources of other cloud services. This policy contains the resource query permissions of some cloud services. If you encounter permission problems, configure required fine-grained permissions of the involved services. For details, see Supported Cloud Services. Alarm notification: depends on SMN FullAccess. Data dump: depends on OBS OperateAccess. |
CES ReadOnlyAccessPolicy |
Read-only permissions for viewing data on Cloud Eye |
System-defined policies |
Cloud Eye monitoring involves querying resources of other cloud services. This policy contains the resource query permissions of some cloud services. If you encounter permission problems, configure required fine-grained permissions of the involved services. For details, see Supported Cloud Services. |
CES AgentAccess |
Permissions required for the Cloud Eye Agent to run
NOTE:
To ensure that the Cloud Eye Agent can provide services, you need to configure an agency. For details, see How Do I Configure an Agency? |
System-defined policies |
None |
CES Administrator |
Administrator permissions for Cloud Eye |
System-defined roles |
Depends on the Tenant Guest policy. Tenant Guest: a global policy, which must be assigned in the Global project |
CES AgencyCheck Access |
IAM operation permissions to be authorized for Cloud Eye to check tenant agency permissions |
System-defined policies |
A collection of agency policies on which OBS dump of cloud service monitoring, data dump, server monitoring, and more Cloud Eye functions depend. This policy contains permission set that needs to be granted to the IAM operations in the agency. For example, if you encounter agency-related permission issues when using these functions, you need to configure fine-grained authorization for IAM agency operations. |
CES Global FullAccess |
All permissions for Cloud Eye global services |
System-defined policies |
A collection of agency policies on which Cloud Eye functions, such as website monitoring, WAN quality monitoring, and alarm notifications, depend. This policy covers global services of Cloud Eye and a collection of global service operations on which Cloud Eye depends. If you encounter permission issues when these functions, you need to configure the permission set. |
CES FullAccess |
All permissions for Cloud Eye. Users granted these permissions can perform all operations on Cloud Eye.
NOTE:
It is recommended that you use CES FullAccessPolicy because CES FullAccess does not meet the least privilege principle. |
System-defined policies |
Cloud Eye monitoring involves querying resources of other cloud services. This policy contains the resource query permissions of some cloud services. If you encounter permission problems, configure required fine-grained permissions of the involved services. For details, see Supported Cloud Services. Alarm notification: depends on SMN FullAccess. Data dump: depends on OBS OperateAccess. |
CES ReadOnlyAccess |
Read-only permissions for viewing data on Cloud Eye
NOTE:
It is recommended that you use CES ReadOnlyAccessPolicy because CES ReadOnlyAccess does not meet the least privilege principle. |
System-defined policies |
Cloud Eye monitoring involves querying resources of other cloud services. This policy contains the resource query permissions of some cloud services. If you encounter permission problems, configure required fine-grained permissions of the involved services. For details, see Supported Cloud Services. |
Table 2 lists common operations supported by the Cloud Eye system-defined permissions.
Feature |
Operation |
CES FullAccessPolicy |
CES ReadOnlyAccessPolicy |
CES Administrator (The Tenant Guest policy must be added at the same time.) |
Tenant Guest |
---|---|---|---|---|---|
Monitoring Overview |
Viewing monitoring overview |
√ |
√ |
√ |
√ |
Viewing full screen monitoring |
√ |
√ |
√ |
√ |
|
Monitoring Panels |
Creating a monitoring panel |
√ |
× |
√ |
× |
Viewing full screen monitoring |
√ |
√ |
√ |
√ |
|
Querying a monitoring panel |
√ |
√ |
√ |
√ |
|
Deleting a monitoring panel |
√ |
× |
√ |
× |
|
Adding a graph |
√ |
× |
√ |
× |
|
Viewing a graph |
√ |
√ |
√ |
√ |
|
Modifying a graph |
√ |
× |
√ |
× |
|
Deleting a graph |
√ |
× |
√ |
× |
|
Adjusting the position of a graph |
√ |
× |
√ |
× |
|
Resource Groups |
Creating a resource group |
√ |
× |
√ |
× |
Viewing the resource group list |
√ |
√ |
√ |
√ |
|
Viewing resource groups (Resource Overview) |
√ |
√ |
√ |
√ |
|
Viewing resource groups (Unhealthy Resources) |
√ |
√ |
√ |
√ |
|
Viewing resource groups (Alarm Rules) |
√ |
√ |
√ |
√ |
|
Viewing resource groups (Alarm Records) |
√ |
√ |
√ |
√ |
|
Modifying a resource group |
√ |
× |
√ |
× |
|
Deleting a resource group |
√ |
× |
√ |
× |
|
Alarm Rules |
Creating an alarm rule |
√ |
× |
√ |
× |
Modifying an alarm rule |
√ |
× |
√ |
× |
|
Enabling an alarm rule |
√ |
× |
√ |
× |
|
Disabling an alarm rule |
√ |
× |
√ |
× |
|
Deleting an alarm rule |
√ |
× |
√ |
× |
|
Exporting alarm rules |
√ |
× |
√ |
× |
|
Querying the alarm rule list |
√ |
√ |
√ |
√ |
|
Viewing details of an alarm rule |
√ |
√ |
√ |
√ |
|
Viewing a graph |
√ |
√ |
√ |
√ |
|
Alarm Records |
Viewing alarm records |
√ |
√ |
√ |
√ |
Alarm Templates |
Viewing a default template |
√ |
√ |
√ |
√ |
Viewing a custom template |
√ |
√ |
√ |
√ |
|
Creating a custom template |
√ |
× |
√ |
× |
|
Modifying a custom template |
√ |
× |
√ |
× |
|
Deleting a custom template |
√ |
× |
√ |
× |
|
Server Monitoring |
Viewing the server list |
√ |
√ |
√ |
√ |
Viewing server monitoring metrics |
√ |
√ |
√ |
√ |
|
Installing the Agent |
√ (You must have the ECS FullAccess permission.) |
× |
√ (You must have the ECS FullAccess permission.) |
× |
|
Restoring the Agent configurations |
√ (You must have the Security Administrator and ECS FullAccess permissions.) |
× |
√ (You must have the Security Administrator and ECS FullAccess permissions.) |
× |
|
Uninstalling the Agent |
√ (You must have the ECS FullAccess permission.) |
× |
√ (You must have the ECS FullAccess permission.) |
× |
|
Configuring process monitoring |
√ |
× |
√ |
× |
|
Configuring monitoring for a process |
√ |
× |
√ |
× |
|
Cloud Service Monitoring |
Viewing the cloud service list |
√ (See Supported Cloud Services.) |
√ (See Supported Cloud Services.) |
√ |
√ |
Querying cloud service metrics |
√ |
√ |
√ |
√ |
|
Custom Monitoring |
Adding custom monitoring data |
√ |
× |
√ |
× |
Viewing the custom monitoring list |
√ |
√ |
√ |
√ |
|
Viewing custom monitoring data |
√ |
√ |
√ |
√ |
|
Event Monitoring |
Adding a custom event |
√ |
× |
√ |
× |
Viewing the event list |
√ |
√ |
√ |
√ |
|
Viewing details of an event |
√ |
√ |
√ |
√ |
|
Data Dumping to DMS Kafka |
Creating a dump task |
√ |
× |
√ |
× |
Querying data dumping tasks |
√ |
√ |
√ |
√ |
|
Querying a specified data dump task |
√ |
√ |
√ |
√ |
|
Modifying a data dump task |
√ |
× |
√ |
× |
|
Starting a data dump task |
√ |
× |
√ |
× |
|
Stopping a data dump task |
√ |
× |
√ |
× |
|
Deleting a data dump task |
√ |
× |
√ |
× |
|
Others |
Configuring data storage |
√ (You must have the OBS Bucket Viewer permission.) |
× |
√ (You must have the Tenant Administrator permission.) |
× |
Exporting monitoring data |
√ |
× |
√ |
× |
|
Sending an alarm notification |
√ |
× |
√ |
× |
Roles or Policies Required for Operations on the Cloud Eye Console
To grant an IAM user the permissions to view or use resources of other cloud services on the Cloud Eye console, you must first grant the CES Administrator, CES FullAccess, or CES ReadOnlyAccess policy to the user group to which the user belongs and then grant the dependency roles or policies listed in Table 3 to the user. These dependency policies will allow the IAM user to access resources of other cloud services.
Function |
Dependent Services |
Roles or Policies Required |
---|---|---|
Cloud service monitoring |
|
IAM users with the CES Administrator, CES FullAccess, or CES ReadOnlyAccess permission can view information about cloud service monitoring. |
Helpful Links
- IAM Service Overview
- For details about how to create a user group and user and grant the CES Administrator permissions, see Creating a User and Granting Permissions.
- For the actions supported by fine-grained policies, see Permissions Policies and Supported Actions in Cloud Eye 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