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 cloud service resources.

With IAM, you can use your 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 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 account does not require individual IAM users for permissions management, skip this section.

IAM is a free service. You pay only for the resources in your account. For more information about IAM, see IAM Service Overview.

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. Therefore, Cloud Eye permissions are assigned to users in specific regions and only take effect in these regions. If you want the permissions to take effect in all regions, you need to 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.
Most policies define permissions based on APIs. For the API actions supported by Cloud Eye, see Permissions Policies and Supported Actions.

Table 1 lists the system-defined policies supported by Cloud Eye.

**Table 1** System policies
Policy Name	Description	Dependency	Type
CES Administrator	Administrator permissions for Cloud Eye	Depend on the Tenant Guest policy. Tenant Guest: a global policy, which must be assigned in the Global project	System-defined role
CES FullAccess	Administrator permissions for Cloud Eye. Users granted these permissions can perform all operations on Cloud Eye.	The Cloud Eye monitoring function involves querying resources of other cloud services, which requires the cloud services to support fine-grained authorization.	System-defined policy
CES ReadOnlyAccess	Read-only permissions for Cloud Eye. Users granted these permissions can only view Cloud Eye data.	The Cloud Eye monitoring function involves querying resources of other cloud services, which requires the cloud services to support fine-grained authorization.	System-defined policy

Table 2 lists common operations supported by the Cloud Eye system policies.

**Table 2** Common operations supported by the Cloud Eye system policies
Feature	Operation	CES Administrator (The Tenant Guest policy must be added at the same time.)	Tenant Guest	CES FullAccess	CES ReadOnlyAccess
Monitoring Overview	Viewing monitoring overview	√	√	√	√
Monitoring Overview	Viewing full screen monitoring	√	√	√	√
Dashboards	Creating a dashboard	√	×	√	×
	Viewing full screen monitoring	√	√	√	√
	Querying a dashboard	√	√	√	√
	Deleting a dashboard	√	×	√	×
	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 (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	√	×	√	×
	Querying the alarm rule list	√	√	√	√
	Viewing details of an alarm rule	√	√	√	√
Alarm Records	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	√	√	√ (Cloud services need to support fine-grained authorization.)	√ (Cloud services need to support fine-grained authorization.)
Cloud Service Monitoring	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 Tenant Administrator permission.)	×	√ (You must have the OBS Bucket Viewer permission.)	×
	Exporting monitoring data	√	×	√	×
	Sending an alarm notification	√	×	√	×

Helpful Links

IAM Service Overview
Creating a User and Granting Permissions
For the actions supported by fine-grained policies, see section "Permissions Policies and Supported Actions" in Cloud Eye API Reference.

Parent topic: Product Introduction

Previous topic: Region and AZ

Next topic: Getting Started