Service Overview - Huawei Cloud

Document Database Service

Service Overview

Issue 16

Date 2022-06-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2022. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without priorwritten consent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respectiveholders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei andthe customer. All or part of the products, services and features described in this document may not bewithin the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,information, and recommendations in this document are provided "AS IS" without warranties, guaranteesor representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Issue 16 (2022-06-30) Copyright © Huawei Technologies Co., Ltd. i

Contents

1 What Is DDS?............................................................................................................................ 1

2 Advantages............................................................................................................................... 4

3 Comparison Between DDS and On-Premises Databases............................................... 6

4 Typical Application Scenarios............................................................................................... 8

5 Functions and Features........................................................................................................ 10

6 System Architecture..............................................................................................................126.1 Cluster....................................................................................................................................................................................... 126.2 Replica Set............................................................................................................................................................................... 136.3 Single Node.............................................................................................................................................................................15

7 Instances..................................................................................................................................177.1 DB Engines and Versions.................................................................................................................................................... 177.2 Instance Specifications........................................................................................................................................................ 177.2.1 Cluster................................................................................................................................................................................... 177.2.2 Replica Set........................................................................................................................................................................... 287.2.3 Single Node......................................................................................................................................................................... 327.3 Read Replica........................................................................................................................................................................... 37

8 Pricing Details........................................................................................................................ 39

9 Basic Concepts........................................................................................................................429.1 Instance.................................................................................................................................................................................... 429.2 Cluster....................................................................................................................................................................................... 429.3 Database Parameter Template.........................................................................................................................................439.4 Region and AZ....................................................................................................................................................................... 449.5 DB Connections..................................................................................................................................................................... 45

10 Compatibility........................................................................................................................4610.1 Versions.................................................................................................................................................................................. 4610.2 Details.....................................................................................................................................................................................4610.3 Browsers................................................................................................................................................................................ 51

11 Permissions Management................................................................................................. 52

12 Related Services...................................................................................................................62

Document Database ServiceService Overview Contents

Issue 16 (2022-06-30) Copyright © Huawei Technologies Co., Ltd. ii

A Change History...................................................................................................................... 64

Document Database ServiceService Overview Contents

Issue 16 (2022-06-30) Copyright © Huawei Technologies Co., Ltd. iii

1 What Is DDS?

Document Database Service (DDS), compatible with MongoDB, is a secure, highavailability (HA) database service that is reliable, scalable, and easy to use. Itprovides functions such as one-click deployment, elastic capacity expansion,disaster recovery, backup, restoration, monitoring, and alarm reporting.

Before using DDS, you need to be familiar with MongoDB and the MongoDBprotocol. For details, see official documents.

Document Database ServiceService Overview 1 What Is DDS?

Issue 16 (2022-06-30) Copyright © Huawei Technologies Co., Ltd. 1

https://docs.mongodb.com/manual/introduction/

Storage Structure

Figure 1-1 Storage structure

The basic management unit of DDS is an instance. A DDS instance consists ofdatabase, collection, and document.

DDS is fully compatible with the MongoDB protocol, so some terms, datastructures, and basic syntax of DDS are the same as those of MongoDB. Thefollowing table lists the difference between common terms in MongoDB andrelational databases to help you better understand and use DDS.

Table 1-1 Terms

MongoDB Description Relational Database

Database A DDS instance contains multipledatabases, and a databasecontains multiple collections.

Database

Collection A collection is a group ofMongoDB documents.

Table

Document A document is a group of key-value pairs (BSONs) and is themost basic unit in MongoDB.

Row



Data Structure

MongoDB uses JSON-like documents when storing documents in collections. Thefollowing figure compares data structures between RDS and MongoDB, helpingyou have a better understanding of MongoDB concepts.

Figure 1-2 Data structures

Why DDS?

For details, see Advantages and Typical Application Scenarios.

Product Pricing

For details, see Pricing Details.

Compatible DB Engines and Versions

For details about the compatible DB engines and versions, see DB Engines andVersions.

Deployment Suggestions

It is recommended that you consider the following factors before deploying DDS:

● Region and Availability Zone: You can select a region and AZs based on thegeographical locations of users, product prices, DR capabilities, and networklatency. Once DB instances are successfully created in specific AZs in a region,the region cannot be changed. For more information, see Region and AZ.

● Network planning: When creating a DDS DB instance, you are advised to usethe Virtual Private Network (VPC) and subnet where the Elastic Cloud Server(ECS) is deployed.

● Data security: DDS provides comprehensive assurance for the data securitythat you may concern. You can deploy DB instances in multiple AZs and useaudit logs, isolated networks, security groups, and data encryption to ensuredata security.



2 Advantages

DDS provides several types of DB instances with high reliability and scalability. Youcan manage them using various O&M tools in a visual way.

Diverse Instance TypesThere are many instance types to meet your requirements in different scenarios.

Table 2-1 Architecture

InstanceArchitecture

Description Application Scenario

Cluster A DDS cluster consists of threetypes of nodes: mongos, shard, andconfig. You can select the numberof mongos and shard nodes andthe cluster configuration you needbased on your performancerequirements.

Cluster instances arerecommended for servicesystems that require both highavailability and scalability.

Replicaset

A DDS replica set consists of threenodes: primary, secondary, andhidden. Data is automaticallysynchronized between nodes toensure high data reliability. If aprimary node goes down orbecomes faulty, the replica setelects a secondary node as a newprimary node and continuesnormal operations.

Replica set instance suits small-and medium-sized servicesystems that require highavailability.

Singlenode

While not as robust as replica sets,single node architecture can be aless expensive way to visualizeO&M and provide elastic scaling.

Single node instances are usefulfor R&D, testing, and non-coredata storage of enterprises.

Document Database ServiceService Overview 2 Advantages


Elastic ScalingDDS allows you to change the storage space, node quantity, CPU, and memory ofan instance.

Friendly UIA web-based console provides comprehensive monitoring information, makingyour operations easy and visual.

Secure● VPCs, subnets, security groups, storage encryption, SSL, and DDoS protection

are provided to defend against various malicious attacks and ensure datasecurity.

● DDS supports audit logs that record your operations on databases orcollections, helping you audit database security and analyze root cause offaults.

● Fine-grained permission management is supported.

Abundant O&M Tools● Backup and restoration

DDS supports full backup, incremental backup, and point-in-time backup andrestoration of replica sets. Backup data can be stored for up to 732 days.

● Monitoring and alarm reportingDDS monitors instance metrics. You can customize the objects you want tomonitor and configure notification policies to learn about the databaseservice status in a timely manner.

Other advantagesDDS also boasts outstanding service availability, data durability, system security,and maintenance cost. For details, see Comparison Between DDS and On-Premises Databases.

Document Database ServiceService Overview 2 Advantages


3 Comparison Between DDS and On-Premises Databases

DDS provides high availability. It is more reliable, secure, and cost-effective thanself-built databases.

Table 3-1 Comparison between DDS and on-premises databases

Item DDS On-Premises Database

Serviceavailability

99.95% Requires setting up theprimary/standby relationshipand HA environment forensuring the availability.

Datadurability

99.9999999% Requires self-guarantee,primary/standby relationshipsetup, and RAID setup.

Systemsecurity

