Huawei Auto Scaling User Manual

Auto Scaling

User Guide

Issue 01

Date 2020-10-27

HUAWEI TECHNOLOGIES CO., LTD.

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specied in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every eort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.

Auto Scaling User Guide Contents

1 AS Group....................................................................................................................................1

1.1 Creating an AS Group............................................................................................................................................................ 1

1.2 (Optional) Adding a Load Balancer to an AS Group.................................................................................................. 5

1.3 Replacing AS Conguration in an AS Group..................................................................................................................6

1.4 Enabling an AS Group............................................................................................................................................................6

1.5 Disabling an AS Group.......................................................................................................................................................... 7

1.6 Modifying an AS Group.........................................................................................................................................................8

1.7 Deleting an AS Group............................................................................................................................................................ 9

2 AS Conguration................................................................................................................... 10

2.1 Creating an AS Conguration...........................................................................................................................................10

2.2 Using an Existing ECS to Create an AS Conguration............................................................................................. 10

2.3 Using a New Specications Template to Create an AS Conguration............................................................... 14

2.4 Copying an AS Conguration........................................................................................................................................... 20

2.5 Deleting an AS Conguration...........................................................................................................................................20

3 AS Policy.................................................................................................................................. 21

3.1 Overview.................................................................................................................................................................................. 21

3.2 Creating an AS Policy.......................................................................................................................................................... 22

3.3 Managing AS Policies.......................................................................................................................................................... 31

4 Scaling Action........................................................................................................................ 33

4.1 Dynamically Expanding Resources..................................................................................................................................33

4.2 Expanding Resources as Planned.................................................................................................................................... 35

4.3 Manually Expanding Resources....................................................................................................................................... 36

Conguring an Instance Removal Policy...................................................................................................................... 37

4.4

4.5 Viewing a Scaling Action.................................................................................................................................................... 38

4.6 Managing Lifecycle Hooks.................................................................................................................................................39

4.7 Conguring Instance Protection...................................................................................................................................... 45

4.8 Standby Instance................................................................................................................................................................... 46

5 Bandwidth Scaling................................................................................................................ 48

5.1 Creating a Bandwidth Scaling Policy..............................................................................................................................48

5.2 Viewing Details About a Bandwidth Scaling Policy.................................................................................................. 54

5.3 Managing a Bandwidth Scaling Policy.......................................................................................................................... 55

Auto Scaling User Guide Contents

6 AS Group and Instance Monitoring...................................................................................58

6.1 Health Check.......................................................................................................................................................................... 58

6.2 Conguring Notication for an AS Group....................................................................................................................59

6.3 Recording AS Resource Operations................................................................................................................................ 60

6.4 Adding Tags to AS Groups and Instances..................................................................................................................... 63

6.5 Monitoring Metrics............................................................................................................................................................... 64

6.6 Viewing Monitoring Metrics..............................................................................................................................................69

6.7 Setting Monitoring Alarm Rules...................................................................................................................................... 70

Auto Scaling User Guide 1 AS Group

1 AS Group

1.1 Creating an AS Group

Scenarios

Notes

An AS group consists of a collection of instances and AS policies that have similar attributes and apply to the same application scenario. An AS group is the basis for enabling or disabling AS policies and performing scaling actions. The congured AS policy automatically adds or deletes instances to or from an AS group, or maintains a

When creating an AS group, specify an AS one or more AS policies for the AS group.

Creating an AS group involves the conguration of the maximum, minimum, and expected numbers of instances and the associated load balancer.

ECS types supported by must choose a proper AS conguration according to the ECS type supported by the AZs used by the AS group.

● If the ECS type AZs used by the AS group, the following situations will occur:

– If the AS group is disabled, it cannot be enabled.

– If the AS group is enabled, its status will become abnormal when

instances are added to it.

● If the ECS type AZs used by the AS group, the ECSs added by a scaling action are distributed only in the AZs supporting the ECS type. As a result, the instances in the AS group may not be evenly distributed.

xed number of instances in an AS group.

conguration for it. Additionally, add

