You need to enable JavaScript to run this app.
E-MapReduce

E-MapReduce

  • Documentation
    • E-MapReduceAPI referenceEMR on ECS API referenceRead before use
Copy page
Download PDF
EMR on ECS API reference
Read before use
Copy page
Download PDF
Read before use

Volcano Engine E-MapReduce (EMR) is an enterprise-level big data analytics system based on the open-source Hadoop ecosystem, fully compatible with open-source components.

1. Note on the invocation process

The EMR OpenAPI invocation process mainly consists of the following steps:

  1. Create a Volcano Engine account: You must complete real-name authentication for your Volcano Engine account. If you have not registered a Volcano Engine account, please register a Volcano Engine account first.
  2. Add API invocation permissions:
    1. The account must enable EMR service permissions.
    2. Log in to Volcano Engine Console >, go to the account information in the upper right corner, enter Access Control > Roles, and add the “ ServiceRoleForEMR ” service role.
  3. Obtain Access_key information for the engine account:
    1. Log in to Volcano Engine Console >, go to the account information in the upper right corner, enter Key Management, and obtain the relevant Access_key information for the account.
      Access Key ID and Secret Access Key are the credentials for accessing OpenAPI, granting full permissions for the account, and no more than two can be created.
      For details, see: Key Management.
  4. Obtain the API endpoint address.

Image

2. Limits

  • Important: The frequency limit for each query-type API is 300 requests per second. If the server returns AccountFlowLimitExceeded or FlowLimitExceeded, it indicates that the rate limit has been triggered. To request a higher QPS, please contact the EMR technical team.
  • The frequency limit for operation-type APIs is 50 requests per second; the rate limit response is the same as above.

3. Note on versions

Version

Note

V1(2022-10-09)

The V1 version API was released in October 2022. This version supports basic features such as cluster management.

V2(2023-12-26)

The V2 version API was released in December 2023. New users are recommended to choose this version for integration.
This version covers all current features of V1 and, except for tag management, also provides cluster management, node group management, application management, operation management, order management, and more.

4. Note on compatibility

To ensure compatibility between new and old versions and avoid affecting the normal use of existing users, the V1 version of OpenAPI will not be discontinued, but iteration will stop and, in principle, no new features will be added. To achieve a better user experience and more comprehensive features, we strongly recommend using the V2 version of OpenAPI.
Compared to V1, the V2 version of OpenAPI adds features such as node group and application management, allows the creation of clusters for all EMR versions, and will continue to be updated.

Last updated: 2026.06.01 17:04:20