● Anti-Distributed denial ofservice (DDoS) attack issupported, helping you repairvarious database securityvulnerabilities in a timelymanner.

● Supports log auditing.

● Requires procurement ofexpensive devices andsoftware, as well as manualdetection and fix of securityvulnerabilities.

● Requires procurement of anaudit system.

Document Database ServiceService Overview

3 Comparison Between DDS and On-PremisesDatabases


Item DDS On-Premises Database

Databasebackup

● Supports automated backupand allows configuration ofbackup policies based onservice operating period.

● Supports manually, physicallybacking up data at any timeand increases backupefficiency by 3 times.

● Backup files areautomatically uploaded toObject Storage Service (OBS)for storage.

● Requires self-setup andmaintenance.

● The open-source versionsupports only logical backup,resulting in low backupefficiency.

Monitoringand alarmreporting

Interconnects with Cloud Eye,which provides a visualizedplatform for you to viewmonitoring metrics in a periodof time and set thresholdalarms.

Requires you to compilemonitoring and alarm scripts,save monitoring data, and drawcharts on your own.

Hosting No need to pay for hosting fees. Requires purchase of threeservers and payment of highhosting fees.

Maintenance cost

Requires no extra O&M cost andsupports second-levelperformance monitoring andthreshold alarm and eventalarm setting.

Requires large manpowerinvestment and professionaldatabase administrator (DBA)for maintenance.

Deployment andscaling

Supports quick deployment,flexible application, elasticscaling, and one-clickspecification change.

Requires procurement,deployment, and coordinationof hardware that matchesoriginal devices.

Logtransfer

Stores slow query logs and errorlogs for one month.

Requires you to transfer, export,and query log information onyour own.

Highavailability

Provides high availabilitycapabilities, supporting second-level switchover and failover.

Requires self-setup of HAmonitoring. Data may be lostafter a manual primary/secondary switchover isperformed using commands.

Document Database ServiceService Overview

3 Comparison Between DDS and On-PremisesDatabases


4 Typical Application Scenarios

GamesGame players' information generated from game applications, such as players'equipment and bonus points, are stored in DDS databases. During peak hours,DDS cluster instances can handle large amounts of concurrent requests. DDScluster and replica set provide high availability to ensure the stable running ofgames in high-concurrency scenarios.

In addition, DDS is compatible with MongoDB and provides the non-schemamode, which frees you from changing table structure when the game play modechanges. DDS can totally meet the flexible gaming requirements. You can storestructured data with fixed schemas in Relational Database Service (RDS), storeservices with flexible schemas in DDS, and store hot data in GaussDB(for Redis),improving data efficiency and reducing data storage costs.

Advantages:

● Supports Embedded Documents: Embedded documents eliminate JOIN,reducing the application development complexity. Flexible schemas alsofacilitate rapid development and iteration.

● Easy to Cope with Peak Pressure: Sharded clusters provide enough capacityto store data into the TB range.

IoTDDS is compatible with MongoDB and provides the high-performance andasynchronous data write function. In certain scenarios, DDS can process data inthe memory database. In addition, cluster instances can dynamically add thenumber of mongos and shard nodes or upgrade specifications. The performanceand storage space can be quickly expanded, making cluster instances suitable forIoT scenarios with high concurrent writes.

Intelligent IoT terminals need to collect various types of data, store device logs,and analyze information in multiple dimensions. In recent years, IoT services havegrown rapidly, with huge volumes of data and increasing access traffic that requirehorizontal expansion capabilities for data storage.

DDS provides the secondary index to meet dynamic query requirements and usesthe MapReduce aggregation framework that is compatible with MongoDB toanalyze data from multiple dimensions.

Document Database ServiceService Overview 4 Typical Application Scenarios


Advantages:

● High Write Performance: DDS sharded cluster provides high writeperformance to meet the requirements of terabyte-scale databases.

● High Performance and Scalability: DDS supports applications with high QPSrates, and its sharding architecture can be scaled in or out to flexibly copewith application changes.

InternetDDS replica set uses the three-node HA architecture. Three data nodes form ananti-affinity group and are deployed on different physical servers to automaticallysynchronize data. The primary and secondary nodes provide services. Each nodehas a private IP address and works with Driver to allocate read workloads.

Many organizations need to process and store data into the TB range, requiringdata to be written to databases in real time and dynamic analysis capabilities inbig data computing.

Advantages:

● MapReduce: With a complete data analysis utility, you can query statementsor scripts, and distribute requests to DDS.

● Excellent Scalability: DDS DB instances can be scaled up to support growingservices and data volumes in content management systems.

Document Database ServiceService Overview 4 Typical Application Scenarios


5 Functions and Features

This section describes the main functions and features of DDS.

Migrating Data

With Data Replication Service (DRS), you can migrate self-built MongoDBdatabases or other cloud MongoDB databases to DDS in real time. DRS simplifiesdata transmission between databases and reduces data transmission costs.

Scaling up Storage

If the storage you purchased cannot meet your requirements, you can scale upthe instance.

Changing Instance Class

If the CPU or memory of an instance cannot meet your service requirements, youcan change the instance class on the console.

Backup and Restoration● You can configure the automated backup policy and create backups. The

maximum retention period for an automated backup is 732 days. A manualbackup can be retained until you delete it.

● Data can be restored using backup files. Replica set instances support point-in-time recovery at the instance level, database level and table level.

Monitoring Metrics

DDS monitors key performance metrics of instances and DB engines in realtime, including the CPU usage, memory usage, storage space usage, commandexecution frequency, delete statement execution frequency, insert statementexecution frequency, and number of active connections.

Managing Logs

DDS allows you to query and download database error logs and slow query logs.

Document Database ServiceService Overview 5 Functions and Features


https://support.huaweicloud.com/intl/en-us/drs/index.html

https://support.huaweicloud.com/intl/en-us/usermanual-dds/dds_03_0131.html


https://support.huaweicloud.com/intl/en-us/usermanual-dds/en-us_topic_0104472218.html

https://support.huaweicloud.com/intl/en-us/usermanual-dds/en-us_topic_backup_restore.html




https://support.huaweicloud.com/intl/en-us/usermanual-dds/en-us_topic_error_log.html

https://support.huaweicloud.com/intl/en-us/usermanual-dds/en-us_topic_slow_query_log.html

Configuring ParametersDDS allows you to manage parameter templates and modify parametertemplate settings on the console.

Cross-AZ Disaster RecoveryIf the region where your instance is located supports three or more AZs, you candeploy the instance across three AZs to achieve cross-AZ disaster recovery.

Document Database ServiceService Overview 5 Functions and Features





6 System Architecture

6.1 ClusterA cluster consists of a config node, and multiple mongos and shard nodes.

Data read and write requests are forwarded by the mongos nodes, which readconfiguration settings from config, and then allocate the read and write requeststo the shards, making it easy to cope with high concurrency scenarios. In addition,each config node, along with the shards in its cluster, is replicated in triplicate toensure high availability.

Document Database ServiceService Overview 6 System Architecture


Figure 6-1 Cluster architecture

● Each mongos is a single node, but you can provision multiple mongos nodesfor load balancing and failovers. A single cluster can contain 2 to 16 mongosnodes.