dierent AZs may vary. When creating an AS group, you

specied in the AS conguration is supported by none of the

specied in the AS conguration is supported only by certain

pre-

Procedure

1. Log in to the management console.

Auto Scaling User Guide 1 AS Group

2. Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.

3. Click Create AS Group.

4. Set parameters, such as Name, Max. Instances, Min. Instances, and

Expected Instances. Table 1-1 describes the key parameters to be congured.

Table 1-1 AS group parameters

ParameterDescription Example

Value

Region A region is where an AS group resides. N/A

AZ An AZ is a physical region where resources use

independent power supply and networks. AZs are physically isolated but interconnected through an internal network.

Multi-AZ Extensio n Policy

This parameter can be set to Load-balanced or Sequenced.

● Load-balanced: When expanding ECSs in an AS group, the system preferentially distributes ECSs evenly among AZs used by the AS group. If it fails in the target AZ, it automatically selects another AZ based on the sequenced policy.

● Sequenced: When expanding ECSs in an AS group, the system selects the target AZ based on the order in which AZs are selected.

NOTE

This parameter needs to be more AZs are selected.

congured when two or

Name Species the name of the AS group to be created.

The name contains 1 to 64 characters and consists of only letters, digits, underscores (_), and hyphens (-).

N/A

Loadbalanced

N/A

Max. Instance

Species the maximum number of ECS instances in an AS group.

Expected Instance s

Species the expected number of ECS instances in an AS group.

After an AS group is created, you can change this

value, which will trigger a scaling action.

Min. Instance

Species the minimum number of ECS instances in an AS group.

Auto Scaling User Guide 1 AS Group

ParameterDescription Example

Value

congur ation

Species the required AS conguration for the AS group. An AS conguration denes the specications of the ECSs to be added to an AS

group. The specications include the ECS image and system disk size. You need to create the required AS

conguration before creating an AS

group.

VPC Provides a network for your ECSs.

All ECSs in an AS group belong to the same VPC.

Subnet You can select a maximum of ve subnets. The AS

group automatically binds all NICs to the created ECSs. The rst subnet is used by the primary NIC of the ECS by default, and other subnets are used by extension NICs of the ECS.

Load Balancin g

This parameter is optional. A load balancer automatically distributes access trac to all instances in an AS group to balance their service load. It enables higher levels of fault tolerance in your applications and expands application service capabilities.

NOTE

● Up to six load balancers can be added to an AS group.

● After multiple load balancers are added to an AS group, multiple services can be concurrently listened to, thereby improving service scalability. If ELB health check is selected for Health Check Method, when any one of the listeners detects that an instance becomes faulty, AS will replace the faulty instance with a functional one.

If you select Enhanced load balancerIf you select Elastic load balancer,

congure the following

parameters:

● Load Balancer

● Backend ECS Group

● Backend Port:

species the port on which a

backend ECS listens for trac.

● Weight: determines the portion of requests a backend ECS processes compared to other backend ECSs added to the same listener. For more information about load balancing,

Elastic Load Balance User Guide

see

N/A

Auto Scaling User Guide 1 AS Group

ParameterDescription Example

Value

Instance Removal Policy

Species the priority for removing instances from an AS group. If specied conditions are met, scaling actions are triggered to remove instances. AS supports the following instance removal policies:

● Oldest instance created from oldest AS conguration: The oldest instance created based on the oldest conguration is removed from the AS group

rst.

● Newest instance created from oldest AS conguration: The latest instance created based on the oldest conguration is removed from the AS group rst.

● Oldest instance: The oldest instance is removed from the AS group rst.

● Newest instance: The latest instance is removed from the AS group

NOTE

● Removing instances will preferentially ensure that the remaining instances are load balanced in AZs.

● A manually added ECS is removed in the lowest priority. AS does not delete a manually added ECS when removing it. If multiple manually added ECSs must be removed, AS preferentially removes the earliest-added ECS.

rst.

Oldest instance created from oldest AS

congurati on

EIP If EIP has been selected in an AS conguration for

