Quick Config

Scenarios

DDS supports both yearly/monthly and pay-per-use billing modes. This section describes how to buy a replica set instance in Quick Config mode on the console. Quick Config provides commonly recommended configurations, allowing you to buy a replica set instance within several minutes.

Prerequisites

• You have registered a Huawei ID and enabled Huawei Cloud services.

Procedure

1. Go to the Quick Config page.
2. On the displayed page, select a billing mode and configure information about your DB instance. Then, click Next.
   Figure 1 Basic configurations
   

   Table 1 Basic configurations

   Parameter	Description
   Billing Mode	Select a billing mode, Yearly/Monthly or Pay-per-use. For yearly/monthly instances Specify Required Duration, and the system deducts the fees incurred from your account based on the service price. If you do not expect to continue using the instance much after it expires, you can change the billing mode from yearly/monthly to pay-per-use. For details, see Yearly/Monthly to Pay-per-Use. NOTE: Instances billed on a yearly/monthly basis cannot be deleted. They can only be unsubscribed from. For details, see Unsubscribing from a Yearly/Monthly Instance. For pay-per-use instances You are billed for usage based on how much time the service is in use. If you expect to use the service extensively over a long period of time, you can change its billing mode from pay-per-use to yearly/monthly to reduce costs. For details, see Pay-per-Use to Yearly/Monthly.
   Region	The region where the resource is located. 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 purchased. Exercise caution when selecting a region.
   Project	The project corresponds to the current region and can be changed.
   AZ	An AZ is a physical region where resources have independent power supplies and networks. AZs are physically isolated but interconnected through an internal network. Instances can be deployed in a single AZ or three AZs. 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 primary, secondary, and hidden nodes are evenly distributed across three AZs. NOTE: The 3-AZ deployment is not available in all regions. If the 3-AZ option is not displayed on the page for you to buy an instance, try a different region.
   DB Instance Type	Select Replica set. A replica set consists of the primary node, secondary node, and hidden node. If a primary node goes down or becomes faulty, a secondary node is automatically assigned to the primary role and continues normal operation. If a secondary node is unavailable, a hidden node will take the role of the secondary to ensure high availability.
   Compatible MongoDB Version	5.0 4.4 4.2 4.0 3.4
   CPU Type	DDS supports x86 and Kunpeng CPU architectures. NOTE: This parameter is available only for MongoDB 4.0 and 3.4. You do not need to set this parameter for other versions. The default value is x86. x86 x86 CPUs use the Complex Instruction Set Computing (CISC) instruction set. Each instruction can be used to execute low-level hardware operations. CISC instructions vary in length, and tend to be complicated and slow compared to Reduced Instruction Set Computing (RISC). Kunpeng The Kunpeng CPU architecture uses RISC. The RISC instruction set is smaller and faster than CISC, thanks to the simplified architecture. Kunpeng CPUs also offer a better balance between power and performance than x86. Kunpeng CPUs feature high density, low power consumption, and excellent cost-effectiveness, making them ideal for heavy-load applications.
   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. It is also an optimal choice for medium- and heavy-load enterprise applications.
   Recommended Specifications	Currently, medium- and lightweight database specifications and customized specifications are supported. NOTE: The storage space ranges from 10 GB to 5,000 GB.

   Figure 2 Network, Required Duration, and Quantity
   

   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 Creating a VPC with a Subnet in Virtual Private Cloud User Guide. For details about the constraints on the use of VPCs, see Connection Methods. If there are no VPCs available, DDS creates one for you by default. NOTE: After the DDS instance is created, the VPC cannot be changed.
   Enterprise Project	This parameter is only available to enterprise users. To use it, submit a service ticket. An enterprise project allows you to group cloud resources under specific projects, making it easier to manage cloud resources and users. Select an enterprise project from the drop-down list. The default project is default. For details, see Project Management in Enterprise Management User Guide. To customize an enterprise project, click Enterprise in the upper right corner of the console. The Enterprise Management page is displayed. For details, see Creating an Enterprise Project in Enterprise Management User Guide.

   Table 3 Required duration and quantity

   Parameter	Description
   Required Duration	The system will automatically calculate the fee based on the validity period you have selected.
   Auto-renew	By default, this option is not selected. If you select this option, the auto-renewal cycle is determined by the selected required duration.
   Quantity	The purchase quantity depends on the replica set instance quota. If your current quota does not allow you to purchase the required number of instances, you can apply for increasing the quota as prompted. Yearly/Monthly instances that were purchased in batches have the same specifications except for the instance name and ID.

3. On the displayed page, confirm the instance details.
   • For yearly/monthly instances
     • If you need to modify the specifications, click Previous to return to the previous page.
     • If you do not need to modify the specifications, read and agree to the service agreement and click Pay Now to go to the payment page and complete the payment.
   • For pay-per-use instances
     • If you need to modify the specifications, click Previous to return to the previous page.
     • If you do not need to modify the specifications, read and agree to the service agreement and click Submit to start creating the instance.

4. Click Back to Instance List. 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.

Follow-up Operations

• After the instance is created, you can add a description to it. For details, see Changing an Instance Name.
• The default database port is 8635. You can change it after the instance is created. To enhance data and instance security, change the database port immediately after the instance is created. For details, see Changing a Database Port.

FAQs

How Do I Select Instance Specifications and Nodes?

What Precautions Should Be Taken When Using DDS?

Why Is an Instance Not Displayed on the Console After It Is Created?

Related APIs