● Each shard is a three-node replica set. A single cluster supports 2 to 16 shards.● A config node is a necessary part of a cluster instance, and is also deployed as

a replica set. The config node stores instance configuration data.● Cluster is suitable for handling large amounts of data and can meet the

requirements for high availability and scalability.

6.2 Replica SetA replica set consists of a set of mongod processes. It is a collection of nodes thathelp ensure data redundancy and reliability.

NO TE

For details about the mongod process, see the MongoDB official document.

A replica set consists of three nodes: primary, secondary, and hidden. The three-node architecture is set up automatically, and the three nodes automaticallysynchronize data with each other to ensure data reliability. Replica sets arerecommended for small- and medium-sized service systems that require highavailability.



https://docs.mongodb.com/v3.2/tutorial/manage-mongodb-processes/index.html

● Primary node: Primary nodes are used to process both read and writerequests.

● Secondary node: Secondary nodes are used to process read requests only.● Hidden node: Hidden nodes are used to back up data.

You can perform operations on the primary and secondary nodes. If the primarynode is faulty, the system automatically selects a new primary node. The followingfigure shows the replica set architecture.

Figure 6-2 Three-node replica set architecture

After a replica set is created, you can add up to either 5 or 7 nodes. For detailsabout how to add a replica set node, see Adding Replica Set Instance Nodes.




Figure 6-3 Replica set instance nodes

6.3 Single NodeA single node instance, as its name suggests, contains only one node and thatnode can be accessed directly.

As a supplement to the cluster and replica set architectures, the single-nodearchitecture is useful for R&D, testing, and non-core data storage of enterprises.While not as robust as replica sets, single node architecture can be a lessexpensive way to visualize O&M and provide elastic scaling.



Figure 6-4 Single node architecture



7 Instances

7.1 DB Engines and VersionsDDS supports versions 4.0 and 3.4, and you need to use a driver compatible withMongoDB 3.0 or later to access DDS. You can select the DB engine and versionyou need based on your service requirements.

Table 7-1 Supported DB engines and versions

Compatibility CPU Type DB Instance Type Storage Engine

4.0 ● x86● Kunpeng

● Cluster● Replica set● Single node

WiredTiger

3.4 ● x86● Kunpeng

● Cluster● Replica set● Single node

WiredTiger

For details about the compatibility between DDS and MongoDB CommunityEditions, see Versions.

7.2 Instance Specifications

7.2.1 ClusterInstances of the same type have different memory specifications. You can selectinstances of different specifications based on application scenarios.

This section describes cluster instance specifications. The instance specificationsdepend on the selected CPU model.

Document Database ServiceService Overview 7 Instances


NO TE

The default maximum number of connections has been adjusted. Query the number ofconnections based on the instance creation time. For details about the number ofconnections for instances created before July 2021, see Historical Node Specifications.

Node Specifications

Table 7-2 config specifications

CPUType

Specifications

vCPUs Memory(GB)

Flavor ID DefaultMaximumNumberofConnections

Range ofConnections

x86 Enhanced

2 4 dds.mongodb.c3.large.2.config

2000 200-2000

4 8 dds.mongodb.c3.xlarge.2.config

4000 200-4000

8 16 dds.mongodb.c3.2xlarge.2.config

16000 200-16000

EnhancedII


2000 200-2000

Kunpeng

- 2 4 dds.mongodb.large.arm2.config

2000 200-2000

4 8 dds.mongodb.xlarge.arm2.config

4000 200-4000

8 16 dds.mongodb.2xlarge.arm2.config

16000 200-16000



Table 7-3 mongos and shard specifications

CPUType

Specifications

Component

vCPUs Memory (GB)

Flavor ID DefaultMaximumNumber ofConnections

Range ofConnections

x86 General-purpose

mongos

1 4 dds.mongodb.s6.medium.4.mongos

1000 200-1000

2 4 dds.mongodb.s6.large.2.mongos

2000 200-2000


2000 200-2000

4 8 dds.mongodb.s6.xlarge.2.mongos

4000 200-4000


4000 200-4000

8 16 dds.mongodb.s6.2xlarge.2.mongos

16000 200-16000


16000 200-16000

shard 1 4 dds.mongodb.s6.medium.4.shard

1000 200-1000

2 4 dds.mongodb.s6.large.2.shard

2000 200-2000


2000 200-2000

4 8 dds.mongodb.s6.xlarge.2.shard

4000 200-4000


4000 200-4000

8 16 dds.mongodb.s6.2xlarge.2.shard

16000 200-16000


16000 200-16000



CPUType

Specifications

Component

vCPUs Memory (GB)


Range ofConnections

EnhancedII

mongos

2 8 dds.mongodb.c6.large.4.mongos

2000 200-2000

4 16 dds.mongodb.c6.xlarge.4.mongos

4000 200-4000

8 32 dds.mongodb.c6.2xlarge.4.mongos

16000 200-16000


16000 200-16000


16000 200-16000


16000 200-16000

shard 2 8 dds.mongodb.c6.large.4.shard

2000 200-2000

4 16 dds.mongodb.c6.xlarge.4.shard

4000 200-4000

8 32 dds.mongodb.c6.2xlarge.4.shard

16000 200-16000


16000 200-16000


16000 200-16000


16000 200-16000

Kunpeng

- mongos

2 4 dds.mongodb.large.arm2.mongos

2000 200-2000

- 2 8 dds.mongodb.large.arm4.mongos

2000 200-2000

- 4 8 dds.mongodb.xlarge.arm2.mongos

4000 200-4000



CPUType

Specifications

Component

vCPUs Memory (GB)


Range ofConnections


4000 200-4000

- 8 16 dds.mongodb.2xlarge.arm2.mongos

16000 200-16000


16000 200-16000


16000 200-16000


16000 200-16000

- shard 2 4 dds.mongodb.large.arm2.shard

2000 200-2000

- 2 8 dds.mongodb.large.arm4.shard

2000 200-2000

- 4 8 dds.mongodb.xlarge.arm2.shard

4000 200-4000


4000 200-4000

- 8 16 dds.mongodb.2xlarge.arm2.shard

16000 200-16000


16000 200-16000


16000 200-16000


16000 200-16000



Historical Node Specifications

For details about the range of connections of instances created before July 2021,see the following table.

Table 7-4 config specifications

InstanceType

CPUType

Specifications

vCPUs Memory(GB)


Range ofConnections

Cluster

x86 General-purpose

2 4 dds.mongodb.s6.large.2.config

400 200-2000

Enhanced


EnhancedII


Kunpeng

- 2 4 dds.mongodb.large.arm2.config

Table 7-5 mongos and shard specifications

InstanceType

CPUType

Specifications

Component

vCPUs Memory(GB)


RangeofConnections

Cluster

x86 General-purpose

mongos

1 4 dds.mongodb.s6.medium.4.mongos

400 200-1000


400 200-2000



InstanceType

CPUType

Specifications

Component

vCPUs Memory(GB)


RangeofConnections


400 200-2000


1000 200-4000


1000 200-4000


4000 200-16000


4000 200-16000

shard 1 4 dds.mongodb.s6.medium.4.shard

400 200-1000


400 200-2000


400 200-2000


1000 200-4000


1000 200-4000


4000 200-16000



InstanceType

