--- title: "Cloud DB for MongoDB prerequisites" slug: "clouddbformongodb-spec" tags: ["Cloud DB for MongoDB", "VPC"] updated: 2026-09-17T09:37:44Z published: 2026-09-17T09:37:44Z canonical: "guide.ncloud-docs.com/clouddbformongodb-spec" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt > Use this file to discover all available pages before exploring further. # Cloud DB for MongoDB prerequisites Available in VPC View supported environments, server specifications, service limits, etc., for best usage of Cloud DB for MongoDB. ## Cloud environment specifications Cloud environment specifications supported by Cloud DB for MongoDB are described as follows: | Item | Specifications | | --- | --- | | Region (zone) | Korea, Japan, Singapore | | Classic | Not supported | | VPC | Supported | | Languages | Korean, English, and Japanese | Note For more information on the VPC environment, see [Service introduction](https://www.ncloud.com/product/networking/vpc) on the NAVER Cloud Platform portal, and for more information on whether the VPC environments are supported for each service, see [Ncloud user environment guide](/docs/en/environment-environment-1-1). ## Server specifications For NAVER Cloud Platform's Cloud DB for MongoDB, you can flexibly select from various types of server type and use them according to your service size. For server specifications supported by Cloud DB for MongoDB, see [**Services > Database > Cloud DB for MongoDB**](https://www.ncloud.com/product/database/cloudDbMongoDB) in the portal. ### Service limits when changing server specifications The type of an operational MongoDB Server that has been created and is in operation cannot be changed, but the available memory size can be changed at any time using the **Change DB specifications** feature in the console **DB Server** menu. For the upgrade method, see [DB Server](/docs/en/database-database-11-3#db-%EC%8A%A4%ED%8E%99-%EB%B3%80%EA%B2%BD). However, a few service limits exist when changing the server specifications. You need to fully understand these restrictions before changing the server specifications. The service limits are as follows: - They can only be changed within the same type. - They can only be changed to a larger cache memory size type (higher specifications) due to the in-memory characteristics. - In a single DB service, the servers with the same cluster role are all changed to the same specifications. - The server restarts upon completion of the change. Therefore, the service may possibly be affected. - The cluster type may not be changed. Use the backup and recovery feature if you need to change the cluster type. The data continuity is guaranteed as the data in memory is saved to a disk when the server specifications are changed. However, once the server specifications change is complete, we recommend checking the data status using the `dbsize` command. ## Server redundancy configuration Cloud DB for MongoDB supports the high availability (HA) feature. Cloud DB for MongoDB creates a Primary DB Server and a Secondary DB Server. It provides a feature that automatically Fails over to the Secondary when the Primary fails. According to the internal algorithm of MongoDB, a new Primary server is selected among Secondary servers. When creating the MongoDB Server from the NAVER Cloud Platform console, you can select the cluster type. The server configuration will then change according to the selected cluster type. The following describes the server configuration by cluster type. | Cluster type | Redundancy configuration | Number of created servers (units) | Composition | | --- | --- | --- | --- | | Stand-alone | X | 1 | Standalone | | Single Replica Set | O | 3 ~ 7 | Primary, Secondary, Arbiter | | Sharding | O | Mongos : 2 ~ 5 Config : 3 Shard: 2 or more Number of Members per Shard (Replica Set): 3 to 7 Number of Arbiters per Shard (Replica Set): 0 to 1 | Mongos, Primary, Secondary, Arbiter | ## Specifications of MongoDB The specifications of MongoDB offered by Cloud DB for MongoDB are as follows: - Latest versions provided in accordance with the MongoDB lifecycle - Can be selected between Community Edition and Enterprise Edition - WiredTiger storage engine supported - If you need other storage engines, you need to directly install MongoDB on a separate VM to use it. NAVER Cloud Platform does not provide general installation-type MongoDB ## Pricing information Cloud DB for MongoDB uses a pay-as-you-go pricing plan. For detailed description of Cloud DB for MongoDB's pricing standard, see **Portal > Services > Database > Cloud DB for MongoDB**. - [**Portal > Service > Database > Cloud DB for MongoDB**](https://www.ncloud.com/product/database/cloudDbMongoDB)