an AS group, an EIP is automatically bound to the ECS added by a scaling action to the AS group. If you select Release, the EIP bound to an ECS is released when the ECS is removed from the AS group. Otherwise, the system unbinds the EIP from the ECS, but does not release it when the ECS is removed from the AS group.

N/A

Auto Scaling User Guide 1 AS Group

ParameterDescription Example

Value

Health Check Method

Advance d Settings

When a health check detects a faulty ECS, AS removes the faulty ECS from the AS group and adds a new one. The health check is implemented using any of the following methods:

● ECS health check: checks ECS running status. If an ECS is stopped or deleted, it is considered as abnormal. This method is selected by default. Using this method, the AS group periodically determines the running status of each ECS based on the health check result. If the health check result shows that an ECS is faulty, AS removes the ECS from the AS group.

● ELB health check: determines ECS running status using a load balancing listener. This health check method is available only when the AS group uses a load balancing listener. When a load balancing listener detects that an ECS is faulty, AS removes the ECS from the AS group.

Congure notications and tags.

You can select Do not congure or Congure now.

N/A

5. Click Next. On the Add AS existing AS

6. Click Create Now.

7. Check the AS group and AS conguration information. Then click Submit.

8. (Optional) Add AS policies. For details, see Creating an AS Policy.

conguration or create one. For details, see .

Conguration page, you can choose to use an

1.2 (Optional) Adding a Load Balancer to an AS Group

Elastic Load Balance (ELB) automatically distributes incoming trac across multiple backend servers based on congured forwarding policies. ELB expands the service capabilities of applications and improves their availability by eliminating single points of failure (SPOFs).

If ELB functions are required, perform the operations provided in this section to add a load balancer to your AS group. The load balancer added to an AS group distributes application added to or deleted from the AS group.

Only a created load balancer can be bound to an AS group, and the AS group and load balancer must be in the same VPC. For details about how to create a load balancer, see group, perform the following operations:

Elastic Load Balance User Guide

trac to all instances in the AS group when an instance is

. To add a load balancer for an AS

● When creating an AS group, load balancer. For details, see Creating an AS Group.

congure parameter Load Balancing to add a

Auto Scaling User Guide 1 AS Group

● If an AS group has no scaling action ongoing, modify parameter Load

Balancing to add a load balancer. For details, see Modifying an AS Group.

1.3 Replacing AS Conguration in an AS Group

Scenarios

If you need to change the ECS specications in an AS group, you need to change the AS conguration.

Eective Time of New AS Conguration

If the AS group has an in-progress scaling action, the new AS conguration will take eect only for instances scaled in later scaling actions.

For example, the current AS conguration of the AS group is as-cong-A, and the new AS conguration is as-cong-B. The instance conguration in the current scaling action is still

The instance conguration will change to as-cong-B in the next scaling action.

as-cong-A.

Figure 1-1 Changing the AS conguration

Procedure

1. Log in to the management console.

2. Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling. Then click the AS Groups tab.

3. Click the name of the target AS group. On the Basic Information page, click

Change

You can also locate the row containing the target AS group and choose More > Change Conguration in the Operation column.

4. In the displayed Change AS Conguration dialog box, select another AS conguration to be used by the AS group.

5. Click OK.

Conguration to the right of Conguration Name.

1.4 Enabling an AS Group

Scenarios

You can enable an AS group to automatically increase or decrease instances.

After an AS group is enabled, its status changes to Enabled. AS monitors the AS policy and triggers a scaling action for AS groups only in Enabled state. After an AS group is enabled, AS triggers a scaling action to automatically add or remove

Auto Scaling User Guide 1 AS Group

instances if the number of instances in the AS group is dierent from the expected number of instances.

● Only AS groups in the Disabled state can be enabled.

● Only AS groups in the Abnormal state can be forcibly enabled. You can choose More > Forcibly Enable to enable an abnormal AS group. Forcibly enabling an AS group does not have adverse consequences.

● After you create an AS group and add an AS conguration to an AS group, the AS group is automatically enabled.