CPUType

Specifications

Component

vCPUs Memory(GB)


RangeofConnections


4000 200-16000

Enhanced

mongos


400 200-2000


1000 200-4000


4000 200-16000


8000 200-16000


8000 200-16000


8000 200-16000


400 200-2000


1000 200-4000


4000 200-16000


8000 200-16000



InstanceType

CPUType

Specifications

Component

vCPUs Memory(GB)


RangeofConnections


8000 200-16000


8000 200-16000

EnhancedII

mongos


400 200-2000


1000 200-4000


4000 200-16000


8000 200-16000


8000 200-16000


8000 200-16000


400 200-2000


1000 200-4000


4000 200-16000



InstanceType

CPUType

Specifications

Component

vCPUs Memory(GB)


RangeofConnections


8000 200-16000


8000 200-16000


8000 200-16000

Kunpeng

- mongos

2 4 dds.mongodb.large.arm2.mongos

400 200-2000

- 2 8 dds.mongodb.large.arm4.mongos

400 200-2000


1000 200-4000


1000 200-4000


4000 200-16000


4000 200-16000


8000 200-16000



InstanceType

CPUType

Specifications

Component

vCPUs Memory(GB)


RangeofConnections


8000 200-16000

- shard 2 4 dds.mongodb.large.arm2.shard

400 200-2000

- 2 8 dds.mongodb.large.arm4.shard

400 200-2000


1000 200-4000


1000 200-4000


4000 200-16000


4000 200-16000


8000 200-16000


8000 200-16000



Helpful Links1. How do I change the maximum number of connections of a cluster instance?

You can change the maximum number of connections to a DB instance bymodifying the net.maxIncomingConnections parameter. For details abouthow to change parameter values, see Editing a Parameter Template.

2. How do I purchase a cluster instance?For details, see Buying a Cluster Instance.

3. How do I change the CPU or memory of a cluster instance?You can change the CPU and memory of mongos and shards nodes. Fordetails, see Changing the CPU and Memory of a Cluster Instance.

4. How do I scale up the storage space of a cluster instance?You can scale up the storage of shards nodes. For details, see Scaling UpStorage.

7.2.2 Replica SetInstances of the same type have different memory specifications. You can selectinstances of different specifications based on application scenarios.

This section describes replica set instance specifications. The instance specificationsdepend on the selected CPU model.

NO TE

The default maximum number of connections has been adjusted. Query the number ofconnections based on the instance creation time. For details about the number ofconnections for instances created before July 2021, see Historical Instance Specifications.

Instance SpecificationsTable 7-6 lists the specifications of replica set instances.

Table 7-6 Replica set instance specifications

CPUType

Specifications

vCPUs Memory(GB)


RangeofConnections

x86 General-purpose

2 4 dds.mongodb.s6.large.2.repset

1000 200-1000


1000 200-1000

4 8 dds.mongodb.s6.xlarge.2.repset

3000 200-3000



https://support.huaweicloud.com/intl/en-us/usermanual-dds/en-us_topic_configuration.html

https://support.huaweicloud.com/intl/en-us/qs-dds/dds_02_0064.html


https://support.huaweicloud.com/intl/en-us/usermanual-dds/en-us_topic_increase_storage.html


CPUType

Specifications

vCPUs Memory(GB)


RangeofConnections


3000 200-3000

8 16 dds.mongodb.s6.2xlarge.2.repset

8000 200-8000


8000 200-8000

Enhanced II

2 8 dds.mongodb.c6.large.4.repset

1000 200-1000

4 16 dds.mongodb.c6.xlarge.4.repset

3000 200-3000

8 32 dds.mongodb.c6.2xlarge.4.repset

8000 200-8000


16000 200-16000


16000 200-16000


16000 200-16000

Kunpeng

- 2 4 dds.mongodb.large.arm2.repset

1000 200-1000


1000 200-1000

- 4 8 dds.mongodb.xlarge.arm2.repset

3000 200-3000


3000 200-3000

- 8 16 dds.mongodb.2xlarge.arm2.repset

8000 200-8000


8000 200-8000


16000 200-16000



CPUType

Specifications

vCPUs Memory(GB)


RangeofConnections


16000 200-16000

Historical Instance Specifications


Table 7-7 Replica set instance specifications

CPUType

Specifications

vCPUs Memory(GB)


RangeofConnections

x86 General-purpose


400 200-1000


400 200-1000


1000 200-3000


1000 200-3000


4000 200-8000


4000 200-8000

Enhanced


400 200-1000


1000 200-3000



CPUType

Specifications

vCPUs Memory(GB)


RangeofConnections


4000 200-8000


8000 200-16000


8000 200-16000


8000 200-16000

Enhanced II


400 200-1000


1000 200-3000


4000 200-8000


8000 200-16000


8000 200-16000


8000 200-16000

Kunpeng


400 200-1000


400 200-1000


1000 200-3000


1000 200-3000


4000 200-8000


4000 200-8000



CPUType

Specifications

vCPUs Memory(GB)


RangeofConnections


8000 200-16000


8000 200-16000

Helpful Links1. How do I change the maximum number of connections of a replica set

instance?You can change the maximum number of connections to an instance bymodifying the net.maxIncomingConnections parameter. For details abouthow to change parameter values, see Editing a Parameter Template.

2. How do I buy a replica set instance?For details, see Buying a Replica Set Instance.

3. How do I change the CPU and memory of a replica set instance?For details, see Changing the CPU or Memory of a Replica Set Instance.

4. How do I scale up the storage space of a replica set instance?For details, see Scaling Up Storage.

7.2.3 Single NodeInstances of the same type have different memory specifications. You can selectinstances of different specifications based on application scenarios.

This section describes single node instance specifications. The instancespecifications depend on the selected CPU model.

NO TE

The default maximum number of connections has been adjusted. Query the number ofconnections based on the instance creation time. For details about the number ofconnections for instances created before July 2021, see Historical Instance Specifications.







Instance Specifications

Table 7-8 Single Node

CPUType

Specifications

vCPUs Memory(GB)


Range ofConnections

x86 General-purpose

1 4 dds.mongodb.s6.medium.4.single

500 200-500

2 4 dds.mongodb.s6.large.2.single

1000 200-1000


1000 200-1000

4 8 dds.mongodb.s6.xlarge.2.single

8000 200-8000


8000 200-8000

8 16 dds.mongodb.s6.2xlarge.2.single

10000 200-10000


10000 200-10000

Enhanced II

2 8 dds.mongodb.c6.large.4.single

500 200-500

4 16 dds.mongodb.c6.xlarge.4.single

1000 200-1000

8 32 dds.mongodb.c6.2xlarge.4.single

4000 200-4000


8000 200-8000


16000 200-16000


16000 200-16000

Kunpeng

- 2 4 dds.mongodb.large.arm2.single

1000 200-1000


1000 200-1000



CPUType

Specifications

vCPUs Memory(GB)


Range ofConnections

- 4 8 dds.mongodb.xlarge.arm2.single

8000 200-8000


8000 200-8000

- 8 16 dds.mongodb.2xlarge.arm2.single

10000 200-10000


10000 200-10000


16000 200-16000


16000 200-16000

Historical Instance Specifications


Table 7-9 Single Node

