All Products
Search
Document Center

Platform For AI:Download and authenticate the client

Last Updated:Mar 10, 2026

Learn how to download and authenticate EASCMD client for managing Elastic Algorithm Service (EAS) services.

Procedure

  1. Download the EASCMD client.

  2. Optional: Make the downloaded client file executable by running the following command. Skip this step for 64-bit Windows.

    chmod +x <eascmd64>

    Replace <eascmd64> with the downloaded client filename.

  3. Authenticate with the AccessKey pair of your Alibaba Cloud account.

    Authentication command varies by client version:

    • For 64-bit Windows, run the following command in the client file directory.

      eascmdwin64.exe config -i <yourAccessKeyID> -k <yourAccessKeySecret> [-e Endpoint]
    • For other versions, run the following command in the client file directory.

      ./<eascmd64> config -i <yourAccessKeyID> -k <yourAccessKeySecret> [-e Endpoint]

    Replace parameters as needed.

    Parameter

    Description

    <eascmd64>

    Downloaded client filename.

    <yourAccessKeyID>

    AccessKey ID of your Alibaba Cloud account.

    <yourAccessKeySecret>

    AccessKey secret of your Alibaba Cloud account.

    Endpoint

    Default region for EAS services is China (Shanghai). To deploy a model to another region, use the -e parameter to specify that region's endpoint. For endpoint listings, see Service endpoints. For example, if the client file is named eascmd64, use the following command to specify China (Beijing) region.

    ./eascmd64 config -i <yourAccessKeyID> -k <yourAccessKeySecret> -e pai-eas.cn-beijing.aliyuncs.com
  4. Upon successful authentication, the system returns output similar to:

    # Save path varies by operating system.
    Configuration saved to: /Users/test/.eas/config

References

  • After downloading and authenticating the client, use commands to create or manage services. For more information, see Command reference.

  • Alternatively, use the console to create or manage services. For more information, see Custom deployment.