Step 3: Configure Advanced Settings

Advanced Settings

  1. Set ECS Name.

    The name can be customized but can contain only letters, digits, underscores (_), hyphens (-), and periods (.).

    If you want to create multiple ECSs at a time, the system automatically sequences these ECSs.

    The ECS Name set in this step will be the initial host name in the ECS OS.


    Consecutive periods (.) or hyphens (-) will be replaced with the first character to prevent unknown issues.

  2. (Optional) Specify the description of the ECS.

  3. Set Login Mode.

    Key pair: allows you to use a key pair for login authentication. You can select an existing key pair, or click Create Key Pair and create a desired one.


    If you use an existing key pair, make sure that you have saved the key file locally. Otherwise, logging in to the ECS will fail.

  4. Set Cloud Backup and Recovery.

    Cloud Backup and Recovery (CBR) provides backup protection for EVS disks and ECSs, and uses backups to restore the EVS disks and ECSs. After you set Cloud Backup and Recovery, the system binds the target ECS to the cloud backup vault and associates the ECS with the selected backup policy to periodically back up the ECS.

    The following options are provided, among which the default value is Do not use:

    • Create new

      1. Set the name of the cloud backup vault, which consists of 1 to 64 characters, containing only letters, digits, underscores (_), and hyphens (-). For example, vault-f61e. The default naming rule is vault_xxxx.

      2. Enter the vault capacity, which is required for backing up the ECS. The vault capacity cannot be smaller than that of the ECS to be backed up. Its value ranges from the total capacity of the ECS to 10,485,760 in the unit of GB.

      3. Select a backup policy from the drop-down list, or log in to the CBR console and configure a desired one.

    • Specify

      1. Select an existing cloud backup vault from the drop-down list.

      2. Select a backup policy from the drop-down list, or log in to the CBR console and configure a desired one.

    • Do not use

      Skip this configuration if CBR is not required. If you need to enable CBR after creating an ECS, log in to the CBR console, locate the target vault, and bind the ECS to the vault.

  5. Set ECS Group (Optional).

    An ECS group applies the anti-affinity policy to the ECSs in it so that the ECSs are automatically allocated to different hosts. This configuration is optional. For instructions about how to create an ECS group, see Managing ECS Groups.


    An existing ECS attached with a local disk cannot be added to an ECS group. To use ECS group functions, select an ECS group when creating an ECS.

  6. To use functions listed in Advanced Options, select Configure now. Otherwise, do not select it.

    • User Data Injection

      You can specify the user data. The user data will be automatically passed to the ECS when the ECS starts for the first time. This configuration is optional.

      For example, if you activate user root permission by passing a script file to an ECS, you can log in to the ECS as user root.

      For detailed operations, see Passing User Data to ECSs.

    • Tag

      Tagging an ECS to facilitate ECS identification and management. This configuration is optional. You can add up to 10 tags to an ECS.


      Tags added during ECS creation will also be added to the created EIP and EVS disks (including the system disk and data disks) of the ECS. If the ECS uses an existing EIP, the tags will not be added to the EIP.

      After creating the ECS, you can view the tags on the pages providing details about the ECS, EIP, and EVS disks.

      For details, see Overview.

    • Agency

      This configuration is optional. When your ECS resources need to be shared with other accounts, or your ECS is delegated to professional personnel or team for management, the tenant administrator creates an agency in IAM and grants the ECS management permissions to the personnel or team. The delegated account can log in to the cloud system and switch to your account to manage resources. You do not need to share security credentials (such as passwords) with other accounts, ensuring the security of your account.

      If you have created an agency in IAM, you can select the agency from the drop-down list and obtain specified operation permissions. For instructions about how to create an agency, see Identity and Access Management User Guide.

  7. Click Next: Confirm.