CPUType

Specifications

vCPUs Memory(GB)


RangeofConnections

x86 General-purpose

1 4 dds.mongodb.s6.medium.4.single

400 200-500


400 200-1000


400 200-1000



CPUType

Specifications

vCPUs Memory(GB)


RangeofConnections


1000 200-8000


1000 200-8000


4000 200-10000


4000 200-10000

Enhanced


400 200-1000


1000 200-8000


4000 200-10000


8000 200-16000


8000 200-16000


8000 200-16000

Enhanced II


400 200-500


1000 200-1000


4000 200-4000


8000 200-8000


8000 200-16000



CPUType

Specifications

vCPUs Memory(GB)


RangeofConnections


8000 200-16000

Kunpeng


400 200-1000


400 200-1000


1000 200-8000


1000 200-8000


4000 200-10000


4000 200-10000


8000 200-16000


8000 200-16000

Helpful Links1. How do I change the maximum number of connections of a single node

instance?You can change the maximum number of connections to an instance bymodifying the net.maxIncomingConnections parameter. For details abouthow to change parameter values, see Editing a Parameter Template.

2. How do I buy a single node instance?For details, see Buying a Single Node Instance.

3. How do I change the CPU and memory of a single node instance?For details, see Changing the CPU or Memory of a Single Node Instance.

4. How do I scale up the storage of a single node instance?For details, see Scaling Up Storage.







7.3 Read ReplicaTo improve the read capability of the primary node, DDS provides read replicasthat can be accessed independently, which are suitable for handling read-intensiveworkloads and reducing memory pressure on the primary node. You can alsocreate one or more read replicas to process a large number of read requests andimprove throughput.

Differences Between Read Replica and Secondary NodeNode

Description Application Scenario

Secondarynodes

The secondary node of a replicaset instance ensures highavailability. If a primary node isfaulty, the system automaticallyswitches traffic to the secondarynode. If the primary node isfaulty, each secondary node maybe elected as a new primarynode to execute data writerequests.

DDS provides an HA connectionaddress to connect to both theprimary and secondary nodes andseparate read and write operations.In this way, a DDS instance canhandle heavy read workloads withease. In addition, the impact of nodefaults on services is wakened whilethe performance is improved.

Readreplicas

A read replica in a replica setinstance synchronizes data onlyfrom the primary node. It doesnot ensure high availability andwill not be elected as theprimary node. Read replicas canbe connected independently anddo not interfere with primarynodes.

Apply to scenarios where applicationsneed to read large amounts of datafrom existing instances.

Constraints● Only replica set instances can have read replicas.● Instances that only have read replicas cannot be created.● DDS instance version must be 3.4 and 4.0.● Read replicas are used only for processing read requests and do not

participate in primary/secondary node election.● A maximum of five read replicas can be added to a replica set instance. To

add a read replica, see Adding a Read Replica.● Data is asynchronously replicated between the primary node and the read

replica, and this process will delay by a few seconds.




Functions● You can change the number of read replicas to meet fluctuating service

demands and reduce service costs.● The specifications of a read replica are the same as those of the primary

node. Data is automatically synchronized to the read replica.● Resources on the primary node are not occupied. Adding or deleting read

replicas does not affect services on the primary node.● Read replicas can be connected independently and do not interfere with

existing primary and secondary nodes.● You can monitor the performance of read replicas.

Billing● After a read replica is added to the current instance, you will be billed for

using the VM and disks of the read replica.● The price of a read replica is equal to that of a single node in a replica set

instance or a shard node in a cluster instance. For example, if the price of athree-node replica set instance is USD $3,000, the price of a read replica isUSD $1,000.



8 Pricing Details

HUAWEI CLOUD Document Database Service (DDS) provides different DB instancetypes, including replica set and cluster. These instances are charged on a pay-per-use basis and there are no minimum usage requirements.

Pricing

Table 8-1 Description

Item Description Billing Standards

Instancespecifications

The instance specifications thatyou select.For a cluster instance, thespecification fees refer to thefees of mongos, shard, andconfig specifications.

For details, see ProductPricing Details. You canuse the DDS pricecalculator to quicklyobtain an estimate priceof a DB instance with thespecifications you select.

Storage Storage space is charged on thecapacity you selected.For cluster instances, thestorage fees include the storagefees of shard and config nodes.

Backup storage(optional)

DDS backup files are stored inOBS and do not occupy thestorage of DDS instances.DDS provides backup storageup to 100% of your provisioneddatabase storage at noadditional fees. If the backupstorage usage exceeds 100% ofyour provisioned databasestorage, you will be charged forresource usage.

Document Database ServiceService Overview 8 Pricing Details


https://www.huaweicloud.com/intl/en-us/pricing/index.html?tab=detail#/dds


Item Description Billing Standards

Audit log space(optional)

An audit log records operationsperformed on your databasesand collections. The generatedlog files are stored in OBS.

Enabling audit log incurscertain fees. For details,see Pricing Details.

(Optional) Publicnetwork traffic

● DDS instances can beaccessed from the Internet,and traffic fees aregenerated accordingly.

● You are not charged for thetraffic generated in thecloud.

For details, see EIPPricing Details.

Billing ModeDDS provides two billing modes: pay-per-use and yearly/monthly. Pay-per-use isrecommended if you are unsure of your future service needs and want to avoidpaying for unused resources. However, if you are sure of your needs, yearly/monthly will be less expensive.

● Yearly/Monthly is a prepaid billing mode, which provides a larger discountthan pay-per-use billing and is recommended for long-term use of resources.

● Pay-per-use (hourly): This billing mode is flexible. You pay only for what youuse. Pricing is listed on a per-hour basis, but bills are calculated based on theactual usage duration.

● You can change the billing mode from pay-per-use to yearly/monthly or viceversa.For operation details, see Changing the Billing Mode from Pay-per-Use toYearly/Monthly and Changing the Billing Mode from Yearly/Monthly toPay-per-Use.

Configuration ChangesYou can change the specifications of an existing DB instance based on your servicerequirements. After the change, the instance is billed based on the newspecifications.

● Adding instances or nodes: You can add instances to handle growing services.After the instances are added, you will be charged based on the new numberof instances. The number of cluster instances can only be increased. Thenumber of mongos nodes ranges from 2 to 32, the number of shard nodesranges from 2 to 32, and the number of config nodes is 1 by default.

● Scaling up storage space: You can change the storage space based on servicerequirements. After scaling the storage space, you will be charged based onthe new storage space. Note that storage space cannot be scaled down.

RenewalDDS supports the yearly/monthly and pay-per-use billing modes.




https://www.huaweicloud.com/intl/en-us/pricing/index.html?tab=detail#/eip

https://www.huaweicloud.com/intl/en-us/pricing/index.html?tab=detail#/eip

https://support.huaweicloud.com/intl/en-us/usermanual-dds/en-us_topic_instance_mgmt.html

https://support.huaweicloud.com/intl/en-us/usermanual-dds/en-us_topic_instance_mgmt.html



● Pay-per-use: You are charged for a full hour regardless of whether you use thefull or partial hour. You can use the service as long as your account balance issufficient. If your account balance is insufficient, the service cannot be usednormally. Top up your account in a timely manner.

