E-MapReduce clusters support execution plan authentication. You can authorize subaccounts to access execution plans using the master account.

Master account access

After logging on to E-MapReduce console with the master account, you can run the corresponding execution plan on the Execution plan page. Submit the jobs to the security cluster for execution and access the related open source component services involved in the jobs using the hadoop username.

Subaccount access

After logging on to E-MapReduce console with the RAM subaccount, you can run the corresponding execution plan on the Execution plan page. Submit the jobs to the security cluster for execution and access the related open source component services involved in the jobs using the corresponding username of the RAM subaccount.

Examples

  • The master account administrator can create multiple subaccounts (such as A, B, and C) as needed and grant the Aliyun EMR Full Access permissions to these subaccounts from the RAM console. Then, the subaccounts can log on to the E-MapReduce console and use the related functions.
  • The master account administrator may provide the subaccounts to developers.
  • After job creation and plan execution, developers may start executing the execution plans to submit jobs to the cluster, and then access the relevant component services in the cluster using usernames (such as A, B, and C) corresponding to their subaccounts.
    Note Currently, the periodic execution plans are uniformly executed using the hadoop account.
  • Relevant permission control for component services, for example, whether Account A has the permission to access a file in hdfs or not, is performed by using the username of a subaccount.