Enabling an AS Group

1. Log in to the management console.

2. Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling. Then click the AS Groups tab.

3. In the AS group list, locate the row containing the target AS group and click Enable in the Operation column. You can also click the AS group name and then Enable to the right of Status on the Basic Information page to enable the AS group.

4. In the Enable AS Group dialog box, click Yes.

Forcibly Enabling an AS Group

1. Log in to the management console.

2. Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling. Then click the AS Groups tab.

3. In the AS group list, locate the row containing the target AS group and select Forcibly Enable from the More drop-down list in the Operation column. You can also click the AS group name and then Forcibly Enable to the right of Status on the Basic Information page to enable the AS group.

4. In the Forcibly Enable AS Group dialog box, click Yes.

1.5 Disabling an AS Group

Scenarios

When you are required to stop an instance in an AS group for upgrade, disable the AS group before performing the operation. This prevents the instance from being deleted in a health check. When the instance status restores, enable the AS group again.

If a scaling action, for example, creating an instance or EVS disk, consistently fails (the failure cause can be viewed on the Elastic Cloud Server page) and retries in an AS group, use either of the following methods to stop the retry:

conguration or

● Disable the AS group. Then, the scaling action that is being performed fails and will not retry. Enable the AS group again when the environment recovers or after replacing the AS

● Disable the AS group and change the expected number of instances to the number of existing instances. After the scaling action fails and ends, the scaling action will not retry.

conguration.

NO TE

Auto Scaling User Guide 1 AS Group

After an AS group is disabled, its status changes to Disabled. AS does not automatically trigger any scaling actions for a Disabled AS group. When an AS group has an in-progress scaling action, the scaling action does not stop immediately after the AS group is disabled.

You can disable an AS group when its status is Enabled or Abnormal.

Procedure

1. Log in to the management console.

2. Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling. Then click the AS Groups tab.

3. In the AS group list, locate the row containing the target AS group and click Disable in the Operation column. You can also click the AS group name and then Disable to the right of Status on the Basic Information page to disable the AS group.

4. In the Disable AS Group dialog box, click Yes.

1.6 Modifying an AS Group

Scenarios

You can modify an AS group as needed. The values of the following parameters can be changed: Name, Max. Instances, Min. Instances, Expected Instances, Health Check Method, Health Check Interval, Instance Removal Policy.

Changing the value of Expected Instances will trigger a scaling action. Then, AS automatically increases or decreases the number of instances to the value of Expected Instances.

If the AS group is not enabled, contains no instance, and has no scaling action ongoing, you can modify Subnet action ongoing, you can modify its AZ and ELB congurations.

Procedure

1. Log in to the management console.

2. Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling. Then click the AS Groups tab.

congurations. If an AS group has no scaling

3. In the AS group list, locate the row containing the target AS group, click the AS group name to switch to the Basic Information page, and click Modify in the upper right corner.

You can also locate the row containing the target AS group and choose More > Modify in the Operation column.

4. In the Modify AS Group dialog box, modify related data, for example, the expected number of instances.

5. Click OK.

Auto Scaling User Guide 1 AS Group

1.7 Deleting an AS Group

Scenarios

You can delete an AS group when it is no longer required.

Procedure

● If an AS group is not required during a advised to disable it but not delete it.

● For an AS group that has an instance or ongoing scaling action, if you attempt to forcibly delete the AS group and remove and delete the instances in the AS group, the AS group enters the deleting state, rejects new scaling requests, waits until the ongoing scaling action completes, and removes all instances from the AS group. Then, the AS group is automatically deleted. Manually added instances are only removed out of the AS group, while the instances automatically created in a scaling action are removed and deleted. During the preceding process, you are not allowed to perform other operations in the AS group.

● After an AS group is deleted, its AS policies and the alarm rules generated based on the AS policies deleted.

1. Log in to the management console.

2. Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.

3. In the AS group list, locate the row containing the target AS group and choose More > Delete in the Operation column.

4. In the displayed Delete AS Group dialog box, click Yes.

congured for the AS group will be automatically