● Yearly/monthly: An upfront payment is required when you purchase theservice. No additional fees are incurred during your usage.



9 Basic Concepts

9.1 Instance● An instance is a basic management unit of DDS. One or more databases can

be created in a single DDS instance, and one or more collections can becreated in each database.

● You can create and manage DB instances of various types and versions on themanagement console. For details about DB instance types, versions, andspecifications, see Instances.

● Resources, such as the CPU, memory, and I/O, of each DDS DB instance areisolated from each other.

9.2 ClusterEach DDS cluster consists of a config node, and multiple mongos and shard nodes.The following diagram shows the node relationships.

Document Database ServiceService Overview 9 Basic Concepts


Figure 9-1 Diagram of node relationships

mongosA mongos is a router for reading and writing data, providing a unified interface foraccessing DB instances.● Each DB instance has 2 to 16 mongos nodes. You can specify the quantity.● A mongos reads configuration settings from configs and allocates read and

write requests to shards. You can connect to a mongos directly.

configA config stores configuration settings for DB instances and consists of one replicaset.

You cannot connect to a config node directly.

shardShards are used to store user data.● Each Community Edition instance has 2 to 16 shard nodes. You can specify

the quantity.● Each shard node is deployed as a replica set to ensure data redundancy and

high reliability.● You cannot connect to a shard node directly.

9.3 Database Parameter TemplateA database parameter template is a collection of configuration parameters andvalues and can be applied to multiple DB instances.



9.4 Region and AZ

ConceptA region and availability zone (AZ) identify the location of a data center. You cancreate resources in a specific region and AZ.

● Regions are divided from the dimensions of geographical location andnetwork latency. Public services, such as Elastic Cloud Server (ECS), ElasticVolume Service (EVS), Object Storage Service (OBS), Virtual Private Cloud(VPC), Elastic IP (EIP), and Image Management Service (IMS), are sharedwithin the same region. Regions are classified as universal regions anddedicated regions. A universal region provides universal cloud services forcommon tenants. A dedicated region provides services of the same type onlyor for specific tenants.

● An AZ contains one or multiple physical data centers. Each AZ hasindependent cooling, fire extinguishing, moisture-proof, and electricityfacilities. Within an AZ, computing, network, storage, and other resources arelogically divided into multiple clusters. AZs within a region are interconnectedusing high-speed optical fibers to allow you to build cross-AZ high-availabilitysystems.

Figure 9-2 shows the relationship between regions and AZs.

Figure 9-2 Region and AZ

HUAWEI CLOUD provides services in many regions around the world. You canselect a region and AZ as needed. For more information, see HUAWEI CLOUDGlobal Regions.

Selecting a RegionWhen selecting a region, consider the following factors:

● LocationYou are advised to select a region close to you or your target users. Thisreduces network latency and improves access rate. However, Chinesemainland regions provide basically the same infrastructure, BGP networkquality, as well as operations and configurations on resources. Therefore, if



https://www.huaweicloud.com/intl/en-us/global/

https://www.huaweicloud.com/intl/en-us/global/

you or your target users are in the Chinese mainland, you do not need toconsider the network latency differences when selecting a region.

● Resource priceResource prices may vary in different regions. For details, see Product PricingDetails.

Selecting an AZWhen determining whether to deploy resources in the same AZ, consider yourapplications' requirements on disaster recovery (DR) and network latency.

● For high DR capability, deploy resources in different AZs in the same region.● For low network latency, deploy resources in the same AZ.

Regions and EndpointsBefore using an API to call resources, specify its region and endpoint. For moredetails, see Regions and Endpoints.

9.5 DB ConnectionsThe number of connections indicates the number of databases that can besimultaneously connected to an application. The number of connections isirrelevant to the maximum number of users allowed by your applications orwebsites.

● For a cluster instance, the number of connections is the number ofconnections between the client and the mongos nodes.

● For a replica set instance, the number of connections is the number ofconnections between the client and the primary and secondary nodes.

● For a single-node instance, the number of connections is the number ofconnections between the client and the node.





https://developer.huaweicloud.com/intl/en-us/endpoint

10 Compatibility

10.1 VersionsDDS supports versions 3.4 and 4.0. This section describes the compatibilitybetween DDS and MongoDB Community Editions.

● DDS 3.4DDS 3.4 is fully compatible with MongoDB 3.4 Community Edition.

● DDS 4.0DDS 4.0 is fully compatible with MongoDB 4.0 Community Edition andpartially compatible with MongoDB 4.4 Community Edition.

10.2 DetailsThis section describes the features and compatibility of DDS and MongoDB.

Document Database ServiceService Overview 10 Compatibility


MongoDB Compatibility

Table 10-1 Compatible features

Category

Details DDS 4.0 DDS 4.2 MongoDB 4.2CommunityEdition

MongoDB 4.4CommunityEdition

Databasecommands

The find commandsupports theallowDiskUse field,which allowsMongoDB to usetemporary files ondisk to store dataexceeding the systemmemory limit whileprocessing a non-index sort operation.

× × × √

Distributedtransactions

Distributedtransactions aresupported. Distributedtransactions refer tomulti-documenttransactions onsharded clusters andreplica sets. Multi-documenttransactions (whetheron sharded clusters orreplica sets) are alsoknown as distributedtransactions startingin MongoDB 4.2.

× √ √ √

The 16 MB total sizelimit for a transactionwas removed.

× × √ √

The MongoDB driversmust be updated forMongoDB 4.2.

× √ √ √



https://docs.mongodb.com/v4.2/release-notes/4.2/#distributed-transactions




Category



Aggregation

● The aggregationcapability isimproved. Data canbe updated in theaggregationpipeline.

● Added $merge.● Added

$accumulator and$function.

● Supported unionAll.

● Added $unionWith.● For details about

aggregationoperations, seeTable 10-2.

√ √ √ √

Wildcardindexes

Wildcard indexes aresupported.

√ √ √ √

Shardedcluster

A document's shardkey field value can bechanged.

× × √ √

The fields associatedwith the shard keycan be adjusted.

√ √ × √

Collections can besharded using acomposite shard keythat consists of asingle hash field.

× × × √

The 512-byte sizelimit on a shard keywas removed.

× × × √

Multi-documenttransactions allow thecreation of indexesand collections (non-distributedtransactions).

× × × √



https://docs.mongodb.com/v4.2/aggregation/

https://docs.mongodb.com/v4.2/aggregation/

https://docs.mongodb.com/v4.2/core/index-wildcard/



https://docs.mongodb.com/v4.2/sharding/#sharded-cluster

https://docs.mongodb.com/v4.2/sharding/#sharded-cluster

Category



Indexes The size limit onindexes was removed.

√ √ √ √

The length limit onindex names wasremoved.

× × √ √

Composite indexescan contain hashindexes.

× × × √

Hidden indexes aresupported forcommissioning.

√ √ × √

The size limit oncollection namespacesis changed.The length of<database>.<collection> is increased from120 bytes to 255bytes.

× × × √

NO TE

√ indicates that an item is supported, and × indicates that an item is not supported.

Aggregation Operations

Table 10-2 Aggregation operations

Operator DDS 4.0 DDS 4.2 MongoDB 4.2CommunityEdition


$sin √ √ √ √

$cos √ √ √ √

