Creating an AS Configuration from Scratch

Scenarios

If you have special requirements on the ECS instances for scaling out, use a new specifications template to create the AS configuration. In such a case, ECS instances that have the specifications specified in the template will be added to the AS group in scaling actions.

Procedure

1. Log in to the AS console.
2. Click Create AS Configuration.

   

3. Set parameters for the AS configuration. Table 1 lists the AS configuration parameters.
   Figure 1 Setting AS configuration parameters
   

   

   

   

   Table 1 AS configuration parameters

   Parameter	Description	Example Value
   Billing Mode	Specifies the billing mode of instances whose specifications are defined in the AS configuration. You can select Pay-per-use or Spot pricing. Pay-per-use: a postpaid billing mode, in which an ECS is billed based on the service duration. You can create or delete such an ECS at any time. For more information, see Pay-per-Use Billing. Spot pricing: a postpaid billing mode, in which a spot ECS is billed based on the service duration at a lower price than that of a pay-per-use ECS with the same specifications. Huawei Cloud offers spot ECSs based on market transaction prices or changes in supply and demand. For more information, see Spot Pricing (for Spot Instances).	Pay-per-use
   Region	Select the region where the AS configuration is created. Resources in different regions cannot communicate with each other over an intranet. For low latency and fast access, select a region close to where your services will be provided.	-
   Name	Specifies the AS configuration name. The name consists of 1 to 64 characters, including only letters, digits, underscores (_), and hyphens (-).	-
   Configuration Template	Select Create new template. If this option is selected, configure parameters, such as the vCPUs, memory, image, disk, and ECS type, to create a new AS configuration.	Create new template
   CPU Architecture	Both x86 and Kunpeng CPU architectures are available: x86: The x86-based CPU architecture uses Complex Instruction Set Computing (CISC). Kunpeng: The Kunpeng-based CPU architecture uses Reduced Instruction Set Computing (RISC). NOTE: This parameter is displayed only when both x86-based and Kunpeng-based ECSs are available in the current region.	x86
   DeH	(Optional) Instances automatically created by the AS group will run on a DeH. You can choose to allow the system to select a DeH or specify a DeH. If you select auto placement, the system will automatically assign a DeH to deploy ECSs. If you specify a DeH, the system will automatically create ECSs on the DeH you specify. NOTE: This parameter is available only if you have DeHs.	Auto placement
   Flavors	The public cloud provides various ECS flavors for different application scenarios. For more information, see Elastic Cloud Server User Guide. Configure the ECS parameters, including the vCPU/memory ratio, image type, and disk, based on the ECS type.	c9.2xlarge.4
   Flavor selection policy	This parameter is available only when you select two or more flavors. It defines the flavor priority order which AS will honor during scaling. This parameter is not available when a single flavor is selected. You can select Sequenced or Cost-centered. Sequenced: The flavors are prioritized based on the order in which they are selected. Cost-centered: The flavors are prioritized in the ascending order of their costs. For details about the flavor priority order, see If the AS Configuration of an AS Group Uses Multiple Flavors, in What Order Are the Flavors Selected During Scale-out Actions?	Sequenced
   Image	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. If a public image does not contain the applications or software you need, you can use the public image to create a cloud server and then deploy required software 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 private image to create ECSs frees you from configuring multiple ECSs repeatedly. Shared image A shared image is a private image shared by another public cloud user. KooGallery image A KooGallery image is a third-party image that has the OS, application environment, and software pre-installed. You can use such an image for website setup, application development, and visualized management with just a few clicks. No additional configurations are required. It is suitable for scenarios where specific software stacks need to be quickly deployed.	Public image
   Disk	Includes system and data disks. System Disk Common I/O: uses serial advanced technology attachment (SATA) drives to store data. High I/O: uses serial attached SCSI (SAS) drives to store data. General Purpose SSD: uses general-purpose solid state disk (GPSSD) drives to store data. Extreme SSD: uses enhanced solid state disk (ESSD) drives to store data. Ultra-high I/O: uses solid state disk (SSD) drives to store data. If a full-ECS image is used, the system disk is restored using the disk backup. On the console, you can only change the volume type and size. In addition, the volume cannot be smaller than the disk backup. NOTE: Different ECS flavors support different disk types. The supported disk types will be displayed on the management console. Data Disk You can create multiple data disks for an ECS instance and encrypt them. In addition, you can use a data disk image to export data. (Optional) Set encryption parameters. These parameters are available only when Encryption is selected. The encryption parameters are as follows: Agency Name: specifies the name of the agency that is used to grant EVS the permissions needed to obtain KMS keys for disk encryption and decryption. When Agency Name is displayed as EVSAccessKMS, KMS permissions have been granted to EVS. KMS Encryption: specifies how to obtain a KMS key. Select an existing key: Select a KMS key from the KMS Key Name drop-down list. Enter a key ID: Select a KMS key using the key ID. (Optional) KMS Key Name: specifies the name of the key used to encrypt EVS disks. This parameter is displayed only when KMS Encryption is set to Select an existing key. You can select an existing key, or click Create KMS Key and create a KMS key on the KMS console. The default value is evs/default. KMS Key ID: specifies the ID of the key used to encrypt data disks. If the image you selected is a full-ECS image, you can change the volume type and size and encryption attributes of the data disk restored using the disk backup. Ensure that the disk is at least as big as the disk backup. The encryption attributes can only be modified if the disk backup is in the same region as the disk.	-
   Security Group	Controls ECS access within or between security groups by defining access rules. ECSs added to a security group are protected by the access rules you define. For details about how to configure a security group, see Security Group Examples.	-
   EIP	An EIP is a static public IP address bound to an ECS in a VPC. Using the EIP, the ECS provides services externally. The following options are provided: Do not use: An ECS without an EIP cannot access the Internet. However, it can still be used as a service ECS or deployed in a cluster on a private network. Automatically assign: An EIP with a dedicated bandwidth is automatically assigned to each ECS. You can set the bandwidth size. NOTE: If you select Automatically assign, specify EIP Type, Billed By, and Bandwidth. The billing items vary depending on the EIP billing mode. For details, see EIP Billing Overview.	Automatically assign
   Bandwidth	Specifies the bandwidth size in Mbit/s. NOTE: This parameter is available only when EIP is set to Automatically assign. If you select Dedicated, you can select Bandwidth or Traffic for Billed By. Shared bandwidths can be billed only by bandwidth. You can select a shared bandwidth to which the EIP is to be added.	100
   Login Mode	An ECS can be authorized using a key pair or a password. Key pair A key pair is used for ECS login authentication. If you select this mode, create or import a key pair first. For details about how to create a key pair, see Creating a Key Pair on the Management Console. NOTE: If you use an existing key pair, make sure that you have saved the key file locally. Without the key, you will not be able to log in to your ECS. Password The initial password of user root (for Linux) or user Administrator (for Windows) is used for authentication. You can log in to an ECS instance using a username and password combination.	Admin@123
   Advanced Settings	This allows you to configure ECS Group and User Data. You can select Do not configure or Configure now.	-
   User Data	Injects user data automatically into an ECS when the ECS starts for the first time. This configuration is optional. If this function is enabled, user data will be automatically injected into an ECS upon its first startup. For details, see Elastic Cloud Server User Guide. The following methods are available: As text: allows you to enter the user data in the text box below. As file: allows you to inject script files or other files when you create an ECS. NOTE: For Linux, if you use password authentication, this function is not supported. If the selected image does not support user data injection, this function is not supported.	-
   ECS Group	An ECS group allows you to create ECSs on different hosts to improve service reliability. For details about how to create ECS groups, see Managing ECS Groups.	-

