Network type of the Cloud Load Balancer instance:
OPEN: public network attribute, INTERNAL: private network attribute.

Type of the Cloud Load Balancer instance. 1: Common CLB instance. Currently only support passing in 1.

The name of the Cloud Load Balancer instance is effective only when creating an instance. Rule: 1-80 characters in internationally compatible languages such as English letters, Chinese characters, digits, connecting line "-", underscore "_", and other common characters (Unicode supplementary characters such as emoji and rare Chinese characters are forbidden). Note: If the name is identical to an existing Cloud Load Balancer instance name in the system, the system will automatically generate the name for the created CLB instance.

When you purchase a private network CLB instance in a VPC, the subnet ID must be specified. The VIP of the private network CLB instance is generated in this subnet.
This parameter is required when you create a private network CLB instance or a CLB instance of the IPv6FullChain version.
It cannot be specified when you create a public network IPv4 CLB instance.

Applicable only to public network CLB. IP version, valid values: IPV4, IPV6, IPv6FullChain, case-insensitive, default value IPV4. Description: A value of IPV6 means IPV6 NAT64 version; a value of IPv6FullChain means IPv6 version.

Count of Cloud Load Balancers to create, default value is 1. The count must not exceed the maximum value allowed for the account, with a default creation maximum value of 20.

Applicable only to public network load balancing with IP version IPv4. Sets the primary AZ ID for cross-AZ disaster recovery. Both AZ ID and name are supported, such as 100001 or ap-guangzhou-1.
Note: The primary AZ loads traffic. The secondary AZ does not load traffic by default and is used only if the primary AZ becomes unavailable.

Applicable only to public network load balancing with IP version IPv4. AZ ID, availability zone id and name are supported. Specify availability zone to create a CLB instance. For example: 100001 or ap-guangzhou-1.

Maximum outbound bandwidth under the network billing mode. It applies only to LCU-supported instances of the private network type and all instances of the public network type.

Applicable only to public network CLB. Currently, only Guangzhou, Shanghai, Nanjing, Jinan, Hangzhou, Fuzhou, Beijing, Shijiazhuang, Wuhan, Changsha, Chengdu, and Chongqing regions support static single-line IP type. If you need to experience it, contact business manager to submit a request. After approval, you can select operator type of China Mobile (CMCC), China Unicom (CUCC), or China Telecom (CTCC). Only can be used network billing mode BANDWIDTH_PACKAGE. If this parameter is not specified, use BGP by default. You can query ISPs supported in a region via DescribeResources api.

When purchasing a Cloud Load Balancer, you can tag it with up to 20 tag key-value pairs.

Specify VIP to apply for Cloud Load Balancer. This parameter is optional. If this parameter is not specified, VIP is automatically assigned. This parameter is supported for IPv4 and IPv6 types but not for IPv6 NAT64 type.
Note: When creating a private network instance or a public IPv6 BGP instance with a designated VIP, creation fails if the VIP is not within the IP range of the specified VPC subnet or if the VIP is already occupied.

Bandwidth package ID, which can be obtained through the DescribeBandwidthPackages API. When this parameter is specified, the network billing mode (InternetAccessible.InternetChargeType) supports only billing by bandwidth package (BANDWIDTH_PACKAGE), and the bandwidth package attributes determine the settlement method. For IPv6 Cloud Load Balancer instances purchased by non-promoted users with a non-BGP operator type, specifying bandwidth package ID is unsupported.

Dedicated instance info. This parameter is required when creating a private network CLB instance of exclusive type.

Performance capacity specification.

• If you need to create an LCU-supported instance, this parameter is required. Valid values:
  • clb.c2.medium: Standard
  • clb.c3.small: Advanced 1
  • clb.c3.medium: Advanced 2
  • clb.c4.small: Super Large 1
  • clb.c4.medium: Super Large 2
  • clb.c4.large: Super Large 3
  • clb.c4.xlarge: Super Large 4
• For Chinese site users who need to create a shared instance, this parameter is not required. International site users will purchase a standard instance by default if this parameter is not passed.

Cluster ID. This cluster identifier is used for configuring a public cloud exclusive cluster or a local dedicated cluster. To apply for a public cloud exclusive cluster, submit a ticket. For local dedicated clusters, refer to the description in Local Dedicated Cluster.

String used to ensure request idempotency. This string is generated by the customer and must be unique among different requests, with a maximum value of 64 ASCII characters. If not specified, request idempotency cannot be guaranteed.

Whether binding cross-regional or cross-Vpc IP addresses is supported.

Enable the cross-regional or cross-Vpc IP binding feature to create a SnatIp.

Tag of the Stgw exclusive cluster.

Applicable only to public network load balancing with IP version IPv4. Sets the secondary AZ ID for cross-AZ disaster recovery. AZ ID and name are supported, such as 100001 or ap-guangzhou-1.
Note: The secondary AZ is the availability zone that needs to carry traffic after primary availability zone failure. Query a region's list of primary/secondary AZs via the DescribeResources API. [If you need to trial the feature, submit a ticket application via Work Order]

The unique ID of EIP can be accessed through the DescribeAddresses api for the query. Example: eip-qhx8udkc, applicable only to bind EIP for private network CLB.

Allow CLB traffic to the Target. Enable (true): verify security groups on CLB; deny CLB traffic to the Target (false): verify security groups on both CLB and backend instances. IPv6 CLB security group default permit, this parameter is not required.

Create a domain-name based CLB.

Network outbound

Prepaid billing attributes of the CLB instance

Billing type of the CLB instance. Valid values: POSTPAID_BY_HOUR and PREPAID. Default value: POSTPAID_BY_HOUR.

Enumeration values:

• POSTPAID_BY_HOUR: Pay-As-You-Go
• PREPAID: Monthly Subscription

L7 access log topic ID

Whether layer-7 advanced routing is enabled

Availability zone affinity info

An array consisting of the unique IDs of Cloud Load Balancer instances.
In certain scenarios, such as delay in creation, this field may return null. At this point, you can query the created resource ID through the DescribeTaskStatus API using the RequestId or DealName parameter returned by the API.

Order number.