$tan √ √ √ √

$asin √ √ √ √

$acos √ √ √ √

$atan √ √ √ √



https://docs.mongodb.com/v4.2/indexes/



$atan2 √ √ √ √

$asinh √ √ √ √

$acosh √ √ √ √

$atanh √ √ √ √

$degreesToRadians

√ √ √ √

$radiansToDegrees

√ √ √ √

$round √ √ √ √

$trunc √ √ √ √

$regexFind √ √ √ √

$regexFindAll √ √ √ √

$regexMatch √ √ √ √

$merge √ √ √ √

$planCacheStats

× × √ √

$replaceWith √ √ √ √

$set √ √ √ √

$unset √ √ √ √

NOW √ √ √ √

CLUSTER_TIME

√ √ √ √

findAndModify

√ √ × √

update √ √ √ √

$accumulator √ √ × √

$binarySize √ √ × √

$bsonSize √ √ × √

$first √ √ × √

$function √ √ × √

$last √ √ × √





$isNumber √ √ × √

$replaceOne √ √ × √

$unionWith √ √ × √

NO TE

√ indicates that an item is supported, and × indicates that an item is not supported.

10.3 BrowsersFor details about the compatibility between DDS and browsers, see WhichBrowsers Are Supported?



https://support.huaweicloud.com/intl/en-us/usermanual-iaas/en-us_topic_0041752254.html

https://support.huaweicloud.com/intl/en-us/usermanual-iaas/en-us_topic_0041752254.html

11 Permissions Management

If you need to assign different permissions to employees in your enterprise toaccess your DDS resources, IAM is a good choice for fine-grained permissionsmanagement. IAM provides identity authentication, permissions management,and access control, helping you secure access to your HUAWEI CLOUD resources.

With IAM, you can use your HUAWEI CLOUD account to create IAM users for youremployees, and assign permissions to the users to control their access to specificresource types. For example, some software developers in your enterprise need touse DDS resources but must not delete them or perform any high-risk operations.To achieve this result, you can create IAM users for the software developers andgrant them only the permissions required for using DDS resources.

If your HUAWEI CLOUD account does not need individual IAM users forpermissions management, you may skip over this topic.

IAM can be used free of charge. You pay only for the resources in your account.For more information about IAM, see IAM Service Overview.

DDS PermissionsBy default, new IAM users do not have permissions assigned. You need to add auser to one or more groups, and attach permissions policies or roles to thesegroups. Users inherit permissions from the groups to which they are added andcan perform specified operations on cloud services based on the permissions.

DDS is a project-level service deployed and accessed in specific physical regions. Toassign GaussDB NoSQL permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If Allprojects is selected, the permissions will take effect for the user group in allregion-specific projects. When accessing DDS, users need to switch to a regionwhere they have been authorized to use DDS.

You can grant users permissions by using roles and policies.

● Roles: A type of coarse-grained authorization mechanism that definespermissions related to user responsibilities. This mechanism provides only alimited number of service-level roles for authorization. When using roles togrant permissions, you need to also assign other roles on which thepermissions depend to take effect. However, roles are not an ideal choice forfine-grained authorization and secure access control.

Document Database ServiceService Overview 11 Permissions Management


https://support.huaweicloud.com/intl/en-us/productdesc-iam/iam_01_0026.html

● Policies: A type of fine-grained authorization mechanism that definespermissions required to perform operations on specific cloud resources undercertain conditions. This mechanism allows for more flexible policy-basedauthorization, meeting requirements for secure access control. For example,you can grant DDS users only the permissions for managing a certain type ofresources.

Table 11-1 lists all the system-defined roles and policies supported by DDS.

Table 11-1 System-defined roles and policies supported by DDS

Policy Name/System Role

Description Type Dependency

DDS FullAccess All operations on DDS. System-definedpolicy

None

DDSReadOnlyAccess

Read-only permissions forDDS resources. Usersgranted these permissionscan only view DDS data.

System-definedpolicy

None

DDSManageAccess

DBA permissions on DDSexcept the DDS DB instancedeletion operations.

System-definedpolicy

None

DDSAdministrator

DDS administrator, who hasall permissions of theservice.

System-defined role

The TenantGuest andTenantAdministratorroles need tobe assigned inthe sameproject.

Table 11-2 lists the common operations supported by each system-defined policyor role of DDS. Select the policies or roles as required.

Table 11-2 Common operations supported by the DDS system policy

Operation DDSFullAccess

DDSReadOnlyAccess

DDSManageAccess

DDSAdministrator

Creating aninstance

√ x √ √

Querying DBinstances

√ √ √ √

Deleting a DBinstance

√ x x √




DDSReadOnlyAccess

DDSManageAccess

DDSAdministrator

Restarting aDB instance

√ x √ √

Performing aprimary/secondaryswitchover

√ x √ √

Modifying theport

√ x √ √

Resetting apassword

√ x √ √

Modified SSL √ x √ √

Modifying asecurity group

√ x √ √

Binding andunbinding anEIP

√ x √ √

Scaling upstorage space

√ x √ √

Changing DBinstanceclasses

√ x √ √

Adding nodes √ x √ √

Deleting thenode thatfails to beadded

√ x × √

Modifying anautomatedbackup policy

√ x √ √

Renaming aDB instance

√ x √ √

Changing aprivate IPaddress

√ x √ √




DDSReadOnlyAccess

DDSManageAccess

DDSAdministrator

Changing theparametertemplateassociatedwith the nodein a DBinstance

√ x √ √

Showingoriginal slowlogs

√ x √ √

Enabling ordisabling locallog auditing

√ x √ √

Downloadingaudit logs

√ x √ √

Deleting auditlogs

√ x × √

Downloadinga backup file

√ x √ √

Changing thebilling modefrom pay-per-use to yearly/monthly

√ x √ √

Creating amanualbackup

√ x √ √

Querying thebackup list

√ √ √ √

Restoringdata to a newDB instance

√ x √ √

Restoring toan existingDB instance

√ x √ √

Deleting abackup

√ x × √

Creating aparametertemplate

√ x √ √




DDSReadOnlyAccess

DDSManageAccess

DDSAdministrator

Viewingparametertemplates

√ √ √ √

Modifying aparametertemplate

√ x √ √

Deleting aparametertemplate

√ x × √

Task Centerlist

√ x √ √

Table 11-3 lists common DDS operations and corresponding actions. You can referto this table to customize permission policies.

Table 11-3 Common Operations and actions

Operation Actions AuthorizationScope

Description

Instancecreationpage

● vpc:vpcs:list● vpc:subnets:

get● vpc:security

Groups:get

Supported:● IAM projects● Enterprise

projects

The VPC, subnet, and securitygroup are displayed on theinstance creation page.

Creating aninstance

● dds:instance:create

● vpc:vpcs:list● vpc:vpcs:get● vpc:subnets:

get● vpc:security

Groups:get● vpc:ports:get


projects

If the default VPC, subnet,and security group are used,the vpc:*:create permissionmust be configured.To create an encryptedinstance, configure the KMSAdministrator permission forthe project.

QueryingDBinstances

dds:instance:list Supported:● IAM projects● Enterprise

projects

-




Description

Queryingdetails of aDB instance


projects

