---
title: "createLaunchConfiguration"
slug: "compute-autoscaling-createlaunchconfiguration"
updated: 2026-09-17T10:05:57Z
published: 2026-09-17T10:05:57Z
canonical: "api.ncloud-docs.com/compute-autoscaling-createlaunchconfiguration"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://api.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# createLaunchConfiguration

## Overview

A launch configuration is a template used by Auto Scaling to create cloud server instances and put them into service. The template contains all the information Auto Scaling needs to create a server instance. Once created, the launch configuration attributes can't be changed.

## Request

### Request parameters

| Parameter name | Required | Type | Restrictions | Description |
| --- | --- | --- | --- | --- |
| launchConfigurationName | No | String | Min: 1 Max: 255 | It acts as an identifier as the name of the launch configuration. default: automatically assigned by NAVER Cloud Platform |
| serverImageProductCode | Conditional | String | Min: 1 Max: 20 | - Product code of the software (including OS) installed on the server image `serverImageProductCode` (software product code) `memberServerImageNo` (member server image number) Only one of the two values must be specified. |
| serverProductCode | No | String | Min: 1 Max: 20 | Server product code related to server hardware spec default: created with minimum specifications |
| memberServerImageNo | Conditional | String | - | - My server image number created by the member `serverImageProductCode` (software product code) `memberServerImageNo` (member server image number) Only one of the two values must be specified. |
| accessControlGroupConfigurationNoList | No | List | It can't be duplicated. | If you do not specify a value for the Access Control Group (ACG) configuration number, the default Access Control Group (ACG) is specified. |
| loginKeyName | No | String | Min: 3 Max: 30 | - Login key name If not specified, the name of the login key created most recently by the user is specified. default: Use the most recently created login key name. |
| userData | No | String | Min: 1 Max: 21847 | Only BASE64 encoded strings are allowed as user data. When the server instance is booted for the first time, a script file consisting of plain text strings is executed by decoding the BASE64 encoded strings. If two parameters, userData and initScriptNo, are passed together, a creation error will occur. |
| initScriptNo | No | String |  | - Initialization script number Run the initialization script set by the user when the server boots for the first time. Initialization script number of the initialization script is passed as a parameter. If two parameters, userData and initScriptNo, are passed together, a creation error will occur. initScriptNo can be obtained through the getInitScriptList action. |
| regionNo | No | String |  | You can obtain the status where input is possible through the getRegionList action. |
| responseFormatType | No | String |  | - Format type of the response result Options: xml \| json Default: xml |

## Response

### Response body

- [LaunchConfigurationList](/docs/en/common-apidatatype-launchconfigurationlist)

## Examples

### Request example

```
{AUTOSCALILNG_API_URL}/createLaunchConfiguration
?launchConfigurationName=lc-0228
&serverImageProductCode=SPSW0LINUX000009
```

### Response example

```
<createLaunchConfigurationResponse>
   <requestId>19fff23d-d5cd-49fd-8a0a-986ae02bf660</requestId>
   <returnCode>0</returnCode>
   <returnMessage>success</returnMessage>
   <totalRows>1</totalRows>
   <launchConfigurationList>
      <launchConfiguration>
         <launchConfigurationName>lc-0228</launchConfigurationName>
         <launchConfigurationNo>***013</launchConfigurationNo>
         <serverImageProductCode>SPSW0LINUX000009</serverImageProductCode>
         <serverProductCode>SPSVRSTAND000043</serverProductCode>
         <memberServerImageNo />
         <loginKeyName>hkey-0217</loginKeyName>
         <createDate>2014-02-28T17:11:36+0900</createDate>
         <userData />
         <initScriptNo />
      </launchConfiguration>
   </launchConfigurationList>
</createLaunchConfigurationResponse>
```