--- title: "createLoadBalancerInstance" slug: "cli-vloadbalancer-loadbalancer-createloadbalancerinstance" tags: ["Load Balancer", "VPC"] updated: 2026-10-08T05:08:49Z published: 2026-10-08T05:08:49Z canonical: "cli.ncloud-docs.com/cli-vloadbalancer-loadbalancer-createloadbalancerinstance" --- > ## Documentation Index > Fetch the complete documentation index at: https://cli.ncloud-docs.com/llms.txt > Use this file to discover all available pages before exploring further. # createLoadBalancerInstance Available in VPC Create load balancer instances. ## Syntax The `createLoadBalancerInstance` syntax is as follows: ``` ./ncloud vloadbalancer createLoadBalancerInstance \ --loadBalancerTypeCode \ --vpcNo \ --subnetNoList | --loadBalancerSubnetList \ --loadBalancerListenerList \ [--loadBalancerName ] \ [--loadBalancerNetworkTypeCode ] \ [--throughputTypeCode ] \ [--idleTimeout ] \ [--loadBalancerDescription ] \ [--regionCode ] \ [--output ] ``` ## Options This section describes the options available when running `createLoadBalancerInstance`. ### Required options The following options are required for `createLoadBalancerInstance`. | Options | Type | Required | Description | | --- | --- | --- | --- | | `--loadBalancerTypeCode` | String | Required | Load balancer type - `APPLICATION` \| `NETWORK` \| `NETWORK_PROXY` - `APPLICATION`: Application Load Balancer - `NETWORK`: Network Load Balancer - `NETWORK_PROXY`: Network Proxy Load Balancer | | `--vpcNo` | String | Required | VPC number - See [getVpcList](/docs/en/cli-vpc-vpcmanagement-getvpclist). | | `--loadBalancerListenerList` | List | Required | Load balancer listener list - Specify each listener as pairs in the format {field='value'}, separated by commas and enclosed in quotation marks. - `protocolTypeCode` (optional): Protocol type of the load balancer listener. Available values are limited depending on the type of load balancer. Application Load Balancer: `HTTP` (default) \| `HTTPS`, Network Load Balancer: `TCP` (default) \| `UDP`, Network Proxy Load Balancer: `TCP` (default) \| `TLS` - `port` (optional): Port of the load balancer listener `1`~`65534`. The default value is determined by the listener's protocol type (`HTTP`, `TCP`, `UDP`: `80`, `HTTPS`, `TLS`: `443`). Can't be duplicated with existing listener ports. - `targetGroupNo` (required): Target group number applied to each listener's default rule. Target groups already in use by other load balancers can't be used. Available target groups are limited based on the load balancer type and the target group’s protocol type (Application Load Balancer: `HTTP` \| `HTTPS`, Network Load Balancer: `TCP` \| `UDP`, Network Proxy Load Balancer: `PROXY_TCP`). See [getTargetGroupList](/docs/en/cli-vloadbalancer-targetgroup-gettargetgrouplist). - `useHttp2` (optional): Whether to use the HTTP/2 protocol. `true` \| `false` (default). Can be set if the listener’s protocol type is `HTTPS`. - `sslCertificateNo` (conditional): SSL certificate number. An SSL certificate must be configured if the listener’s protocol type is `HTTPS` or `TLS`. See [getCertificateList](/docs/en/security-certificatemanager-getcertificatelist). - `tlsMinVersionTypeCode` (optional): Minimum supported TLS version. `TLSV10` (TLS 1.0, default) \| `TLSV11` (TLS 1.1) \| `TLSV12` (TLS 1.2) \| `TLSV13` (TLS 1.3). `TLS_AES_256_GCM_SHA384`, `TLS_CHACHA20_POLY1305_SHA256`, and `TLS_AES_128_GCM_SHA256` cipher suites are always included. Can be set if the listener’s protocol type is `HTTPS` or `TLS`. - `cipherSuiteList` (optional): List of cipher suites provided by the load balancer during encryption negotiation with the client. `TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA` \| `TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256` \| `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256` \| `TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA` \| `TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384` \| `TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384` \| `TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA` \| `TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256` \| `TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256` \| `TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA` \| `TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384` \| `TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384` \| `TLS_RSA_WITH_AES_128_CBC_SHA` \| `TLS_RSA_WITH_AES_128_CBC_SHA256` \| `TLS_RSA_WITH_AES_128_GCM_SHA256` \| `TLS_RSA_WITH_AES_256_CBC_SHA` \| `TLS_RSA_WITH_AES_256_CBC_SHA256` \| `TLS_RSA_WITH_AES_256_GCM_SHA384` \| `TLS_DHE_RSA_WITH_AES_128_CBC_SHA` \| `TLS_DHE_RSA_WITH_AES_128_CBC_SHA256` \| `TLS_DHE_RSA_WITH_AES_256_CBC_SHA` \| `TLS_DHE_RSA_WITH_AES_256_CBC_SHA256`. Default: Select all. Can be set if the listener's protocol type is `HTTPS` or `TLS`. | | `--subnetNoList` | List | Conditional | List of subnet numbers - Either `subnetNoList` or `loadBalancerSubnetList` must be entered. (If both are provided, `loadBalancerSubnetList` is applied.) - Select the subnet located in the selected VPC. - You can select one load balancer-dedicated subnet per zone. - You can enter multiple items separated by spaces (e.g., `--subnetNoList 23456790 23456791`). - See [getSubnetList](/docs/en/cli-vpc-subnetmanagement-getsubnetlist). | | `--loadBalancerSubnetList` | List | Conditional | List of subnets dedicated to load balancers - Either `subnetNoList` or `loadBalancerSubnetList` must be entered. (If both are provided, `loadBalancerSubnetList` is applied.) - For each subnet, enter {field='value'} pairs enclosed in quotes and separated by commas. - `subnetNo` (conditional): Subnet number. Required when applying `loadBalancerSubnetList`. Select the subnet located in the selected VPC. See [getSubnetList](/docs/en/cli-vpc-subnetmanagement-getsubnetlist). - `publicIpInstanceNo` (optional): Public IP instance number. If left blank, a new public IP will be created and assigned. Can be set if the load balancer's network type is `PUBLIC`. - You can select one subnet per zone dedicated to the load balancer. | ### Optional options These are the optional options for `createLoadBalancerInstance`. Options that are not specified will use their default values. | Options | Type | Required | Description | | --- | --- | --- | --- | | `--loadBalancerName` | String | Optional | Load balancer name - Enter 3-30 characters, including lowercase English letters, numbers, and special `-`. - The string must start with an English letter and end with an English letter or number. - If not entered, NAVER Cloud Platform will assign one automatically. | | `--loadBalancerNetworkTypeCode` | String | Optional | Load balancer network type - `PUBLIC` (default) \| `PRIVATE` | | `--throughputTypeCode` | String | Optional | Load balancing performance type - `SMALL` \| `MEDIUM` \| `LARGE` \| `DYNAMIC` \| `XLARGE` - Available values are limited depending on the load balancer type. - Application, Network Proxy Load Balancer: `SMALL` (default) \| `MEDIUM` \| `LARGE` \| `XLARGE` - Network Load Balancer: `DYNAMIC` (default) | | `--idleTimeout` | Integer | Optional | Connection idle timeout (second) - `1`-`3600` (default: `60`) - Can't be set if the load balancer type is `NETWORK`. | | `--loadBalancerDescription` | String | Optional | Load balancer description (byte) - 0-1000 | ### Common options For information about the options common to all `vloadbalancer` subcommands, see [Load Balancer (VPC) options](/docs/en/cli-vloadbalancer#%EC%98%B5%EC%85%98). ## Examples If the request to create a load balancer instance is successful, the instance's configuration information and creation status are returned. ### Command The command example is as follows: ``` ./ncloud vloadbalancer createLoadBalancerInstance \ --loadBalancerTypeCode APPLICATION \ --vpcNo 12345678 \ --subnetNoList 23456790 \ --loadBalancerListenerList "protocolTypeCode='HTTP', port='80', targetGroupNo='55667788'" \ --loadBalancerName lb-test-01 \ --loadBalancerNetworkTypeCode PRIVATE \ --throughputTypeCode SMALL \ --idleTimeout 60 \ --loadBalancerDescription "Test load balancer" \ --regionCode KR \ --output json ``` ### Output The output example is as follows: ``` { "createLoadBalancerInstanceResponse": { "totalRows": 1, "loadBalancerInstanceList": [ { "loadBalancerInstanceNo": "41112223", "loadBalancerInstanceStatus": { "code": "INIT", "codeName": "LB INIT state" }, "loadBalancerInstanceOperation": { "code": "CREAT", "codeName": "LB CREATE OP" }, "loadBalancerInstanceStatusName": "Creating", "loadBalancerDescription": "Test load balancer", "createDate": "2026-07-07T17:12:11+0900", "loadBalancerName": "lb-test-01", "loadBalancerDomain": "lb-test-01-41112223-16dd7a5738c1.kr.lb.naverncp.com", "loadBalancerIpList": [], "loadBalancerType": { "code": "APPLICATION", "codeName": "Application Load Balancer" }, "loadBalancerNetworkType": { "code": "PRIVATE", "codeName": "Private" }, "throughputType": { "code": "SMALL", "codeName": "Small" }, "idleTimeout": 60, "vpcNo": "12345678", "regionCode": "KR", "accessLogUseYn": "N", "subnetNoList": [ "23456790" ], "loadBalancerSubnetList": [ { "zoneCode": "KR-1", "subnetNo": "23456790", "publicIpInstanceNo": "" } ], "loadBalancerListenerNoList": [ "60001111" ] } ], "requestId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890", "returnCode": "0", "returnMessage": "success" } } ```