as
  1. Help Center
  2. AS Management
  3. AS Configurations
  4. Using a New Specifications Template to Create an AS Configuration

Using a New Specifications Template to Create an AS Configuration

If you have special requirements on the ECSs for resource expansion, use a new specifications template to create the AS configuration. In such a case, ECSs meeting specifications of the template will be added to the AS group in scaling actions.

Procedure

  1. Log in to the management console.
  2. Under Computing, click Auto Scaling.
  3. Click Create AS Configuration.
  4. Set the parameters for the AS configuration. Table 1 lists the AS configuration parameters.
    Table 1 AS configuration parameters

    Parameter

    Description

    Example Value

    Name

    Specifies the name of an AS configuration.

    N/A

    Configuration Template

    Select Create a new specifications 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 a new specifications template

    I/O Optimization

    Enabling I/O optimization improves network performance between different ECSs and between ECSs and EVS disks attached to the ECSs, which improves the storage performance of the EVS disks. This configuration is optional.

    NOTE:

    I/O optimization is provided only in certain AZs. Therefore, the system allocates the ECSs in an AS group where this parameter is selected for the AS configuration only to the AZs supporting I/O optimization.

    N/A

    Specifications

    The system provides various ECS types for different application scenarios.

    For details, see sections "ECS Types and Specifications" and "Scenarios" in Elastic Cloud Server User Guide.

    Configure the ECS specifications, including vCPUs, memory, image type, and disk, according to the ECS type.

    Memory-optimized ECS

    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. You can configure the applications 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 private image to create ECSs removes the need to configure multiple ECSs repeatedly.

      NOTE:

      If you select an encrypted image, you must grant key management system (KMS) access rights to EVS. Otherwise, encryption cannot be used. If you have rights granting permission, grant the KMS access rights to EVS. If you do not have the permission, contact the user having the security administrator rights to grant the KMS access rights. For details, see Identity and Access Management User Guide.

      • Encrypted: indicates that the image has been encrypted.
      • KMS Key Name: specifies the name of the key used by the encrypted image. By default, the name is ims/default.
      • Xrole Name: EVSAccessKMS: indicates that EVS has obtained the KMS access rights.

      For more information about encrypted images, see Image Management Service User Guide.

    • Shared image

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

    Public image

    License Type

    Specifies a license type for using an OS or software on the platform. If the image you selected is free of charge, this parameter is unavailable. If the image you selected is charged, such as an Ubuntu, SUSE, Oracle Linux, or Windows Server Edition image, this parameter is available.

    • Use license from the system

      Allows you to use the license provided by the platform. Obtaining the authorization of such a license is charged.

    • Bring your own license (BYOL)

      Allows you to use your existing OS license. In such a case, you do not need to apply for a license again.

    For more information about the license type, see Elastic Cloud Server User Guide.

    Bring your own license (BYOL)

    Disk

    Includes system disks and data disks. You can select an EVS disk.
    • 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.

      Ultra-high I/O: uses solid state disk (SSD) drives to store data.

    • Data Disk

      You can create multiple data disks for an ECS. In addition, you can specify a data disk image for exporting data.

      When encrypting a data disk, select Encryption for it. KMS access rights must be granted to EVS for using the encryption feature. If you have rights granting permission, grant the KMS access rights to EVS. If you do not have the permission, contact the user having the security administrator rights to grant the KMS access rights. For details, see Identity and Access Management User Guide.

      • Xrole Name: EVSAccessKMS: indicates that EVS has obtained the KMS access rights.
      • KMS Key Name: specifies the name of the key used by the encrypted data disk. By default, the name is evs/default.
      • KMS Key ID: specifies the ID of the key used by the encrypted data disk.

      For more information about EVS disk encryption, see Elastic Volume Service User Guide.

    Common I/O for System Disk

    EIP

    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 deployed in a cluster or on a private network.

    • Automatically assign

      An EIP with exclusive bandwidth is automatically assigned to each ECS. You can set the bandwidth size.

    Automatically assign

    Login Mode

    An ECS can be authorized using a key pair or a password.
    • Key Pair

      In this mode, keys are used for authenticating the users who attempt to log in to target ECSs. If you select this mode, create or import a key pair on the Key Pair page.

      NOTE:

      If you use an existing key, make sure that you have saved the key file locally. Otherwise, logging in to the ECS will fail.

    • Password

      In this mode, the initial password of user root (for Linux) or user Administrator (for Windows) is used for authentication. You can log in to an ECS using the username and its initial password.

    Admin@123

    File Injection

    Enables the system 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 Linux, specify the path for storing the injected file, for example /etc/foo.txt.
    • For Windows, the injected file is automatically stored in the root directory of disk C. You only need to specify the file name, such as foo. The file name can contain only letters and digits.

    N/A

    User Data Injection

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

    N/A

  5. Click Create Now. The Confirm Specifications page is displayed.
  6. Check the AS configuration, and click Confirm Application.

    The system displays a message indicating that the AS configuration has been created and switches to the AS Configurations page. You can view the newly created AS configuration then.

  7. If you want to use the newly created AS configuration, add it to the AS group. For details, see section Replacing an AS Configuration in an AS Group.
  8. (Optional) Enable the AS group.

    If the AS group is in Disabled state, enable it. For details, see section Enabling an AS Group.