Step 3: Configure Advanced Settings

Advanced Settings

Set ECS Name.
The name can be customized but 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 a 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 numbering of the new ECS names continues from the highest existing value. For example, if the ECS with the highest 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 over again from 0001.

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

The name of a Windows ECS can contain a maximum of 15 characters and must be unique. Otherwise, some Windows applications cannot be used.

The ECS Name set in this step will be the initial host name in the ECS OS.
The naming rules of hostnames comply with RFC 952 and RFC 1123.

When you set the ECS name and hostname, you are advised to use letters (a-z), digits (0-9), and hyphens (-) to prevent unknown issues. In the ECS:
- Underscores (_) will be converted to hyphens (-).
- A combination of a hyphen and underscore (-_) will be converted to a hyphen (-).
- Periods (.), hyphens (-), Chinese characters, or underscores (_) at the beginning of the name will be ignored.
- If periods (.) and Chinese characters are not at the beginning, they and the content following them will be ignored.

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
Password	Consists of 8 to 26 characters. Contains at least three of the following character types: Uppercase letters Lowercase letters Digits Special characters for Windows: $!@%-_=+[]:./,? Special characters for Linux: !@%-_=+[]:./^,{}? Cannot contain the username or the username spelled backwards. Cannot contain more than two consecutive characters in the same sequence as they appear in the username. (This requirement applies only to Windows ECSs.) Cannot start with a slash (/) for Windows ECSs.

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

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.

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.

For CBR pricing details, see How Is CBR Billed?

The following options are provided:
- 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.
- 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 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.
Configure Cloud Eye.
If you select certain public images, it is a good practice to enable detailed monitoring to collect OS metrics. These metrics help you understand the resource utilization and locate a fault.

After you enable detailed monitoring, an agent will be automatically installed on the ECS to provide 1-minute fine-grained monitoring of ECS metrics, such as CPU, memory, network, disk, and process.

For details about the monitoring metrics after the agent is installed, see OS Monitoring Metrics Supported by ECSs with the Agent Installed.
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.
To use functions listed in Advanced Options, select Configure now. Otherwise, do not select it.
- User Data
  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.
  - As text: allows you to enter the user data in the text box.
  - As file: enables the text to automatically inject a script file or other files into a specified directory on an ECS when you create the ECS.
  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
  This configuration is optional. You can tag an ECS to facilitate identification and management. 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.
  
  If your organization has created a tag policy for ECS, you need to add tags for ECS based on the tag policy. If a tag does not comply with the tag rules, the creation may fail. Contact the organization administrator to learn details about the tag policy.
  
  After creating the ECS, you can view the tags on the pages providing details about the ECS, EIP, and EVS disks.
  
  For details, see Tag Management.
- 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 agencies, see Account Delegation.
Click Next: Confirm.