Copying an AS Configuration

Scenarios

You can copy an existing AS configuration.

When copying an AS configuration, you can modify parameter settings, such as the configuration name, ECS specifications, and image of the existing AS configuration to rapidly add a new AS configuration.

Procedure

1. Log in to the AS console.
2. On the Instance Scaling page, click the AS Configurations tab, locate the row containing the target AS configuration, and click Replicate in the Operation column.

   

3. In the displayed dialog box, modify the 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
   Name	Specifies the AS configuration name. The name consists of 1 to 64 characters, including only letters, digits, underscores (_), and hyphens (-).	-
   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).	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 you to select based on application scenarios. Configure the ECS parameters, including the vCPUs/memory ratio, image type, and disk, based on the ECS type. You can select a maximum of 10 ECS flavors for an AS configuration. For details about configuring multiple ECS flavors in an AS configuration, see Notes on Multiple Flavors in an AS Configuration. For details about how to select ECS flavors, see ECS Types.	c9.large.2
   Flavor selection policy	This parameter is displayed when you select two or more ECS flavors. It is not displayed when you select only one ECS flavor. It specifies the order in which AS selects instance flavors for an AS group. You can select Sequenced or Cost-centered. Sequenced: When an ECS is added for capacity expansion, the target flavor is determined in the order in which it was selected. If the current flavor is unavailable, the system will automatically select the next flavor for capacity expansion. Cost-centered: When an ECS is added for capacity expansion, the target flavor is determined for minimal expenses on the basis of one vCPU. If the current flavor is unavailable, the system will automatically select the next flavor for capacity expansion. For details about the order in which flavors are selected, 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 image provided by the cloud platform and is available to all users. It contains an OS and preinstalled public applications. 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. 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. You can change the disk type and size or add data disks. System Disk The following disk types are supported: 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. NOTE: If the image based on which an ECS is created is encrypted, the system disk of the ECS is automatically encrypted. In addition, the name of the encrypted key is displayed on the page. If a full-ECS image is used, the system disk is restored using the disk backup. On the console, you can only change the disk type and size. The disk size cannot be smaller than the disk backup. Different ECS flavors support different disk types. The supported disk types are displayed on the 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 disk encryption. The following encryption parameters are displayed only when you select Encryption: 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. 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 to 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. (Optional) Create Disk from Data Disk Image: Click Create Disk from Data Disk Image and select a desired data disk image. 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. NOTE: The encryption function cannot be used together with the function of creating disks from data disk images.	-
   Security Group	Controls ECS access within or between security groups by defining access rules. You can define access rules for a security group. Then these rules will apply to all cloud resources added to this security group. 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
   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 User Data and ECS Group. 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. The following methods are available: As text: Copy user data from the script to the text box. As file: Upload the user data script to the cloud platform. For details, see Injecting User Data. 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 OK.