Available in VPC
Create a Launch Configuration.
Request
This section describes the request format. The method and URI are as follows:
Method | URI |
---|---|
GET | POST | /vautoscaling/v2/createLaunchConfiguration |
This guide is based on the GET method. POST method call tests can be performed through Swagger in the API Gateway service of the NAVER Cloud Platform console.
Request headers
For information about the headers common to all Auto Scaling APIs, see Auto Scaling request headers.
Request query parameters
You can use the following query parameters with your request:
Field | Type | Required | Description |
---|---|---|---|
regionCode |
String | Optional | Region code
|
memberServerImageInstanceNo |
String | Conditional | Server image instance number
|
serverImageNo |
String | Conditional | Server image number
|
serverImageProductCode |
String | Conditional | Server image product code
|
serverSpecCode |
String | Conditional | Server specification code
|
serverProductCode |
String | Conditional | Server product code
|
isEncryptedVolume |
Boolean | Optional | Whether to encrypt the default block storage volume
|
initScriptNo |
String | Optional | Init script number
|
launchConfigurationName |
String | Optional | Launch configuration name
|
loginKeyName |
String | Optional | Authentication key name
|
responseFormatType |
String | Optional | Format of the response data
|
When entering a request query parameter, see the following:
- When you create a server from a new server image (scale-out), the available fields vary depending on the hypervisor type of the server image, as follows:
- KVM:
serverImageNo
andserverSpecCode
are used. - XEN:
serverImageNo
andserverSpecCode
orserverImageProductCode
andserverProductCode
are used. - RHV:
serverImageNo
andserverSpecCode
orserverImageProductCode
andserverProductCode
are used.
- KVM:
Request example
The request example is as follows:
curl --location --request GET 'https://ncloud.apigw.ntruss.com/vautoscaling/v2/createLaunchConfiguration
?regionCode=KR
&serverImageNo=100614134
&serverProductCode=SVR.VSVR.CPU.C002.M004.G003
&launchConfigurationName=launchconfigtest
&responseFormatType=json' \
--header 'x-ncp-apigw-timestamp: {Timestamp}' \
--header 'x-ncp-iam-access-key: {Access Key}' \
--header 'x-ncp-apigw-signature-v2: {API Gateway Signature}'
Response
This section describes the response format.
Response body
The response body includes the following data:
Field | Type | Required | Description |
---|---|---|---|
createLaunchConfigurationResponse |
Object | - | Response result |
createLaunchConfigurationResponse.requestId |
String | - | ID for the request
|
createLaunchConfigurationResponse.returnCode |
String | - | Response code |
createLaunchConfigurationResponse.returnMessage |
String | - | Response message |
Response status codes
For response status codes common to all Auto Scaling APIs, see Auto Scaling response status codes.
Response example
The response example is as follows:
{
"createLaunchConfigurationResponse": {
"totalRows": 1,
"launchConfigurationList": [
{
"regionCode": "KR",
"launchConfigurationNo": "5994",
"launchConfigurationName": "launchconfigtest",
"serverImageProductCode": "SW.VSVR.OS.LNX64.UBNTU.SVR24.G003",
"serverProductCode": "SVR.VSVR.CPU.C002.M004.G003",
"loginKeyName": "ncp-loginkey",
"createDate": "2025-06-12T14:15:45+0900",
"launchConfigurationStatus": {
"code": "CREAT",
"codeName": "Created"
},
"initScriptNo": "",
"isEncryptedVolume": false,
"serverImageNo": "100614134",
"osInformation": "ubuntu-24.04",
"serverSpecNo": "1916",
"serverSpecCode": "ci2-g3",
"serverSpecDescription": "vCPU 2EA, Memory 4GB"
}
],
"requestId": "2d7f87e6-****-****-****-94b87f5f5500",
"returnCode": "0",
"returnMessage": "success"
}
}