createAutoScalingGroup
    • PDF

    createAutoScalingGroup

    • PDF

    Article summary

    Overview

    Creates a new Auto Scaling group by specifying a name and other required properties. Once a request to create a new Auto Scaling group is completed, the Auto Scaling group is ready to be used by other API calls. However, this does not mean that server instances in the Auto Scaling group are completely created and used for your services.

    Request

    Request parameters

    ParameterRequiredTypeLimitationsDescription
    autoScalingGroupNameNStringMin: 1
    Max: 255
    It identifies Auto Scaling groups. It cannot be changed once specified.
    launchConfigurationNameYStringMin: 1
    Max: 255
    Launch configuration name
    It contains server related information used when a new server instance in the Auto Scaling group is created.
    desiredCapacityNIntegerMin: 0
    Max: 30
    It is desired capacity, which is the number of server instances that belong to the Auto Scaling group.
    It must be greater than or equal to the current minSize and less than or equal to the current maxSize of the Auto Scaling group.
    minSizeYIntegerMin: 0
    Max: 30
    Minimum size (It is at least 0 and less than or equal to the maxSize.)
    maxSizeYIntegerMin: 0
    Max: 30
    Maximum size
    defaultCooldownNIntegerMin: 0
    Max: 2147483647
    Default cooldown time
    Default: 300
    loadBalancerNameList.NNListMax: 10List of load balancer names to add when a server in this Auto Scaling group is created and starts to run for your services.
    healthCheckGracePeriodConditionalIntegerMin: 0
    Max: 2147483647
    Health check grace period. Auto Scaling waits until the health check grace period ends before checking the health status of the server instance.
    It is required if healthCheckTypeCode is LOADB (Load balancer).
    healthCheckTypeCodeNStringMin: 1
    Max: 5
    Health check type code.
    SVR (Server), LOADB (Load balancer)
    zoneNoListYStringDuplicates not allowedZONE number list
    List of zones in which server instances in this auto scaling group will be located.

    Response

    Response body

    Examples

    Request example

    {AUTOSCALILNG_API_URL}/createAutoScalingGroup
    ?autoScalingGroupName=asg-0224
    &desiredCapacity=0
    &launchConfigurationName=lc-1
    &maxSize=0&minSize=0
    &zoneNoList.1=2
    &zoneNoList.2=3
    

    Response example

    <createAutoScalingGroupResponse>
       <requestId>015a4c61-c887-43f7-89ba-997ccdd75732</requestId>
       <returnCode>0</returnCode>
       <returnMessage>success</returnMessage>
       <totalRows>1</totalRows>
       <autoScalingGroupList>
          <autoScalingGroup>
             <autoScalingGroupName>asg-0224</autoScalingGroupName>
             <autoScalingGroupNo>***517</autoScalingGroupNo>
             <launchConfigurationName>lc-1</launchConfigurationName>
             <launchConfigurationNo>***013</launchConfigurationNo>
             <desiredCapacity>0</desiredCapacity>
             <minSize>0</minSize>
             <maxSize>0</maxSize>
             <loadBalancerInstanceSummeryList />
             <healthCheckGracePeriod>0</healthCheckGracePeriod>
             <healthCheckType>
                <code>SVR</code>
                <codeName>Server</codeName>
             </healthCheckType>
             <createDate>2014-02-24T15:11:11+0900</createDate>
             <inAutoScalingGroupServerInstanceList />
             <suspendedProcessList />
             <zoneList>
                <zone>
                   <zoneNo>2</zoneNo>
                   <zoneName>zone2</zoneName>
                   <zoneDescription>nang zone</zoneDescription>
                </zone>
                <zone>
                   <zoneNo>3</zoneNo>
                   <zoneName>zone3</zoneName>
                   <zoneDescription>nang zone2</zoneDescription>
                </zone>
             </zoneList>
          </autoScalingGroup>
       </autoScalingGroupList>
    </createAutoScalingGroupResponse>
    

    Error codes

    Errors that may occur while using this action are listed below. For information on common errors, refer to NAVER Cloud Platform API.

    HTTP response codeReturn codeReturn message
    40050150This is returned when you cannot delete a launch configuration, scaling policy, or auto scaling group because it is being used.
    40050160You cannot request actions while there are scaling activities in progress for that group.

    Was this article helpful?

    Changing your password will log you out immediately. Use the new password to log back in.
    First name must have atleast 2 characters. Numbers and special characters are not allowed.
    Last name must have atleast 1 characters. Numbers and special characters are not allowed.
    Enter a valid email
    Enter a valid password
    Your profile has been successfully updated.