tencent cloud


COS Ranger Permission System Solution

Terakhir diperbarui:2022-08-04 15:09:53


    Hadoop Ranger is a permission solution for big data scenarios. A user adopting the compute/storage separation mode can host data in COS. However, COS uses the CAM permission system, meaning that the user roles and permission policies could be different from those of Hadoop Ranger. Therefore, we introduce a solution to integrate COS with Ranger herein.


    • Fine-grained and Hadoop-compatible permission control, allowing users to centrally manage permissions for big data components and data hosted in cloud.
    • No need to set keys in core-site on the plugin side. Instead, keys are centrally set in COS Ranger Service to avoid key plaintext exposure.

    Solution Architecture

    In the Hadoop permission system, the authentication is offered by Kerberos and authorized by Ranger. On the basis of this, the following components are introduced to support the COS Ranger permission solution:

    1. COS Ranger Plugin: A service define plugin used on the Ranger server. It provides the COS service description, including permission types and definitions of required parameters (such as bucket and region), on the Ranger side. Once the plugin is deployed, users can set permission policies on the Ranger control panel.
    2. COS Ranger Service: Integrates the Ranger client to periodically sync permission policies from the Ranger server, and verifies permissions locally when an authentication request is received. It also offers generation/lease renewal APIs relevant to DelegationToken of Hadoop. All APIs are defined through Hadoop IPC.
    3. COS Ranger Client: COSN dynamically loads it and forwards the permission verification requests to COS Ranger Service.

    Environment Deployment

    • Hadoop environment
    • ZooKeeper, Ranger, and Kerberos (if there are authentication requirements)

      As the above services are mature open-source components, you can install them on your own.

    Component Deployment

    Deploy components in the following sequence: CHDFS Ranger Plugin, COS Ranger Service, COS Ranger Client, and COSN.

    COS Ranger Plugin extends the service types of the Ranger Admin console. Users can configure the COS-related permissions in the Ranger console.

    Source code download

    You can go to GitHub > ranger-plugin to obtain the source code.


    v1.1 or later

    Deployment directions

    1. Create a COS directory in the service definition directory in Ranger. Note that you should at least have execute and read permissions on the directory.
      a. In the Tencent Cloud EMR environment, the path is ranger/ews/webapp/WEB-INF/classes/ranger-plugins.
      b. In the self-built Hadoop environment, you can search the path of the Ranger-integrated components (such as HDFS) to find the path.
    2. Place cos-chdfs-ranger-plugin-xxx.jar (with at least the r permission) and cos-ranger.json files in the COS root directory. You can get them from GitHub.
    3. Restart Ranger.
    4. Register COS service in Ranger. A command sample is as follows:
      ## Create the service. The Ranger admin account and password, as well as the Ranger service address should be specified.
      ## For an EMR cluster, the admin user is root, and the password is the root password set when the EMR cluster is created. Replace the IP of the Ranger service with the master node IP of EMR.
      ## Password set during EMR cluster creation, which is also the login password of the Ranger web service.
      ## If the Ranger service has multiple master nodes, select any of them.
      ## Specify the .json file in step 2 as -d in the command.
      curl -v -u${adminUser}:${adminPasswd} -X POST -H "Accept:application/json" -H "Content-Type:application/json" -d @./cos-ranger.json http://${rangerServerAddr}/service/plugins/definitions
      ## To delete a defined service, for example, the service created above, pass the service ID that is returned when you created the service.
      curl -v -u${adminUser}:${adminPasswd} -X DELETE -H "Accept:application/json" -H "Content-Type:application/json" http://${rangerServerAddr}/service/plugins/definitions/${serviceId}
    5. When the service is created successfully, you can view the COS service in the Ranger console, as shown in the following figure:
    6. Click the + icon on the right of the COS service to define the service instance. On the Edit Service page, customize the Service Name, for example, cos or cos_test, as shown below:

      Where, policy.grantrevoke.auth.users needs to be set to the name of the user that is used to launch COS Ranger Service (i.e., the user that is allowed to pull permission policies). We recommend you set it to hadoop, which can be used as the username to launch COS Ranger Service in subsequent operations.
    7. Click the newly created COS service instance.

      Add a policy as shown below:
    8. On the page that is displayed, configure the following parameters:
    • Bucket: Bucket name, for example, examplebucket-1250000000. It can be queried in the COS console.
    • Path: Path of the COS object. Note that it does not start with a slash (/).
      • include: Indicates whether the permission applies to the specified path, or other paths except for the specified path.
      • recursive: Indicates the permission applies to the specified path as well as the subpaths (i.e., the recursive subpaths) under it. It is usually used when the path is set to a directory.
    • Select Group/Select User: Username and user group in logical OR relationship; that is, the operation is authorized as long as the username or user group condition is met.
    • Permissions:
      • Read: Permission on operations such as downloading objects and querying the object metadata. It corresponds to the GET and HEAD operations in COS.
      • Write: Permissions on operations such as uploading objects. It corresponds to the PUT operation in COS.
      • Delete: Delete permission. It corresponds to the delete object operation in COS. To rename a path in Hadoop, you need to have delete permission on the original path and write permission on the new path.
      • List: Traverse permission. It corresponds to the List Object operation in COS.


    1. Use Hadoop commands to perform operations related to COSN access, i.e., check whether the current operations comply with the permissions set by the root account.

      # Replace the bucket, path, and other information with that of the root account.
      hadoop fs -ls cosn://examplebucket-1250000000/doc
      hadoop fs -put ./xxx.txt cosn://examplebucket-1250000000/doc/
      hadoop fs -get cosn://examplebucket-1250000000/doc/exampleobject.txt
      hadoop fs -rm cosn://examplebucket-1250000000/doc/exampleobject.txt
    2. Use MR Job for verification. Before the verification, related services, such as Yarn and Hive, should be restarted first.


    Must Kerberos be installed?

    Kerberos meets the authentication needs. If the cluster and users are trusted, and the purpose of the authentication is only to avoid maloperations caused by unauthorized users, you can skip installing Kerberos and only use Ranger for authentication. As a matter of fact, Kerberos also compromises performance. Therefore, you can balance your needs for security and performance. If authentication is needed, you can enable Kerberos, and then configure COS Ranger Service and COS Ranger Client.

    What would happen if I enable Ranger, but haven’t set any policy or no policy is matched?

    If no policy is matched, the operation will be denied by default.

    Can a sub-account configure the key on the COS Ranger Service side?

    Yes. A sub-account with relevant permissions on the operated bucket can generate a temp key for the COSN plugin and operate relevant operations. Normally, you can grant all permissions of the bucket to the configured key.

    How can I update the temp key? Do I need to obtain it from COS Ranger Service every time before I access COS?

    The temp key is cached on the COSN side. It will be periodically updated asynchronously.

    What should I do if the policy modified on the Ranger page doesn't take effect?

    Decrease the ranger.plugin.cos.policy.pollIntervalMs value (in milliseconds) in the ranger-cos-security.xml file and restart COS Ranger Service. After the policy is tested, we recommend you change it back to the original value (if the time interval is too short, the polling frequency will be high, causing a high CPU utilization).

    Hubungi Kami

    Hubungi tim penjualan atau penasihat bisnis kami untuk membantu bisnis Anda.

    Dukungan Teknis

    Buka tiket jika Anda mencari bantuan lebih lanjut. Tiket kami tersedia 7x24.

    Dukungan Telepon 7x24