• Specifies the number of primary and secondary nodes for each replica set during replica set instance creation. Call the DescribeSpecInfo API to obtain the maximum and minimum number of nodes supported for each replica set.
• Specifies the number of primary and secondary nodes for each shard during sharded cluster instance creation. Call the DescribeSpecInfo API to obtain the maximum and minimum number of nodes supported for each shard.

Instance memory size. Unit: GB. Call the DescribeSpecInfo API to obtain specific saleable memory specifications.

Instance disk size. Unit: GB. Call the DescribeSpecInfo API to obtain the maximum and minimum disk sizes corresponding to each CPU specification.

Refers to version information. For supported versions, use the interface DescribeSpecInfo to query.

• MONGO_40_WT: MongoDB 4.0 WiredTiger engine version.
• MONGO_42_WT: MongoDB 4.2 WiredTiger engine version.
• MONGO_44_WT: MongoDB 4.4 WiredTiger engine version.
• MONGO_50_WT: MongoDB 5.0 WiredTiger engine version.
• MONGO_60_WT: MongoDB 6.0 WiredTiger engine version.
• MONGO_70_WT: MongoDB 7.0 WiredTiger engine version.
• MONGO_80_WT: MongoDB 8.0 WiredTiger engine version.

Number of instances. The minimum value is 1, and the maximum value is 30.

AZ information. The input format must be ap-guangzhou-2.

• For details, use the interface DescribeSpecInfo to obtain them.
• This parameter is the primary AZ. If multi-AZ deployment is used, Zone must be one of AvailabilityZoneList.

Specifies the purchase duration during instance purchase. Valid values: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 24, and 36. Unit: months.

Recommended product specification types:

• GE.LD.T1: Local disk (Common I).
• GE.CD.T1: Cloud disk (Common I).

Product allowlist specification types:

• HIO10G: Local disk (High IO 10G).
• HCD: Cloud disk (Cloud disk edition).

Note: Allowlist specification types are under allowlist control. If needed, submit a ticket to apply.

Instance architecture type.

• REPLSET (replica set)
• SHARD (sharded cluster)

• Specifies the number of replica sets during replica set instance creation. This parameter can only be 1.
• Specifies the number of shards during sharded cluster instance creation. Call the DescribeSpecInfo API to query the range of shard quantity. The parameters MinReplicateSetNum and MaxReplicateSetNum in the returned data structure SpecItems correspond to the minimum value and maximum value, respectively.

Project ID.

• If this parameter is not set, the default project is used.
• You can obtain the project ID on the MongoDB console project management page.

VPC ID.

• Only private networks can be configured, and a private network in the same region as the instance must be selected. Log in to the VPC console to obtain a used private network ID.
• After successful instance creation, VPC replacement is allowed. For detailed operations, see Changing the Network.

Subnet ID of the VPC.

• You must specify a subnet within the selected private network. Log in to the VPC console to obtain the subnet ID.
• After the instance is successfully created, replacement of the private network and subnet is allowed. For detailed operations, please refer to Network Change.

Instance password. The requirements are as follows:

• Character count is [8,32].
• Enter characters within [A,Z], [a,z], [0,9].
• Special characters include: exclamation mark "!", at "@", pound sign "#", percent sign "%", caret "^", asterisk "*", brackets "()", underscore "_".
• Cannot set a single letter or number.

Instance tag information.

Auto-renewal flag.

• 0: no auto-renewal.
• 1: auto-renewal.

Indicates whether to automatically select voucher.

• 1: Yes.
• 0: No. Default is 0.

Instance type.

• 1: Formal instance.
• 3: Read-only instance.
• 4: Disaster recovery instance.
• 5: Clone instance. Note: RestoreTime is a required item when you clone an instance.

Parent instance ID.

• When the Clone parameter is 3 or 4, that is, the instance is read-only or a disaster recovery instance, this parameter must be configured.
• Log in to the MongoDB console and copy the parent instance ID in the instance list.

Security group ID. Log in to the security group console to obtain the ID of the security group within the same region as the database instance.

Rollback time of the cloned instance. It is required when the Clone value is 5 or 6. - This parameter is required for cloned instances. Format: 2021-08-13 16:30:00. - Rollback time range: Only data within the last 7 days can be rolled back.

Instance name. Only Chinese, English, digits, underscores (_), and hyphens (-) are supported, with a maximum length of 128 characters. When purchasing database instances in batches, you can efficiently set instance names by using custom pattern strings and automatically ascending numeric suffixes.

• Basic mode: prefix + automatic ascending number (starting from 1 by default). Only a custom instance name prefix is required for lnstanceName. For example, it can be set to cmgo. If the purchase quantity is set to 5, after purchase, the instances will be sequentially named cmgo1, cmgo2, cmgo3, cmgo4, and cmgo5, respectively.
• Custom starting number mode: prefix + {R:x} (x is the custom starting number). InstanceName requires "prefix{R:x}". For example, cmgo{R:3}. If the purchase quantity is set to 5, the instance names will be cmgo3, cmgo4, cmgo5, cmgo6, and cmgo7.
• Composite pattern string: prefix1{R:x} + prefix2{R:y} + ⋯ + fixed suffix, where x and y are the starting numbers for each prefix. InstanceName requires a composite pattern string. For example, cmgo{R:10}_node{R:12}_db. If the batch purchase quantity is set to 5, the instance names will be cmgo10_node12_db, cmgo11_node13_db, cmgo12_node14_db, cmgo13_node15_db, and cmgo14_node16_db.

For cloud database instances in multi-AZ deployment, specify the availability zone list.

• For instances in multi-AZ deployment mode, the Zone parameter specifies the primary AZ, and AvailabilityZoneList specifies all AZs, including the primary AZ. Format: [ap-guangzhou-2,ap-guangzhou-3,ap-guangzhou-4].
• Use the DescribeSpecInfo API to access cloud databases and obtain availability zone information planned for different regions, so that you can assign valid AZs.
• Nodes in multi-AZ deployment can only be deployed in 3 different availability zones. Deploying most nodes of a cluster in the same availability zone is not supported. For example, a 3-node cluster does not support deploying 2 nodes in the same zone.

Number of Mongos node CPU cores. Valid values: 1, 2, 4, 8, and 16. This parameter is required during sharded cluster instance purchase.

Mongos node memory size.

• This parameter is required during sharded cluster instance purchase.
• Unit: GB. Valid values: 2 (for 1 core), 4 (for 2 cores), 8 (for 4 cores), 16 (for 8 cores), and 32 (for 16 cores).

Number of Mongos nodes. This parameter is required during sharded cluster instance purchase.

• For single-AZ deployment instances, the quantity range is [3,32].
• For instances deployed across multiple availability zones, the quantity range is [6,32].

Number of read-only nodes. Value ranges from 0 to 5.

Array of AZs of read-only nodes. This parameter is required for instances in multi-AZ deployment mode when ReadonlyNodeNum is not set to 0.

Availability zone of the Hidden node. To deploy instances across availability zones, you must configure this parameter.

Parameter template ID.

• A parameter template is a collection of preset specific parameters applicable to quick configuration of new MongoDB instances. Proper use of parameter templates can effectively improve database deployment efficiency and operating performance.
• The parameter template ID can be obtained through the DescribeDBInstanceParamTpl API. Please select the parameter template ID corresponding to your instance version and architecture.

Instance CPU core size. Unit: C. Call the DescribeSpecInfo API to obtain specific saleable CPU specifications.
Note: CPU size must be set for common I Instance Type.

Order ID

List of instance created IDs