Advanced Settings

1. Set ECS Name.

   The name can be customized but must comply with the following naming rules: Can contain only letters, digits, underscores (_), hyphens (-), and periods (.).

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

   If multiple ECSs are created at the same time, the system automatically adds a hyphen followed by a four-digit incremental number to the end of each ECS name. For example, if you enter ecs, the ECSs will be named ecs-0001, ecs-0002, .... If you create multiple ECSs again, the values in the new ECS names increase from the existing maximum value. For example, the existing ECS with the maximum number in name is ecs-0010. If you enter ecs, the names of the new ECSs will be ecs-0011, ecs-0012, .... When the value reaches 9999, it will start from 0001.

   Allow duplicate ECS name: allows ECS names to be duplicate. If you select Allow duplicate ECS name and create multiple ECSs in a batch, the created ECSs will have the same name.

2. Set Login Mode.
   Key pair authentication is more secure than password authentication. If you select Password, ensure that the password meets complexity requirements listed in Table 1 to prevent malicious attacks.

   • Key pair

     A key pair is used for ECS 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.

   • Password

     A username and its initial password are used for ECS login authentication.

     The initial password of user root is used for authenticating Linux ECSs, while that of user Administrator is used for authenticating Windows ECSs.

     The passwords must meet the requirements described in Table 1.

     Table 1 Password complexity requirements

     Parameter	Requirement	Example Value
     Password	Consists of 8 characters to 26 characters. Contains at least three of the following character types: Uppercase letters Lowercase letters Digits Special characters: $!@%-_=+[]:./^,{}? Cannot contain the username or the username spelled backwards. Cannot contain more than two characters in the same sequence as they appear in the username. (This requirement applies only to Windows ECSs.)	YNbUwp!dUc9MClnv NOTE: The example password is generated randomly. Do not copy this example password.

     

     The system does not periodically change the ECS password. It is recommended that you change your password regularly for security.

   • Image password

     If you use a private image to create an ECS, you can use the image password for login authentication. Make sure that a password has been set for the selected private image.

   • Set password later

     The password for logging in to the ECS is not configured during the ECS creation. After the ECS is created, select Reset Password in the Operation column, set a password for the ECS as prompted, and log in to the ECS.

3. 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

   • Auto assign
     1. Set the name of the cloud backup vault, which is a character string consisting of 1 to 64 characters, including letters, digits, underscores (_), and hyphens (-). The name is in the format of "vault_xxxx" by default, for example, vault-f61e.
     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.
   • Use existing
     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.
   • Not required

     Skip this configuration if CBR is not required. If you require this function after purchasing the ECS, log in to the CBR console and bind the desired cloud backup vault to your ECS.

4. Configure host monitoring.

   If you select certain public images, you are advised to use the host monitoring function provided by the public cloud. Host monitoring collects ECS OS metrics, such as CPU usage, memory usage, and network status, so that you can use these metrics to monitor resource utilization or locate a fault.

   Enable Detailed Monitoring. After you enable this function, the system will automatically install an agent on the ECS to provide 1-minute detailed monitoring for your ECS.

   For details about the monitoring metrics after the agent is installed, see OS Monitoring Metrics Supported by ECSs with the Agent Installed.

5. Set ECS Group.

   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.
   • File Injection

     Enables the ECS to automatically inject a script file or other files into a specified directory on an ECS when you create the ECS. This configuration is optional.

     For example, if you activate user root permission using script file injection, you can log in to the ECS as user root.

     For details about file injection, see Injecting Files into ECSs.

   • User Data Injection

     Enables the ECS to automatically inject user data when the ECS starts for the first time. This configuration is optional.

     For example, if you activate user root permission using script file injection, you can log in to the ECS as user root.

     For detailed operations, see Injecting User Data into ECSs.

   • Tag

     Tags an ECS, facilitating ECS identification and management. This configuration is optional. You can add up to 10 tags to an ECS.

     For detailed operations, see Tags.

   • 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 more information about agency, see Account Agencies.

7. Click Next: Confirm.