4. Click Create Now.

   The system displays a message indicating that the AS configuration is successfully created. Go back to the AS configuration page to view the created AS configuration.

Notes on Multiple Flavors in an AS Configuration

AS configuration supports multiple flavors to minimize the probability of capacity expansion failures due to insufficient or unavailable flavors and ensure that capacity expansion succeeds during peak hours.

A maximum of 10 flavors can be selected for an AS configuration.

Applicable Scenario

• No special requirement for the instance flavors created in the AS group
• Requiring higher success ratio and low latency of creating instances in an AS group
• Requiring instances with high specifications
• Services that are stateless and can be horizontally scaled

The AS group sorts multiple flavors in either of the following ways:

• Sequenced: During AS group expansion, flavors are used based on the sequence they are selected. When the first flavor is insufficient or the instance fails to be created due to other reasons, the system attempts to create an instance of the second flavor, and so on.
• Cost-centered: During AS group expansion, the flavor with the minimum cost comes first. When creating an instance in an AS group, the system selects the flavor with the minimum cost. If the instance cannot be created, the system selects one with the minimum cost from the remaining flavors, and so on for all available flavors.

Related Operations

If you want to use the newly created AS configuration, add it to the AS group. For details, see Creating an AS Group or Changing the AS Configuration for an AS Group.