Permission Dependency of the CCE Console

Some CCE permissions policies depend on the policies of other cloud services. To view or use other cloud resources on the CCE console, you need to enable the system policy access control feature of IAM and assign dependency policies for the other cloud services.

Dependency policies are assigned based on the CCE FullAccess or CCE ReadOnlyAccess policy you configure. For details, see Cluster Permissions (IAM-based).
Only users and user groups with namespace permissions can gain the view access to resources in clusters of v1.11.7-r2 and later.
- If a user is granted the view access to all namespaces of a cluster, the user can view all namespaced resources (except secrets) in the cluster. To view secrets in the cluster, the user must gain the admin or edit role in all namespaces of the cluster.
- HPA policies take effect only after the cluster-admin permissions are configured for the namespace.
- The view role within a single namespace allows users to view resources only in the specified namespace.

Dependency Policy Configuration

To grant an IAM user the permissions to view or use resources of other cloud services on the CCE console, you must first grant the CCE Administrator, CCE FullAccess, or CCE ReadOnlyAccess policy to the user group to which the user belongs and then grant the dependency policies listed in Table 1 to the user. These dependency policies will allow the IAM user to access resources of other cloud services.

Enterprise projects can group and manage resources across different projects of an enterprise. Resources are thereby isolated. IAM allows you to implement fine-grained authorization. It is strongly recommended that you use IAM for permissions management.

If you use an enterprise project to set permissions for IAM users, the following restrictions apply:

Storage resources are not available to enterprise projects. Therefore, when an enterprise project user queries the storage resources of clusters in an enterprise project other than Default on the CCE console, all buttons on the page are in gray and resources are not displayed.
On the CCE console, enterprise projects cannot call the API used to obtain AOM monitoring data for cluster monitoring. Therefore, IAM users in these enterprise projects cannot query monitoring data.
On the CCE console, enterprise projects cannot call the API to query the key pair created during node creation. Therefore, IAM users in these enterprise projects cannot use the key pair login mode. Only the password login mode is supported.
After assigning the CCE FullAccess permission to an enterprise project, you need to configure the ecs:availabilityZones:list action on the IAM console so that the enterprise project users can create nodes. Otherwise, the system will prompt that they do not have the permission.

CCE supports fine-grained permissions configuration, but has the following restrictions:

AOM does not support resource-level monitoring. After operation permissions on specific resources are configured using IAM's fine-grained cluster resource management function, IAM users can view cluster monitoring information on the Dashboard page of the CCE console, but cannot view the data on non-fine-grained metrics.

