MENU
      updateAutoScalingGroup

        updateAutoScalingGroup


        Article summary

        Overview

        Updates the specified Auto Scaling group.
        Only the properties associated with the specified parameters are updated, and the rest stays the same.
        Even if the minSize, desiredCapacity or maxSize is changed, the following condition must be satisfied: maxSize >= desiredCapacity >= minSize.
        If zoneNoList is updated, zones are rebalanced.
        If a new launch configuration is specified, it takes effect when a new server instance is created.
        If this API request is made while a scaling action is being performed for the auto scaling group, an error occurs.

        • When the minSize is specified but the desiredCapacity is not specified, if the new minSize is larger than the current size of the auto scaling group, the setDesiredCapacity action is implicitly called to set the group’s current size to the new minSize.
        • When the maxSize is specified but the desiredCapacity is not specified, if the new maxSize is larger than the current size of the auto scaling group, the setDesiredCapacity action is implicitly called to set the group’s current size to the new maxSize.
        • Those optional parameters that are not specified when the API request is made stay the same. If no optional parameters are specified, no properties are updated. (No errors error.)

        Request

        Request parameters

        ParameterRequiredTypeLimitationsDescription
        autoScalingGroupNameYStringMin: 1, Max: 255Name of the Auto Scaling group to get
        launchConfigurationNameNStringMin: 1, Max: 255Launch configuration name
        It contains server related information used when a new server instance in the Auto Scaling group is created.
        desiredCapacityNIntegerMin: 0, Max: 30It 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.
        minSizeNIntegerMin: 0, Max: 30Minimum size (It is at least 0 and less than or equal to the maxSize.)
        maxSizeNIntegerMin: 0, Max: 30Maximum size
        defaultCooldownNIntegerMin: 0, Max: 2147483647Default cooldown time
        Default: 300
        healthCheckGracePeriodConditionalIntegerMin: 0, Max: 2147483647Health 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: 5Health check type code.
        SVR (Server) LOADB (Load balancer)
        zoneNoListNStringDuplicates 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}/updateAutoScalingGroup
        ?autoScalingGroupName=asg-1
        &desiredCapacity=0
        &maxSize=0
        &minSize=0
        HTTP

        Response example

        <updateAutoScalingGroupResponse>
           <requestId>5e40dcb6-56cc-46cd-ae08-98ec6e611cd9</requestId>
           <returnCode>0</returnCode>
           <returnMessage>success</returnMessage>
           <totalRows>1</totalRows>
           <autoScalingGroupList>
              <autoScalingGroup>
                 <autoScalingGroupName>asg-1</autoScalingGroupName>
                 <autoScalingGroupNo>***517</autoScalingGroupNo>
                 <launchConfigurationName>lc-1</launchConfigurationName>
                 <launchConfigurationNo>***013</launchConfigurationNo>
                 <desiredCapacity>0</desiredCapacity>
                 <minSize>0</minSize>
                 <maxSize>0</maxSize>
                 <loadBalancerInstanceSummeryList>
                    <loadBalancerInstanceSummery>
                       <loadBalancerName>slb-1</loadBalancerName>
                    </loadBalancerInstanceSummery>
                    <loadBalancerInstanceSummery>
                       <loadBalancerName>slb-2</loadBalancerName>
                    </loadBalancerInstanceSummery>
                 </loadBalancerInstanceSummeryList>
                 <healthCheckGracePeriod>600</healthCheckGracePeriod>
                 <healthCheckType>
                    <code>SVR</code>
                    <codeName>Server</codeName>
                 </healthCheckType>
                 <createDate>2014-02-13T17:24:19+0900</createDate>
                 <inAutoScalingGroupServerInstanceList>
                    <InAutoScalingGroupServerInstance>
                       <healthStatus>
                          <code>HLTHY</code>
                          <codeName>Healthy (normal)</codeName>
                       </healthStatus>
                       <lifecycleState>
                          <code>INSVC</code>
                          <codeName>In service</codeName>
                       </lifecycleState>
                       <launchConfiguration>
                          <launchConfigurationName>lc-1</launchConfigurationName>
                          <serverImageProductCode>SPSW0LINUX000009</serverImageProductCode>
                          <serverProductCode>SPSVRSTAND000043</serverProductCode>
                          <memberServerImageNo />
                          <loginKeyName>yh-nang-test</loginKeyName>
                          <createDate>2014-02-13T13:45:57+0900</createDate>
                          <userData />
                       </launchConfiguration>
                       <serverInstanceNo>68084</serverInstanceNo>
                       <serverInstanceName>svr-7f8879ae0826836</serverInstanceName>
                    </InAutoScalingGroupServerInstance>
                 </inAutoScalingGroupServerInstanceList>
                 <suspendedProcessList />
                 <zoneList>
                    <zone>
                       <zoneNo>2</zoneNo>
                       <zoneName>KR-1</zoneName>
                       <zoneCode>KR-1</zoneCode>
                       <zoneDescription>Gasan zone</zoneDescription>
                    </zone>
                 </zoneList>
              </autoScalingGroup>
           </autoScalingGroupList>
        </updateAutoScalingGroupResponse>
        XML

        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
        40050120An invalid or out-of-range value was supplied for the input parameter.
        40050130The quota for capacity groups or launch configurations for this customer has already been reached.
        40050160You cannot delete an Auto Scaling group 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.