ApsaraDB for MongoDB sharded cluster instances consist of three node types: Mongos, Shard, and ConfigServer. This page lists available specifications for each node type across disk-based and local disk-based instance categories.
The memory shown for each instance type reflects the total allocated memory, including memory used by MongoDB management services, database services, and the operating system, as well as memory reserved for BIOS, kernel, and hypervisor. Available memory is less than the total.
Some instance types were upgraded on May 14, 2024. If the maximum connections for your instance do not match the values below, restart the instance for the upgrade to take effect. For more information, see Notification: Maximum connections upgraded for some ApsaraDB for MongoDB instance types .
A single collection file cannot exceed 16 TB. Exceeding this limit makes the instance unavailable.
Cloud Disk Edition
The following database versions are supported:
-
MongoDB 8.0
-
MongoDB 7.0
-
MongoDB 6.0
-
MongoDB 5.0
-
MongoDB 4.4
-
MongoDB 4.2
For more information about the maximum IOPS and throughput of different disk types, see ESSD disks and ESSD AutoPL disks.
|
Node type |
Instance type family |
Specifications |
Instance type code |
Maximum connections |
Maximum IOPS |
Maximum throughput (MB/s) |
Storage space |
|
Mongos |
Dedicated disk-based |
2 vCPU, 8 GB |
mdb.shard.4x.large.d |
5000 |
N/A |
N/A |
N/A |
|
2 vCPU, 16 GB |
mdb.shard.8x.large.d |
8000 |
|||||
|
4 vCPU, 8 GB |
mdb.shard.2x.xlarge.d |
8000 |
|||||
|
4 vCPU, 16 GB |
mdb.shard.4x.xlarge.d |
8000 |
|||||
|
4 vCPU, 32 GB |
mdb.shard.8x.xlarge.d |
12000 |
|||||
|
8 vCPU, 16 GB |
mdb.shard.2x.2xlarge.d |
12000 |
|||||
|
8 vCPU, 32 GB |
mdb.shard.4x.2xlarge.d |
16000 |
|||||
|
8 vCPU, 64 GB |
mdb.shard.8x.2xlarge.d |
16000 |
|||||
|
16 vCPU, 32 GB |
mdb.shard.2x.4xlarge.d |
16000 |
|||||
|
16 vCPU, 64 GB |
mdb.shard.4x.4xlarge.d |
32000 |
|||||
|
16 vCPU, 128 GB |
mdb.shard.8x.4xlarge.d |
32000 |
|||||
|
32 vCPU, 64 GB |
mdb.shard.2x.8xlarge.d |
32000 |
|||||
|
32 vCPU, 128 GB |
mdb.shard.4x.8xlarge.d |
96000 |
|||||
|
32 vCPU, 256 GB |
mdb.shard.8x.8xlarge.d |
96000 |
|||||
|
General-purpose disk-based |
2 vCPU, 4 GB |
mdb.shard.2x.large.c |
3000 |
||||
|
4 vCPU, 8 GB |
mdb.shard.2x.xlarge.c |
6000 |
|||||
|
8 vCPU, 16 GB |
mdb.shard.2x.2xlarge.c |
12000 |
|||||
|
16 vCPU, 32 GB |
mdb.shard.2x.4xlarge.c |
16000 |
|||||
|
32 vCPU, 64 GB |
mdb.shard.2x.8xlarge.c |
32000 |
|||||
|
Shard |
Dedicated disk-based |
2 vCPU, 8 GB |
mdb.shard.4x.large.d |
5000 |
min{1800 + 50 × Storage space, 10000, Maximum IOPS of the selected disk type} |
min{120 + 0.5 × Storage space, 128, Maximum throughput of the selected disk type} |
|
|
2 vCPU, 16 GB |
mdb.shard.8x.large.d |
8000 |
|||||
|
4 vCPU, 8 GB |
mdb.shard.2x.xlarge.d |
8000 |
min{1800 + 50 × Storage space, 20000, Maximum IOPS of the selected disk type} |
min{120 + 0.5 × Storage space, 192, Maximum throughput of the selected disk type} |
|||
|
4 vCPU, 16 GB |
mdb.shard.4x.xlarge.d |
8000 |
|||||
|
4 vCPU, 32 GB |
mdb.shard.8x.xlarge.d |
12000 |
|||||
|
8 vCPU, 16 GB |
mdb.shard.2x.2xlarge.d |
12000 |
min{1800 + 50 × Storage space, 25000, Maximum IOPS of the selected disk type} |
min{120 + 0.5 × Storage space, 256, Maximum throughput of the selected disk type} |
|||
|
8 vCPU, 32 GB |
mdb.shard.4x.2xlarge.d |
16000 |
|||||
|
8 vCPU, 64 GB |
mdb.shard.8x.2xlarge.d |
16000 |
|||||
|
16 vCPU, 32 GB |
mdb.shard.2x.4xlarge.d |
16000 |
min{1800 + 50 × Storage space, 40000, Maximum IOPS of the selected disk type} |
min{120 + 0.5 × Storage space, 384, Maximum throughput of the selected disk type} |
|||
|
16 vCPU, 64 GB |
mdb.shard.4x.4xlarge.d |
32000 |
|||||
|
16 vCPU, 128 GB |
mdb.shard.8x.4xlarge.d |
32000 |
|||||
|
32 vCPU, 64 GB |
mdb.shard.2x.8xlarge.d |
32000 |
min{1800 + 50 × Storage space, 60000, Maximum IOPS of the selected disk type} |
min{120 + 0.5 × Storage space, 640, Maximum throughput of the selected disk type} |
|||
|
32 vCPU, 128 GB |
mdb.shard.4x.8xlarge.d |
96000 |
|||||
|
32 vCPU, 256 GB |
mdb.shard.8x.8xlarge.d |
96000 |
|||||
|
64 vCPU, 128 GB |
mdb.shard.2x.16xlarge.d |
96000 |
min{1800 + 50 × Storage space, 300000, Maximum IOPS of the selected disk type} |
min{120 + 0.5 × Storage space, 2048, Maximum throughput of the selected disk type} |
|||
|
64 vCPU, 256 GB |
mdb.shard.4x.16xlarge.d |
128000 |
|||||
|
64 vCPU, 512 GB |
mdb.shard.8x.16xlarge.d |
128000 |
|||||
|
General-purpose disk-based |
2 vCPU, 4 GB |
mdb.shard.2x.large.c |
3000 |
min{1800 + 50 × Storage space, 10500, Maximum IOPS of the selected disk type} |
min{120 + 0.5 × Storage space, 128, Maximum throughput of the selected disk type} |
||
|
2 vCPU, 8 GB |
mdb.shard.4x.large.c |
3000 |
|||||
|
4 vCPU, 8 GB |
mdb.shard.2x.xlarge.c |
6000 |
min{1800 + 50 × Storage space, 21000, Maximum IOPS of the selected disk type} |
min{120 + 0.5 × Storage space, 192, Maximum throughput of the selected disk type} |
|||
|
4 vCPU, 16 GB |
mdb.shard.4x.xlarge.c |
6000 |
|||||
|
8 vCPU, 16 GB |
mdb.shard.2x.2xlarge.c |
12000 |
min{1800 + 50 × Storage space, 26250, Maximum IOPS of the selected disk type} |
min{120 + 0.5 × Storage space, 256, Maximum throughput of the selected disk type} |
|||
|
8 vCPU, 32 GB |
mdb.shard.4x.2xlarge.c |
16000 |
|||||
|
16 vCPU, 32 GB |
mdb.shard.2x.4xlarge.c |
16000 |
min{1800 + 50 × Storage space, 42000, Maximum IOPS of the selected disk type} |
min{120 + 0.5 × Storage space, 384, Maximum throughput of the selected disk type} |
|||
|
16 vCPU, 64 GB |
mdb.shard.4x.4xlarge.c |
32000 |
|||||
|
32 vCPU, 64 GB |
mdb.shard.2x.8xlarge.c |
32000 |
min{1800 + 50 × Storage space, 50000, Maximum IOPS of the selected disk type} |
min{120 + 0.5 × Storage space, 640, Maximum throughput of the selected disk type} |
|||
|
ConfigServer |
Dedicated Cloud Disk |
4 vCPU, 8 GB |
mdb.shard.2x.xlarge.d |
8000 |
min{1800 + 50 × Storage space, 20000, Maximum IOPS of the selected disk type} |
min{120 + 0.5 × Storage space, 192, Maximum throughput of the selected disk type} |
|
|
4 vCPU, 16 GB |
mdb.shard.4x.xlarge.d |
8000 |
|||||
|
8 vCPU, 16 GB |
mdb.shard.2x.2xlarge.d |
12000 |
min{1800 + 50 × Storage space, 25000, Maximum IOPS of the selected disk type} |
min{120 + 0.5 × Storage space, 256, Maximum throughput of the selected disk type} |
|||
|
8 vCPU, 32 GB |
mdb.shard.4x.2xlarge.d |
16000 |
|||||
|
16 vCPU, 32 GB |
mdb.shard.2x.4xlarge.d |
16000 |
min{1800 + 50 × Storage space, 40000, Maximum IOPS of the selected disk type} |
min{120 + 0.5 × Storage space, 384, Maximum throughput of the selected disk type} |
|||
|
16 vCPU, 64 GB |
mdb.shard.4x.4xlarge.d |
32000 |
|||||
|
General-purpose disk-based |
2 vCPU, 4 GB |
mdb.shard.2x.large.c |
3000 |
min{1800 + 50 × Storage space, 10500, Maximum IOPS of the selected disk type} |
min{120 + 0.5 × Storage space, 128, Maximum throughput of the selected disk type} |
||
|
4 vCPU, 8 GB |
mdb.shard.2x.xlarge.c |
6000 |
min{1800 + 50 × Storage space, 21000, Maximum IOPS of the selected disk type} |
min{120 + 0.5 × Storage space, 192, Maximum throughput of the selected disk type} |
|||
|
8 vCPU, 16 GB |
mdb.shard.2x.2xlarge.c |
12000 |
min{1800 + 50 × Storage space, 26250, Maximum IOPS of the selected disk type} |
min{120 + 0.5 × Storage space, 256, Maximum throughput of the selected disk type} |
|||
|
16 vCPU, 32 GB |
mdb.shard.2x.4xlarge.c |
16000 |
min{1800 + 50 × Storage space, 42000, Maximum IOPS of the selected disk type} |
min{120 + 0.5 × Storage space, 384, Maximum throughput of the selected disk type} |
The 64 vCPU/128 GB, 64 vCPU/256 GB, and 64 vCPU/512 GB Dedicated disk-based instance types for shard nodes are available only in the following regions and zones:
-
China (Hangzhou): Zones G, H, and I.
-
China (Shanghai): Zones B, G, and L.
-
China (Beijing): Zones F, H, L, and K.
-
China (Zhangjiakou): Zones A and C.
-
China (Shenzhen): Zones E, D, and F.
General-purpose disk-based instances are available in the following regions and zones:
-
China (Hangzhou): Zones K and J.
-
China (Shanghai): Zones B, L , M , and N.
-
China (Beijing): Zones I, J, L, F, H, and K.
-
China (Shenzhen): Zone D
-
China (Hong Kong): Zones B and C.
-
Singapore: Zone A.
-
If you select multi-zone deployment when you create an instance, confirm that the destination region supports the selected instance type.
-
Disk encryption is not supported for General-purpose disk-based instance types.
-
General-purpose disk-based instances are not available in all regions. If you cannot find the required instance types in the console for a specific region, you can submit a ticket to request access.
Local disk-based instances
Local disk-based instances use physical disks attached to the host and support MongoDB 4.2, 4.0, and 3.4 (discontinued).
Mongos node specifications
General-purpose local disk-based
| Specifications | Specification code | Maximum connections (per node) |
|---|---|---|
| 1 vCPU, 2 GB | dds.mongos.mid | 1,000 |
| 2 vCPU, 4 GB | dds.mongos.standard | 3,000 |
| 4 vCPU, 8 GB | dds.mongos.large | 6,000 |
| 8 vCPU, 16 GB | dds.mongos.xlarge | 9,000 |
| 8 vCPU, 32 GB | dds.mongos.2xlarge | 16,000 |
| 16 vCPU, 64 GB | dds.mongos.4xlarge | 32,000 |
Shard node specifications
General-purpose local disk-based
| Specifications | Specification code | Maximum connections | Maximum IOPS | Storage space |
|---|---|---|---|---|
| 1 vCPU, 2 GB | dds.shard.mid | 8,000 | 8,000 | 10–2,000 GB (10 GB step) |
| 2 vCPU, 4 GB | dds.shard.standard | 8,000 | 8,000 | 10–2,000 GB (10 GB step) |
| 4 vCPU, 8 GB | dds.shard.large | 8,000 | 8,000 | 10–2,000 GB (10 GB step) |
| 8 vCPU, 16 GB | dds.shard.xlarge | 8,000 | 8,000 | 10–2,000 GB (10 GB step) |
| 8 vCPU, 32 GB | dds.shard.2xlarge | 16,000 | 14,000 | 10–2,000 GB (10 GB step) |
| 16 vCPU, 64 GB | dds.shard.4xlarge | 32,000 | 16,000 | 10–2,000 GB (10 GB step) |
Dedicated local disk-based
| Specifications | Specification code | Maximum connections | Maximum IOPS | Storage space |
|---|---|---|---|---|
| 2 vCPU, 16 GB | dds.shard.sn8.xlarge.3 | 8,000 | 8,000 | 10–250 GB (10 GB step) |
| 4 vCPU, 32 GB | dds.shard.sn8.2xlarge.3 | 8,000 | 9,000 | 10–500 GB (10 GB step) |
| 8 vCPU, 64 GB | dds.shard.sn8.4xlarge.3 | 16,000 | 18,000 | 10–1,000 GB (10 GB step) |
| 16 vCPU, 128 GB | dds.shard.sn8.8xlarge.3 | 32,000 | 36,000 | 10–2,000 GB (10 GB step) |
| 32 vCPU, 256 GB | dds.shard.sn8.16xlarge.3 | 64,000 | 72,000 | 10–3,000 GB (10 GB step) |
ConfigServer node specifications
General-purpose local disk-based
| Specifications | Specification code | Maximum connections | Maximum IOPS | Storage space |
|---|---|---|---|---|
| 1 vCPU, 2 GB | dds.cs.mid | 8,000 | 8,000 | 20–1,270 GB (10 GB step) |
The storage space for a shard node is allocated to each individual node. For example, if the storage for a shard component is 20 GB, each primary node and secondary node in that shard has 20 GB of storage.
To choose storage based on IOPS requirements, see Select storage space based on IOPS .