Buying and Connecting to a Cluster Instance

Operation Process

Preparations

1. Sign up for a HUAWEI ID and enable Huawei Cloud services.
2. For fine-grained permissions management on Huawei Cloud resources, use Identity and Access Management (IAM) to create a user or user group and grant it specific operation permissions. For details, see Creating a User and Granting Permissions.

Video Tutorial

This video shows you how to buy a cluster instance on the console and connect to it.

Step 1: Quickly Buy a Cluster Instance

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	Example Value	Description
   Billing Mode	Pay-per-use	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	CN-Hong Kong	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	default	The project corresponds to the current region and can be changed.
   AZ	az1	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. Instances can be deployed in a single AZ or 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. 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	Cluster	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	4.4	The database version.
   CPU Type	x86	DDS supports x86 and Kunpeng CPU architectures.
   Specifications	Enhanced II	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. For details about the supported instance specifications, see Cluster Instance Specifications.
   dds mongos Node Class	2 vCPUs | 8 GB	For details about the dds mongos CPU and memory, see Cluster Instance Specifications. You can change the class of an instance after it is created. For details, see Changing the Instance Class.
   dds mongos Nodes	2	The value ranges from 2 to 32. You can add nodes to an instance after it is created if necessary. For details, see Adding Cluster Instance Nodes.
   shard Node Class	4 vCPUs | 16 GB	For details about the shard CPU and memory, see Cluster Instance Specifications. 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 the Instance Class.
   shard Storage Space	100 GB	The value ranges from 10 GB to 5,000 GB and must be a multiple of 10. You can scale up an instance after it is created. For details, see Scaling Up a Cluster Instance. NOTE: If the storage space you purchased exceeds 600 GB and the remaining storage space is 18 GB, the instance becomes Read-only. If the storage space you purchased is less than 600 GB and the storage space usage reaches 97%, the instance becomes Read-only. In these cases, delete unnecessary resources or expand the capacity.
   shard Nodes	2	The value ranges from 2 to 32. You can add nodes to an instance after it is created if necessary. For details, see Adding Cluster Instance Nodes.
   config Node Class	2 vCPUs | 4 GB	For details about the CPU and memory of the config node, see Cluster Instance Specifications. You can change the class of an instance after it is created. For details, see Changing the Instance Class.
   config Storage Space	20 GB	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.

   Figure 2 Network, Required Duration, and Quantity
   

   Table 2 Network settings

   Parameter	Example Value	Description
   VPC	default	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 in the Virtual Private Cloud User Guide. If no VPC is available or has been created, DDS allocates a VPC to you by default. NOTE: After the DDS instance is created, the VPC cannot be changed.
   Enterprise Project	default	This parameter is available only to enterprise users. To use this function, submit a service ticket. 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 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.

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 an automated backup policy by default, but you can disable it after an instance is created. After an instance is created, DDS automatically creates a full backup.

Step 2: Connect to a Cluster Instance Through DAS

Data Admin Service (DAS) enables you to manage DB instances on a web-based console, simplifying database management and improving working efficiency. You can connect to and manage DB instances through DAS. By default, you have the permission required for remote login. It is recommended that you use the DAS service to connect to DB instances. DAS is secure and convenient.

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a region and a project.

   If you want compute and network resources dedicated to your exclusive use, enable a DeC and apply for DCC resources. After enabling a DeC, you can select the DeC region and project.

3. Click in the upper left corner of the page and choose Databases > Document Database Service.
4. On the Instances page, locate the target DB instance and click Log In in the Operation column.

   Alternatively, click the target DB instance on the Instances page. On the displayed Basic Information page, click Log In in the upper right corner of the page.

5. In the Instance Login dialog box, enter the correct information and click Log In to access and manage your database.
6. After the login is successful, you can perform operations such as creating a database, managing accounts, and managing databases.

   For details, see Database Management.