Step 1: Configure Basic Settings

The page for creating ECSs is displayed.

If the region is incorrect, click in the upper left corner of the page to select your region.

An AZ is a physical location that uses independent power supply and networks. AZs in the same region can communicate with each other over an intranet.

• To enhance application availability, create ECSs in different AZs.
• To shorten network latency, create ECSs in the same AZ.

During the creation process, you can select a random AZ. The system will use a hash algorithm to select an AZ as the default AZ based on your universally unique identifier (UUID).

The available ECS types and flavors vary depending on AZs. To view all supported ECS types and flavors on the cloud service platform, set AZ to Random. Then, the system automatically allocates an AZ according to your selected ECS flavor.

For example, P2s ECSs are released only in AZ1; P3 ECSs are available in AZ2 and have been sold out in AZ1. If you set AZ to Random, you can view both P2s and P3 ECSs. If you create a P2s ECS, the system automatically allocates it to AZ1. If you create a P3 ECS, the system allocates it to AZ2.

• By Type: Select a CPU architecture, ECS type, flavor, vCPUs, and memory to suit your service needs.
• By Scenario: Select a category and sub-category of your services and then choose appropriate specifications from the displayed specifications list.

This configuration is displayed when you select By Type for Instance Selection.

• x86

  The x86 CPU architecture uses Complex Instruction Set Computing (CISC). Each instruction can be used to execute low-level hardware operations. There are a large number of instructions and the length of each instruction is different. Therefore, executing such an instruction is complex and time-consuming.

The cloud platform provides various ECS types for different application scenarios. You can choose from existing ECS types and flavors in the list. Alternatively, you can enter a flavor or specify vCPUs and memory size to search for the flavor suited to your needs.

Latest generation shows the types and flavors of newly released ECSs, and All generations show the types and flavors of all ECSs provided by the cloud platform.

• Before selecting an ECS type, learn about the introduction and notes on each type of ECSs. For details, see ECS Types.
• When purchasing an ECS, sold-out vCPU and memory resources cannot be selected. You can select Hide sold-out specifications to hide specifications that have been sold out.
• Local Disk: specifies the local storage of the physical server where the ECS is deployed. Only Hard Disk Driver (HDD) disks are supported. If the ECS of the selected type (such as Disk-intensive) uses local disks, the system automatically attaches the local disks to the ECS and displays the information of the local disks.

  For example, if Local Disk is 3x1800 GiB (HDD), three HDDs are attached to the ECS and the capacity of each HDD is 1800 GiB.

• Public image

  A public image is a standard, widely used image. It contains an OS and preinstalled public applications and is available to all users. You can configure the runtime environment or software in the public image as needed.

• Private image

  A private image is an image available only to the user who created it. It contains an OS, preinstalled public applications, and the user's private applications. Using a customized private image, you can create ECSs tailored to your needs in batches.

  For instructions about how to create a private image, see Creating a Private Image.

  You can also select an encrypted image. For more information about encrypted images, see Image Management Service User Guide.

  

  • If you use a full-ECS image to create an ECS, the EVS disks associated with the full-ECS image do not support the function of creating disks using a data disk image.
  • If a full-ECS image is in Normal state and the system displays message "Available in AZx", the full-ECS image can be used to create ECSs in this AZ only, and the encryption attributes of the system and data disks of the created ECSs are the same as those of the system and data disks specified in the full-ECS image. Additionally, the SCSI, data encryption, and sharing attribute settings of the system and data disks cannot be modified during ECS creation.
  • If a full-ECS image is in Normal state but the system does not display message "Available in AZx", the full-ECS image can be used to create ECSs in the entire region, and the encryption attributes of the system and data disks of the created ECSs are the same as those of the system and data disks specified in the full-ECS image. Additionally, the SCSI, data encryption, and sharing attribute settings of data disks can be modified during ECS creation.
  • An ISO image created from an ISO file cannot be used to create ECSs. You need to install an OS and drivers on the ECS and use the ECS to create a system disk image first.
  • ECSs created from ISO images cannot be directly used because some functions like disk attachment are restricted.
  • To ensure that NIC multi-queue is enabled on an ECS created using a private image, configure NIC multi-queue when creating such a private image. NIC multi-queue routes NIC interrupt requests among multiple vCPUs for higher network packets per second (PPS) and bandwidth.

    For details, see How Do I Enable NIC Multi-Queue for an Image?

• Shared image

  A shared image is a private image shared by another user.

• System disk

  For details about the disk types supported by ECS, see EVS Disks.

  • If the image based on which an ECS is created is not encrypted, the system disk of the ECS is not encrypted. If the image based on which an ECS is created is encrypted, the system disk of the ECS is automatically encrypted. For details, see (Optional) Encryption-related parameters.
  • Encryption: indicates that the system disk is encrypted if you select this option. For details, see (Optional) Encryption-related parameters.
• Data disk

  You can create multiple data disks for an ECS and enable required functions for each data disk. During the creation process, you can add a maximum of 23 data disks for each ECS and customize the disk size as needed.

  Click Show and set the following functions if required:

  • SCSI: indicates that the device type of the data disk is SCSI if you select this option. For more information about SCSI disks and the ECSs that can be attached with SCSI disks, see EVS Disks.
  • Share: indicates that the EVS disk is sharable if you select this option. Such an EVS disk can be attached to multiple ECSs.
  • Encryption: indicates that the data disk is encrypted if you select this option. For details, see (Optional) Encryption-related parameters.
• (Optional) Encryption-related parameters

  To enable encryption, click Create Agency to assign KMS access permissions to EVS. If you have rights granting permission, assign the KMS access permissions to EVS. If you do not have the permission, contact the user having the security administrator rights to assign the KMS access permissions. For details, see Can All Users Use the Encryption Feature?

  • Encryption: indicates that the EVS disk has been encrypted.
  • Create Agency: assigns KMS access permissions to EVS to obtain KMS keys. After the permissions are assigned, follow-up operations do not require assigning permissions again.
  • Agency Name: set to EVSAccessKMS, which means that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
  • KMS Key Name: specifies the name of the key used by the encrypted EVS disk. You can select an existing key, or click Create KMS Key and create a new one on the KMS console. The default value is evs/default.
  • KMS Key ID: specifies the ID of the key used by the encrypted data disk.