If the VPC, subnet, andsecurity group need to bedisplayed on the instancedetails page, add the vpc:*:getand vpc:*:list actions.

ExportingDB instancelists


projects

If the VPC, subnet, andsecurity group are required,add the vpc:*:get and vpc:*:listactions.

Deleting aDB instance

dds:instance:deleteInstance


projects

When deleting a DB instance,delete the IP address on thedata side.

Restartinga DBinstance

dds:instance:reboot


projects

-

Performinga primary/secondaryswitchover

dds:instance:switchover


projects

-

Changing aport

dds:instance:modifyPort


projects

-

Resetting apassword

dds:instance:resetPasswd


projects

-

ModifiedSSL

dds:instance:modifySSL


projects

-

Modifyinga securitygroup

dds:instance:modifySecurityGroup


projects

-




Description

Binding anEIP

dds:instance:bindPublicIp

Supported:● IAM projects

When binding an EIP, youneed to query the created EIP.● Enterprise projects are not

supported.● Fine-grained

authentication is notsupported.

For details, see Floating IPAddress.

Unbindingan EIP

dds:instance:unbindPublicIp

Supported:● IAM projects

● Enterprise projects are notsupported.

● Fine-grainedauthentication is notsupported.

For details, see Floating IPAddress.

Scaling upstoragespace

dds:instance:extendVolume


projects

-

ChangingDB instanceclasses

dds:instance:modifySpec


projects

-

Addingnodes

● dds:instance:extendNode


get● vpc:security



projects

-

Deletingthe nodethat fails tobe added

dds:instance:extendNode


projects

If the IP address has beencreated but the subsequentprocedure fails, delete the IPaddress on the data side.



https://support.huaweicloud.com/intl/en-us/api-eip/eip_apipermission_0006.html





Description

Modifyinganautomatedbackuppolicy

dds:instance:modifyBackupPolicy


projects

-

Renaminga DBinstance

dds:instance:modify


projects

-

Changing aprivate IPaddress

● dds:instance:modifyVIP

● vpc:subnets:get

● vpc:ports:get


projects

Before changing the privateIP address, query available IPaddresses.

Changingtheparametertemplateassociatedwith thenode in aDB instance

dds:instance:modifyParameter


projects

-

Showingoriginalslow logs

dds:instance:modifySlowLogPlaintextSwitch


projects

-

Enabling ordisablinglocal logauditing

dds:instances:modifyAuditLogSwitch


projects

-

Downloading auditlogs

dds:instances:downloadAuditLog


projects

-

Deletingaudit logs

dds:instance:deleteAuditLog


projects

-




Description

Downloading abackup file

dds:backup:download


projects

-

Changingthe billingmode frompay-per-useto yearly/monthly

dds:instances:renew


projects

-

Creating aManualBackup

dds:instance:createManualBackup


projects

-

Queryingthe backuplist

dds:backup:list Supported:● IAM projects● Enterprise

projects

-

Restoringdata to anew DBinstance

● dds:backup:createInstanceFromBackup


get● vpc:security



projects

The KMS Administratorpermission needs to beconfigured for the encryptedinstance in the project.

Restoringto anexisting DBinstance

dds:backup:refreshInstanceFromBackup


projects

-

Deleting abackup

dds:backup:delete


projects

-




Description

Creating aparametertemplate

dds:param:create


projects

-

Viewingparametertemplates

dds:param:list Supported:● IAM projects● Enterprise

projects

-

Modifyingaparametertemplate

dds:param:modify


projects

-

Deleting aparametertemplate

dds:param:delete


projects

-

Task Centerlist

dds:task:list Supported:● IAM projects● Enterprise

projects

-

Helpful Links● What Is IAM?● Creating a User Group, a User, and Granting DDS Permissions● Permissions Policies and Supported Actions



https://support.huaweicloud.com/intl/en-us/productdesc-iam/iam_01_0026.html


https://support.huaweicloud.com/intl/en-us/api-dds/dds_api_0036.html

12 Related Services

The following figure shows the relationship between DDS and other services.

Figure 12-1 Related services

Table 12-1 Related services

Service Name Function

Elastic CloudService (ECS)

ECS provides DDS with elastic computing resources and arunning environment for DB instances.

Virtual PrivateCloud (VPC)

VPC provides DDS with elastic network resources andimplements network isolation and access control for yourDB instances.

Document Database ServiceService Overview 12 Related Services


Service Name Function

Object StorageService (OBS)

OBS stores your DDS instance backup files.

Cloud Eye Cloud Eye serves as a monitoring platform, monitoring DDSresources for you in real time. It reports alarms and issueswarnings promptly to ensure that services are runningproperly.

Cloud TraceService (CTS)

CTS records operations related to DDS, facilitating yourfurther queries, audits, and retrievals.

Data ReplicationService (DRS)

DRS smoothly migrates databases to the cloud. Sourcedatabases remain operational during migration, minimizingdowntime and impact.

Document Database ServiceService Overview 12 Related Services


A Change History

Released On Description

2021-12-30 This issue is the sixteenth official release, which incorporatesthe following changes:● Added Read Replica.● Added the pricing description of audit log storage.

2021-10-30 This issue is the fifteenth official release, which incorporates thefollowing change:Added Compatibility.

2021-04-30 This issue is the fourteenth official release, which incorporatesthe following change:Changed parameter group to parameter template.

2021-03-30 This issue is the thirteenth official release, which incorporatesthe following changes:Terminated the sale of DDS Enhanced/Enhanced II instancesthat offer vCPU-to-memory ratio of 1:2.

2020-09-30 This issue is the twelfth official release, which incorporates thefollowing changes:Supported Kunpeng-based instances of Community Edition 4.0.

2020-08-30 This issue is the eleventh official release, which incorporates thefollowing changes:Supported up to 32 mongos nodes and 32 shard nodes in eachCommunity Edition cluster instance.Supported up to 3,000 GB of the replica set storage space.

2020-02-14 This issue is the tenth official release, which incorporates thefollowing change:Modified the description of the replica set instance architecture.

Document Database ServiceService Overview A Change History


Released On Description

2019-10-18 This issue is the ninth official release, which incorporates thefollowing changes:● Added section Comparison Between DDS and On-Premises

Databases.● Updated sections Functions and Features and Typical

Application Scenarios.

2019-09-11 This issue is the eighth official release, which incorporates thefollowing changes:Supported a maximum of 16 mongos nodes and 16 shards for aCommunity Edition cluster instance.

2019-08-13 This issue is the seventh official release, which incorporates thefollowing change:Modified DB instance statuses.

2019-04-19 This issue is the sixth official release, which incorporates thefollowing changes:● Modified the description of the Community Edition cluster

instance architecture.● Modified DB instance statuses.

2019-02-15 This issue is the fifth official release, which incorporates thefollowing change:Modified DB instance statuses.

2018-09-06 This issue is the fourth official release, which incorporates thefollowing change:Modified DB instance statuses.

2018-07-02 This issue is the third official release, which incorporates thefollowing change:Supported multiple specifications.

2018-06-01 This issue is the second official release, which incorporates thefollowing change:Supported DB instances that are compatible with MongoDB 3.4Community Edition.

2018-05-04 This issue is the first official release.

Document Database ServiceService Overview A Change History