specied period of time, you are

Auto Scaling User Guide 2 AS Conguration

2 AS Conguration

2.1 Creating an AS Conguration

Scenarios

Methods

An AS conguration denes the specications of the ECSs to be added to an AS group. The specications include the ECS image and system disk size.

● When you create an AS group, create an AS conguration or use an existing

conguration.

● Create the required AS conguration on the Instance Scaling page.

● Change the AS conguration on the AS group details page.

● Using an existing ECS to create an AS conguration

When you create an AS conguration using an existing ECS, the vCPU, memory, image, disk, and ECS type are the same as those of the selected ECS by default. For details, see Using an Existing ECS to Create an AS

Conguration.

● Using a new specications template to create an AS conguration

If you have special requirements on the ECSs for resource expansion, use a

specications template to create the AS conguration. For details, see

new

Using a New Specications Template to Create an AS Conguration.

2.2 Using an Existing ECS to Create an AS

Conguration

Scenarios

You can use an existing ECS to rapidly create an AS conguration. In such a case, the parameter settings, such as the vCPUs, memory, image, disk, and ECS type in the AS

conguration are the same as those of the selected ECS by default.

Auto Scaling User Guide 2 AS Conguration

Procedure

1. Log in to the management console.

2. Under Computing, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling.

3. Click Create AS Conguration.

4. Set the parameters for the AS conguration parameters.

Table 2-1 AS conguration parameters

Parameter Description Example

Region A region is where an AS conguration resides. N/A

Name Species the name of an AS conguration. N/A

conguration. Table 2-1 lists the AS

Value

Conguratio n Template

Select Use specications of an existing ECS and click Select ECS.

The ECS type, vCPUs, memory, image, and disk information in the AS conguration are the same as those of the selected ECS by default.

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. The bandwidth size is

NOTE

If you select Automatically assign, you need to specify Type, Bandwidth Type, Billed By, and Bandwidth.

congurable.

Use

specication s of an

existing ECS

Automaticall y assign

Auto Scaling User Guide 2 AS Conguration

Parameter Description Example

Value

Bandwidth Type

You can select Dedicated or Shared.

● Dedicated: The bandwidth can be used by only one EIP.

● Shared: The bandwidth can be used by multiple EIPs.

NOTE

● This parameter is available only when EIP is set to Automatically assign.

● If you select Dedicated, you can select Bandwidth or

● The shared bandwidth can be billed only by bandwidth. You can select a shared bandwidth to which the EIP is to be added.

Trac for Billed By.

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 logging in to the ECS will fail.

le locally. Otherwise,

● 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.

Shared

Admin@123

Advanced Settings

This allows you to congure User Data Injection and ECS Group.

N/A

You can select Do not congure or Congure now.

Auto Scaling User Guide 2 AS Conguration

Parameter Description Example

Value

User Data Injection

Enables the ECS to automatically inject user data when the ECS starts for the rst time. This conguration is optional. After this function is enabled, the ECS automatically injects user data upon its rst startup.

For details, see

Guide

Elastic Cloud Server User

The following methods are available:

● As text: allows you to enter the user data in the text box below.

le: allows you to inject script les or

● As other les when you create an ECS. If you select As le, the system automatically injects the

les into a specied directory

when creating an ECS.

– For Linux, specify the path for storing

the injected

le, for example /etc/

foo.txt.

– For Windows, the injected le is

automatically stored in the root directory of disk C. You only need to specify the

le name, such as foo. The

le name can contain only letters and

digits.

NOTE

● For Linux, if you use the password authentication mode, the user data injection function is unavailable.

● If the selected image does not support user data injection, the user data injection function is unavailable.

ECS Group An ECS group allows you to create ECSs on

N/A dierent hosts, thereby improving service reliability.

5. Click Create Now.

6. Click Create Now.

7. If you want to use the newly created AS

conguration, add it to the AS group.

For details, see Replacing AS Conguration in an AS Group.

8. (Optional) Enable the AS group.

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

Group.

Auto Scaling User Guide 2 AS Conguration