**Table 1** Dependency policies
Console Function	Dependent Services	Roles or Policies Required
Dashboard	Application Operations Management (AOM)	An IAM user with CCE Administrator assigned can use this function only after AOM FullAccess policy is assigned. IAM users with IAM ReadOnlyAccess, CCE FullAccess, or CCE ReadOnlyAccess assigned can directly use this function.
Workload management	Elastic Load Balance (ELB) Application Performance Management (APM) Application Operations Management (AOM) NAT Gateway Object Storage Service (OBS) Scalable File Service (SFS)	Except in the following cases, the user does not require any additional role to create workloads. To create a Service using ELB, you must have ELB FullAccess or ELB Administrator plus VPC Administrator assigned. To use a Java probe, you must have AOM FullAccess and APM FullAccess assigned. To create a Service using NAT Gateway, you must have NAT Gateway Administrator assigned. To use OBS, you must have OBS Administrator globally assigned. NOTE: Because of the cache, it takes about 13 minutes for the RBAC policy to take effect after being granted to users, user groups, and enterprise projects. After an OBS-related system policy is granted, it takes about 5 minutes for the policy to take effect. To use SFS, you must have SFS FullAccess assigned.
Cluster management	Application Operations Management (AOM) Billing Center (BSS)	Auto scale-out or scale-up requires the AOM FullAccess policy. Changing the billing mode to yearly/monthly requires the BSS Administrator role.
Node management	Elastic Cloud Server (ECS)	If the permission assigned to an IAM user is CCE Administrator, creating or deleting a node requires the ECS FullAccess or ECS Administrator policy and the VPC Administrator policy.
Network management	Elastic Load Balance (ELB) NAT Gateway	Except in the following cases, the user does not require any additional role to create a Service. To create a Service using ELB, you must have ELB FullAccess or ELB Administrator plus VPC Administrator assigned. To create a Service using NAT Gateway, you must have NAT Administrator assigned.
Storage management	Object Storage Service (OBS) Scalable File Service (SFS)	To use OBS, you must have OBS Administrator globally assigned. NOTE: Because of the cache, it takes about 13 minutes for the RBAC policy to take effect after being granted to users, user groups, and enterprise projects. After an OBS-related system policy is granted, it takes about 5 minutes for the policy to take effect. To use SFS, you must have SFS FullAccess assigned. Using SFS Turbo requires the SFS Turbo Admin role. The CCE Administrator role is required for importing storage devices.
Namespace management	/	/
Chart management	/	IAM users with CCE Administrator assigned can use this function.
Add-on management	/	IAM users with CCE Administrator, CCE FullAccess, or CCE ReadOnlyAccess assigned can use this function.
Permissions management	/	IAM users with CCE Administrator or global Security Administrator assigned can use this function. IAM users with IAM ReadOnlyAccess plus CCE FullAccess or CCE ReadOnlyAccess assigned can use this function.
Configuration center	/	Creating ConfigMaps does not require any additional policy. Viewing secrets requires that the cluster-admin, admin, or edit permission be configured for the namespace. The DEW KeypairFullAccess or DEW KeypairReadOnlyAccess policy must be assigned for dependent services.
Help center	/	/
Switching to other related services	Software Repository for Container (SWR) Application Operations Management (AOM) Cloud Eye (for viewing metrics of nodes and storage systems)	The CCE console provides links to other related services. To view or use these services, an IAM user must be assigned required permissions for the services.

Example

This example describes how to authorize the user James to view monitoring information on the Dashboard page of the CCE console.

Assume that the IAM user James belongs to the user group Developers and Developers is already granted the CCE Administrator role. According to Table 1, to view monitoring information on the Dashboard page of the CCE console, the AOM FullAccess policy is additionally required.

Figure 1 Process for granting dependency policies

Step 1: Verify User's Current Permissions

Log in to the CCE console as the IAM user James.
In the navigation pane, click Dashboard. The monitoring information on the Dashboard page is not available to the user James.

Figure 2 Viewing monitoring information (no data available)

Step 2: Grant Permissions to the User Group

Log out as IAM user James and log in to the CCE console using your account.
In the navigation pane, choose Permissions Management. Click the Cluster-Level Permissions tab. In the same row as the user group Developers to which the IAM user James belongs, click Configure Policy.

Figure 3 Granting permissions to a user group
In the Configure Policy dialog box, click Configure Now.

Figure 4 Configuring a permissions policy
In the navigation pane of the IAM console, choose User Groups. In the user group list, click the user group name Developers to show user group details. On the Permissions tab page, click Assign Permissions.

Figure 5 Granting permissions to a user group
On the page displayed, select the application scope. In this case, select Region-specific projects and then one or more projects in the drop-down list.

Figure 6 Selecting a project type for authorization
Search for AOM in the search box above the permissions list, select the AOM FullAccess policy, and click OK.

Figure 7 Adding an AOM FullAccess policy
Verify that the AOM FullAccess policy is displayed on the Permissions tab page.

Figure 8 Verifying whether a permissions policy is successfully added
In the navigation pane of the CCE console, choose Permissions Management. Click the Cluster-Level Permissions tab. In the upper right corner of the page, click the icon to refresh the page. The AOM FullAccess policy is displayed in the policy list.

Figure 9 Success in adding a policy

Step 3: Verify User's New Permissions

Log in to the CCE console as the IAM user James.
In the navigation pane, choose Dashboard. The monitoring information on the Dashboard page is now available to James.

Figure 10 Monitoring information on the Dashboard page
Verify that the Dashboard page also displays information about dependent services to James.