Configuring Fine-Grained Permissions for MRS Multi-User Access to OBS

Prerequisites

• Fine-grained permission control has been enabled. For details about permissions management, see Creating an MRS User.
• You have a basic knowledge of and OBS fine-grained policies.

Step 1: Configuring an Agency with OBS Access Permission for a Cluster

1. Follow instructions in Configuring a Storage-Compute Decoupled Cluster (Agency) to configure an agency with OBS access permissions.

   The agency takes effect for all users (including internal users) and user groups in the cluster. To control the permissions of users and user groups in the cluster to access OBS, perform the following operations.

Step 2: Creating a Policy and an Agency on IAM

Create policies with different access permissions and bind the policies to the agency. For details, see Creating a Policy and an Agency on IAM.

Step 3: Configuring OBS Permission Control Mappings on the MRS Cluster Details Page

1. On the MRS management console, choose Clusters > Active Clusters and click the cluster name.
2. In the Basic Information area on the Dashboard tab page, click Manage next to OBS Permission Control.
3. Click Add Mapping and set parameters according to Table 1.

   Table 1 OBS permission control parameters

   Parameter	Description
   IAM Agency	Select the agency created in 2.
   Type	User: User-level mapping Group: User group-level mapping NOTE: User-level mapping takes priority over user group-level mapping. If you select Group, you are advised to enter the primary group name in MRS User (User Group). Do not use the same username (user group) for multiple mapping records.
   MRS User (User Group)	Use commas (,) to separate multiple names of users or user groups. NOTE: If OBS permission control is not configured for a user and no AK and SK are configured, the permission in MRS_ECS_DEFAULT_AGENCY will be used for accessing OBS. You are advised not to bind the internal user of a component to an agency. If you need to configure an agency for the internal user of a component when submitting a job in the following scenarios, the requirements are as follows: To control permissions on spark-beeline operations, set the username to spark for a security cluster and omm for a normal cluster. To control permissions on HBase shell operations, set the username to hbase for a security cluster and omm for a normal cluster. To control permissions on Presto, set the username to omm, hive, and the username used for logging in to the client for a security cluster and omm and the username used for logging in to the client for a normal cluster. If you want to use Hive to create tables in beeline mode, set the username to the internal user hive.

4. Click OK.
5. Select I agree to authorize the trust relationships between MRS Users (Groups) and IAM agencies, and click OK. The mapping between the MRS user and OBS permission is added.

   If appears next to OBS Permission Control on the Dashboard tab page or the mapping table has been updated for OBS permission control, the mapping takes effect. It takes about 1 minute to for the mapping to take effect.

   In the Operation column of the mapping list, you can edit or delete the added mapping.

   

   • If OBS permission control is not configured for a user and no AK and SK are configured, the permissions owned by the agency configured for the cluster in the Object Storage Service (OBS) project will be used to access OBS.
   • Regardless of whether OBS permission control is configured, AK/SK permission is used for accessing OBS once it is configured.
   • Security Administrator permission is required to modify, create, or delete a mapping.
   • To enable mapping changes to take effect in spark-line, hive beeline and Presto respectively, you need to restart Spark, exit beeline and enter again, and restart Presto respectively.

Component Access to OBS When OBS Permission Control Is Enabled

1. Log in to any node in a cluster as user root using the password set during cluster creation.
2. Set environment variables (In MRS 3.x and later versions, the default installation path of the client is /opt/Bigdata/client. In MRS 3.x and earlier versions, the default installation path is /opt/client. For details, see the actual situation.).

   source /opt/Bigdata/client/bigdata_env

3. If the Kerberos authentication is enabled for the current cluster, run the following command to authenticate the user. If the Kerberos authentication is disabled for the current cluster, skip this step:

   kinit MRS cluster user

   Example: kinit admin

4. If the Kerberos authentication is disabled for the current cluster, run the following commands to log in. Note that you should create a user that belongs to the supergroup group by referring to Creating a User and replace XXXX with the username:

   mkdir /home/XXXX

   chown XXXX /home/XXXX

   su - XXXX

5. Access OBS. You do not need to configure the AK, SK, and endpoint. The OBS path format is obs://buck_name/XXX.

   Example: hadoop fs -ls "obs://obs-example/job/hadoop-mapreduce-examples-3.1.2.jar"

   

   • If you want to use hadoop fs to delete files on OBS, use hadoop fs -rm -skipTrash to delete the files.
   • If data import is not involved when a table is created using spark-sql and spark-beeline, OBS will not be accessed. That is, if you create a table in an OBS directory on which you do not have permission, the CREATE TABLE operation will still be successful, but the error message "403 AccessDeniedException" is displayed when you insert data.

Creating a Policy and an Agency on IAM

1. Create a policy on IAM.
   1. Log in to the IAM console.
   2. Choose Permissions. On the displayed page, click Create Custom Policy.
   3. Set parameters according to Table 2. Obtain the customized OBS policy samples that are frequently used by referring to .

      Table 2 Policy parameters

      Parameter	Description
      Policy Name	Only letters, digits, spaces, and special characters (-_.,) are allowed.
      Scope	Select Global services, because OBS is a global service.
      Policy View	Select Visual editor.
      Policy Content	Allow: Select Allow. Select service: Select Object Storage Service (OBS). Select action: Select WriteOnly, ReadOnly, and ListOnly. Specific resources: Set object to Specify resource path, click Add Resource Path, and enter obs_bucket_name/tmp/ and obs_bucket_name/tmp/*. The /tmp directory is used as an example. If you need to add permissions for other directories, perform the following steps to add the directories and resource paths of all objects in the directories. Set bucket to Specify resource path, click Add Resource Path, and enter obs_bucket_name. (Optional) Add request condition, which does not need to be added currently.
      Description	(Optional) Brief description about the policy.

      

      If the data write operation of each component is implemented in rename mode, the permission to delete objects must be configured when data is written.

   4. Click OK to save the policy.

2. Create an agency on IAM.
   1. Log in to the IAM console.
   2. Choose Agencies. On the displayed page, click Create Agency.
   3. Set parameters according to Table 3.

      Table 3 Agency parameters

      Parameter	Description
      Agency Name	Only letters, digits, spaces, and special characters (-_.,) are allowed.
      Agency Type	Select Common account.
      Delegated Account	Enter your cloud account, that is, the account you register using your mobile phone number. It cannot be a federated user or an IAM user created using your cloud account.
      Validity Period	Set this parameter as required.
      Description	(Optional) Brief description about the agency.
      Permissions	In the Project [Region] column, locate the row where OBS is, click Attach Policy. Select the policy created in 1 to display it in Selected Policies. Click OK.

   4. Click OK to save the agency.
      

      If you modify an agency and policies bound to it after using the agency to access OBS, the modification will take effect within 15 minutes.