2.3 Using a New Specications Template to Create an AS Conguration

Scenarios

If you have special requirements on the ECSs for resource expansion, use a new specications template to create the AS conguration. In such a case, ECSs meeting specications 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. In the navigation pane on the left, choose Instance Scaling.

3. Click Create AS

4. Set the parameters for the AS conguration parameters.

Conguration.

conguration. Table 2-2 lists the AS

Table 2-2 AS

Parameter

Region A region is where an AS conguration

Name Species the name of the AS

Conguratio n Template

CPU Architecture

conguration parameters

Description Example Value

resides.

conguration to be created.

Select Create a new specications template.

If this option is selected, congure parameters, such as the vCPUs, memory, image, disk, and ECS type, to create a new AS

The following two types of CPU architectures are available:

● x86: The x86-based CPU architecture

● Kunpeng: The Kunpeng-based CPU

conguration.

uses Complex Instruction Set Computing (CISC).

architecture uses Reduced Instruction Set Computing (RISC).

N/A

Create a new

specications

template

x86

Auto Scaling User Guide 2 AS Conguration

Parameter Description Example Value

SpecicationsThe public cloud provides various ECS

types for dierent application scenarios.

For more information, see

Server User Guide

Elastic Cloud

Congure the ECS specications, including vCPUs, memory, image type, and disk, according to the ECS type.

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 congure 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 congure multiple ECSs repeatedly.

● Shared image A shared image is a private image shared by another public cloud user.

Memoryoptimized ECS

Public image

Auto Scaling User Guide 2 AS Conguration

Parameter Description Example Value

Disk Includes system disks 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.

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.

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

If the image you selected is of the full-ECS image type, you can change the volume type and size and encryption attributes of the data disk restored using the disk backup. Ensure that the volume size is greater than or equal to the disk backup size, and the encryption attributes can be modied only if the disk backup of the full-ECS image locates in the target region.

Common I/O System Disk

for

Security Group

Controls ECS access within or between security groups by dening access rules.

N/A

ECSs added to a security group are protected by the access rules you dene.

Auto Scaling User Guide 2 AS Conguration

Parameter Description Example Value

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, you need to specify Type, Billed By, and Bandwidth.

Bandwidth You can select Dedicated or Shared.

● Dedicated: The bandwidth can be used by only one EIP.

● Shared: The bandwidth can be used by multiple EIPs.

NOTE

● This parameter is available only when EIP is set to Automatically assign.

● If you select Dedicated, you can select Bandwidth or

● The shared bandwidth can be billed only by bandwidth. You can select a shared bandwidth to which the EIP is to be added.

Trac for Billed By.

Automatically assign

Shared

Auto Scaling User Guide 2 AS Conguration

Parameter Description Example Value

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 Otherwise, logging in to the ECS will fail.

le locally.

Advanced Settings

This parameter allows you to congure ECS Group and User Data Injection.

You can select Do not congure or Congure now.

Admin@123

N/A

Auto Scaling User Guide 2 AS Conguration

Parameter Description Example Value

User Data Injection

For details, see

User Guide

Elastic Cloud Server

The following methods are available:

● As text: allows you to enter the user data in the text box below.

le: allows you to inject script les

● As or other les when you create an ECS. If you select As

le, the system automatically injects the les into a specied directory when creating an ECS.

– For Linux, specify the path for

storing the injected

le, for

example /etc/foo.txt.

– For Windows, the injected

le is automatically stored in the root directory of disk C. You only need to specify the foo. The

le name, such as

le name can contain

only letters and digits.

NOTE

● For Linux, if you use the password authentication mode, the user data injection function is unavailable.

● If the selected image does not support user data injection, the user data injection function is unavailable.

ECS Group An ECS group allows you to create ECSs

N/A on dierent hosts, thereby improving service reliability.

5. Click Create Now. The system displays a message indicating that the AS conguration is successfully created.

6. If you want to use the newly created AS conguration, add it to the AS group. For details, see Replacing AS

Conguration in an AS Group.

+ 51 hidden pages