Overview
Renew the specified Auto Scaling Group.
Only the attributes corresponding to the specified parameters will have their values changed, and the attributes corresponding to the parameters that have not been passed will remain at their existing values.
Even if minSize, desiredCapacity, or maxSize are changed by calling this action, the order relationship must still be maintained as maxSize >= desiredCapacity >= minSize.
Zone rebalancing occurs when zoneNoList changes.
If a new launch configuration is specified with calling this action, it takes effect when a new server instance is created.
If you call this while the current scaling action for Auto Scaling Group is in progress, it will throw an error.
- When minSize is specified but desiredCapacity is not specified, if the new minSize value is larger than the current size of the Auto Scaling Group, setDesiredCapacity is implicitly called, and the group size is set to the new minSize.
- When maxSize is specified but desiredCapacity is not specified, if the new maxSize value is smaller than the current size of the Auto Scaling Group, setDesiredCapacity is implicitly called and the group size is set to the new maxSize.
- All optional parameters that are not passed when requested will remain at their existing values. If no optional parameters are passed, no attribute values will be changed. (No error will occur.)
Request
Request parameters
Parameter name | Required | Type | Restrictions | Description |
---|---|---|---|---|
autoScalingGroupName | Yes | String | Min: 1, Max: 255 | Enter the name of the auto scaling group you want to query. |
launchConfigurationName | No | String | Min: 1, Max: 255 | - Launch configuration name Server-related information used when a server instance belonging to the corresponding auto scaling group is newly created |
desiredCapacity | No | Integer | Min: 0, Max: 30 | - Expected service capacity Set the number of server instances to be operated as a member of the group. This value must not be less than the existing attribute minSize, which is already set for autoscaling, and must not be greater than maxSize. |
minSize | No | Integer | Min: 0, Max: 30 | Minimum size (minimum of 0, must be less than or equal to the maxSize value) |
maxSize | No | Integer | Min: 0, Max: 30 | Maximum size |
defaultCooldown | No | Integer | Min: 0, Max: 2147483647 | Default cooldown timedefault : 300 |
healthCheckGracePeriod | Conditional | Integer | Min: 0, Max: 2147483647 | - Health check grace period Set the time to hold off on health checks after a server instance is put into service. Required if the healthCheckTypeCode is LOADB (load balancer) |
healthCheckTypeCode | No | String | Min: 1, Max: 5 | Health check type codeSVR (server) LOADB (load balancer) |
zoneNoList | No | String | It can't be duplicated. | - Zone number list List of zone numbers where server instances belonging to this group will exist |
responseFormatType | No | String | - Format type of the response result Options: xml | json Default: xml |
Response
Response body
Examples
Request example
{AUTOSCALILNG_API_URL}/updateAutoScalingGroup
?autoScalingGroupName=asg-1
&desiredCapacity=0
&maxSize=0
&minSize=0
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>
Errors
Errors that may occur while using this action are listed below. For more information about common errors, see NAVER Cloud Platform API.
HTTP Response Code | Return code | Return message |
---|---|---|
400 | 50120 | An invalid or out-of-range value was supplied for the input parameter. |
400 | 50130 | The quota for capacity groups or launch configurations for this customer has already been reached. |
400 | 50160 | You cannot delete an Auto Scaling group while there are scaling activities in progress for that group. |