The primary availability zone of the instance, for example: ap-guangzhou-3. If needed to support multiple AZs, add primary and secondary AZ information in the DBNodeSet.N field.
AZ information can be obtained by calling the DescribeZones api and checking the Zone field in the returned value.

Purchasable specification code. Obtain this parameter by calling the SpecCode field in the return value of DescribeClasses.

Instance disk capacity size, unit: GB. The step length for parameter settings is 10.

Number of instances to purchase, value ranges from 1 to 10. Single transaction supports a maximum quantity of 10. If exceeding this quantity, multiple calls can be performed to purchase.

Purchase duration, unit: month.

Instance character set, which currently supports only:

Username of the instance root account. Specific specifications are as follows:

Password for the instance root account username, with a length of 8-32 characters. It is recommended to use a password of more than 12 characters and it cannot start with "/".
Must contain the following four character types:

PostgreSQL major version number (this parameter is currently required). Version information can be obtained from DescribeDBVersions. Currently supports major versions 10, 11, 12, 13, 14, and 15. For details, see kernel version overview.
When this parameter is entered, an instance running the latest kernel version of the latest minor version will be created based on this major version number.

PostgreSQL community major version + minor version number.
It's generally not recommended to pass in this parameter. If needed, only the latest minor version number under the current major version can be passed.

PostgreSQL kernel version number.
It's generally not recommended to pass in this parameter. If needed, only the latest kernel version number under the current major version can be passed.

Instance billing type. Currently supports:

VPC ID, such as vpc-xxxxxxxx (this parameter is currently required). A valid VPC ID can be obtained by logging in to the console to query or by calling the API DescribeVpcEx and acquiring the unVpcId field in the API return.

VPC subnet ID, such as subnet-xxxxxxxx (this parameter is currently required). Effective VPC subnet IDs can be queried by logging in to the console or by calling the API DescribeSubnets and acquiring the unSubnetId field in the API return.

Instance node deployment information. When multi-availability zone deployment is supported, it requires specifying the AZ information for each node.
AZ information can be obtained from the Zone field in the returned value by calling the DescribeZones API.

Auto-renewal flag:

Whether to automatically use a voucher:

Voucher ID list. Currently only support specifying one voucher.

Project ID. The default value is 0, which means it belongs to the default project.

Activity ID.

Instance name only supports Chinese/English/number/"_"/"-" with length less than 60. If no instance name is specified, "unnamed" is displayed by default.

Tag information that should be bound to the instance is empty by default. You can get it by calling DescribeTags and checking the Tags field in the return value.

Security group to which an instance belongs. Obtain this parameter by calling the sgId field in the returned value of DescribeSecurityGroups. If not specified, the default security group is bound.

Whether data transparent encryption is required:

The KeyId of the custom key. If you select custom key encryption, you need to input the KeyId of the custom key. KeyId is the unique identifier of CMK.
For related reference on KeyId creation and retrieval, see Enable Transparent Data Encryption

For regions using the KMS service, KMSRegion is empty by default and the local region KMS is used. If the local region is not supported, select another KMS supported region.
For details about KMSRegion, see enable transparent data encryption

Designate the service cluster for KMS. If KMSClusterId is empty, use the KMS of the Default Cluster. To select the specified KMS cluster, require the input of KMSClusterId. For details about KMSClusterId, see enable transparent data encryption.

Database engine, support:

Configuration information for the database engine. The configuration format is as follows:
{"$key1":"$value1", "$key2":"$value2"}
Supported engines:
mssql_compatible engine:

Primary-standby sync mode, supports:

Whether required to support Ipv6:

Whether to enable deletion protection for the instance: true-enable deletion protection; false-disable deletion protection.

Instance storage type. Available values: PHYSICAL_LOCAL_SSD: LOCAL SSD hard disk of PHYSICAL machine; CLOUD_PREMIUM: high-performance CLOUD block storage; CLOUD_SSD: SSD CLOUD disk; CLOUD_HSSD: enhanced SSD CLOUD disk.

Order number list. Each instance corresponds to an order number.

Frozen transaction ID.

ID set of successfully created instances. Return value is available only in pay scenarios.