Quick Config

Precautions

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a region and a project.
3. Click Service List. Under Database, click Document Database Service to go to the DDS console.
4. On the Instances page, click Create DB Instance. The Quick Config page is displayed by default.
5. Specify instance details and click Create Now.

   Table 1 Basic configurations

   Parameter	Description
   Region	The region where the resource is located. For details, see Region and AZ. NOTE: Instances deployed in different regions cannot communicate with each other through a private network, and you cannot change the region of an instance once it is created. Exercise caution when selecting a region.
   AZ	An AZ is a part of a region with its own independent power supply and network. AZs are physically isolated but can communicate through internal network connections. If your service requires low network latency between instances, you deploy the components of the instance in the same AZ. If you select a single AZ to deploy your instance, anti-affinity deployment is used by default. With an anti-affinity deployment, your primary, secondary, and hidden nodes are deployed on different physical machines for high availability. If you want to deploy an instance across AZs for disaster recovery, select three AZs. In this deployment mode, the dds mongos, shard, and config nodes are evenly distributed across the three AZs.
   DB Instance Type	Select Cluster. A cluster instance includes three types of nodes: dds mongos, shard, and config. Each shard and config is a three-node replica set to ensure high availability.
   Compatible MongoDB Version	5.0 4.4 4.2 4.0 3.4
   Specifications	With an x86 architecture, you have the following options: General-purpose (s6): S6 instances are suitable for applications that require moderate performance generally but occasional bursts of high performance, such as light-workload web servers, enterprise R&D and testing environments, and low- and medium-performance databases. Enhanced II (c6): C6 instances have multiple technologies optimized to provide stable powerful compute performance. 25 GE intelligent high-speed NICs are used to provide ultra-high bandwidth and throughput, making it an excellent choice for heavy-load scenarios. It is suitable for websites, web applications, general databases, and cache servers that have higher performance requirements for compute and network resources; and medium- and heavy-load enterprise applications.
   dds mongos Node Class	For details about the dds mongos CPU and memory, see Cluster. You can change the class of an instance after it is created. For details, see Changing a Cluster Instance Class.
   dds mongos Nodes	The value ranges from 2 to 32. You can add nodes to an instance after it is created if necessary. For details, see Changing Cluster Instance Nodes.
   shard Node Class	For details about the shard CPU and memory, see Cluster. The shard node stores user data but cannot be accessed directly. You can change the class of an instance after it is created. For details, see Changing a Cluster Instance Class.
   shard Storage Space	The minimum storage space is 10 GB. If a shard node has fewer than 8 vCPUs, the maximum storage that can be scaled up to is 5,000 GB. If a shard node has 8 or more vCPUs, the maximum storage that can be scaled up to is 10,000 GB. The storage space must be a multiple of 10. You can scale up an instance after it is created. For details, see Scaling Up a Cluster Instance.
   shard Nodes	The value ranges from 2 to 32. You can add nodes to an instance after it is created if necessary. For details, see Changing Cluster Instance Nodes.
   config Node Class	The CPU and memory of a config node. The config node stores instance configurations but cannot be accessed directly. For details, see Cluster.
   config Storage Space	Based on the functions and minimum requirements of the config node, the storage space of the config node is set to 20 GB by default. You cannot scale up the storage of the node after it is created.

   Table 2 Network settings

   Parameter	Description
   VPC	The VPC where your DB instances are located. A VPC isolates networks for different services. It allows you to easily manage and configure private networks and change network configurations. You need to create or select the required VPC. For details, see in the Virtual Private Cloud User Guide. For details about the constraints on the use of VPCs, see Connection Methods. NOTE: After the DDS instance is created, the VPC cannot be changed.
   Enterprise Project	Only enterprise users can use this function. To use this function, contact customer service. An enterprise project is a cloud resource management mode, in which cloud resources and members are centrally managed by project. Select an enterprise project from the drop-down list. The default project is default. For more information about enterprise project, see in Enterprise Management User Guide.

   Table 3 Default configuration items

   Specifications	Value	Editable After Instance Creation
   DB Instance Name	dds-6c01	Yes
   Storage Engine	WiredTiger	No
   SSL	Disabled	Yes
   Database Port	8635	Yes
   Cluster Parameter Template	Default-DDS-4.0-Mongos Default-DDS-4.0-Shard Default-DDS-4.0-Config	Yes
   Tags	Not configured	Yes
   Advanced Settings	Not configured	Yes

   Note

   • Some settings are configured by default during purchase, but can still be modified after the instance is created. If you do not see a setting listed for your instance, click Custom Config.
   • Instance performance depends on the specifications you select during creation. The hardware configuration items that can be selected include the node class and storage space.

6. On the displayed page, confirm the instance details.
   • If you need to modify the specifications, click Previous to return to the previous page.
   • If you do not need to modify the specifications, click Submit to start creating the instance.

7. After a DDS instance is created, you can view and manage it on the Instances page.
   • When an instance is being created, the status displayed in the Status column is Creating. This process takes about 15 minutes. After the creation is complete, the status changes to Available.
   • DDS enables the automated backup policy by default. After an instance is created, you can modify or disable the automated backup policy. An automated full backup is immediately triggered after the creation of an instance.