- What's New
- Function Overview
- Service Overview
-
Getting Started
- Overview
- Getting Started with Clusters
- Getting Started with Replica Sets
- Getting Started with Single Nodes
- Logging In to the DDS Console
- Example: Buying and Connecting to a DDS Instance
- Change History (Getting Started) Europe Site
-
User Guide
- Migrating Data
- Performance Tuning
- Permissions Management
- Instance Lifecycle Management
- Instance Modifications
- Data Backups
- Data Restorations
-
Parameter Template Management
- Overview
- Creating a Parameter Template
- Modifying a Parameter Template
- Viewing Parameter Change History
- Exporting a Parameter Template
- Comparing Parameter Templates
- Replicating a Parameter Template
- Resetting a Parameter Template
- Applying a Parameter Template
- Viewing Application Records of a Parameter Template
- Modifying the Description of a Parameter Template
- Deleting a Parameter Template
- Connection Management
- Database Usage
- Data Security
- Monitoring and Alarm Reporting
- Auditing
- Logs
- Task Center
- Billing
- Tags
- Quotas
- DDS Usage Suggestions
- Change History
- Developer Guide
-
Best Practices
- Overview
- Common Methods for Connecting to a DDS Instance
- How Do Replica Sets Achieve High Availability and Read/Write Splitting?
- Sharding
- How Do I Improve DDS Performance by Optimizing SQL Statements?
- How Do I Prevent the Mongos Cache Problem?
- How Do I Solve the High CPU Usage Issue?
- Creating a User and Granting the Read-Only Permission to the User
- Security White Paper
- Performance White Paper
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
-
APIs V3.0 (Recommended)
- Querying the API Version
- Querying Database Version Information
- Querying Database Specifications
- Querying the Database Disk Type
-
DB Instance Management
- Creating a DB Instance
- Restarting a DB Instance
- Deleting a DB Instance
- Querying Instances and Details
- Scaling Up Storage Space
- Adding Nodes for a Cluster Instance
- Modifying DB Instance Specifications
- Performing a Primary/Secondary Switchover in a Replica Set Instance
- Enabling or Disabling SSL
- Modifying a DB Instance Name
- Changing an Instance Description
- Changing a Database Port
- Changing a Security Group
- Binding an EIP
- Unbinding an EIP
- Changing a Private IP Address
- Creating Shard or Config IP Addresses of a Cluster Instance
- Configuring Cross-CIDR Access for a Replica Set
- Querying AZs to Which an Instance Can Be Migrated
- Migrating a DB Instance to Another AZ
- Adding Nodes to a Replica Set Instance
- Adding a Read Replica to an Instance
- Connection Management
-
Backup and Restoration
- Creating a Manual Backup
- Deleting a Manual Backup
- Querying the Backup List
- Querying an Automated Backup Policy
- Setting an Automated Backup Policy
- Restoring Data to a New DB Instance
- Obtaining the Link for Downloading a Backup File
- Querying the Restoration Time Ranges
- Obtaining the List of Databases That Can Be Restored
- Obtaining the List of Database Collections That Can Be Restored
- Restoring Data to the Original DB Instance
- Restoring Databases and Tables to a Point in Time
- Parameter Configuration
- Log Information Queries
- Tag Management
-
Managing Databases and Users
- Creating a Database User
- Creating a Database Role
- Querying Details About Database Users
- Querying the Database Role List
- Changing the Password of a Database User
- Checking the Password for Logging In to a Database
- Querying Cluster Balancing Settings
- Enabling or Disabling Cluster Balancing
- Setting the Activity Time Window for Cluster Balancing
- Deleting a Database User
- Deleting a Database Role
- Quota Management
- Task Management
- API V3 (Unavailable Soon)
- Examples
- Permissions Policies and Supported Actions
- Appendix
- Change History (European Sites)
- SDK Reference
-
FAQs
-
Product Consulting
- What Is the Relationship Between DDS and MongoDB Community Edition?
- What Are the Differences Between DDS and GaussDB(for Mongo)?
- What Precautions Should Be Taken When Using DDS?
- What Is the Availability of DDS DB Instances?
- Will My DDS DB Instances Be Affected by Other Users' DDS DB Instances?
- Does DDS Support Multi-AZ Deployment?
- Can I Change the VPC for a Created Instance?
- Can I Change the Region for a Created Instance?
- What Is Hidden Node?
- Database Versions
-
Resource and Disk Management
- Which Items Occupy the Storage Space of DDS Instances?
- Which Types of Logs and Files Occupy DDS DB Instance Storage Space?
- Why Is the Storage Space Usage Displayed on the GUI Smaller Than the Actual Usage?
- Why Does Available Disk Space Not Increase After Data Is Deleted?
- Why Is the Resident Memory of a 4 vCPUs/8 GB Memory Replica Set Instance Only 4 GB?
- Capacity Expansion and Specification Changes
-
Database Performance
- When Will a Primary/Standby Switchover Be Triggered for a Cluster or Replica Set?
- High Storage Usage
- What Is the Time Delay for Primary/Secondary Synchronization in a Replica Set?
- How Is Data Transferred Between the Primary and Secondary Nodes of a Replica Set?
- How Do I Clear an Alarm Saying the Shard Memory Usage Exceeds 90%?
- What Can I Do If a Query Error Is Reported After Data Is Written Into the DDS Cluster?
- Database Permissions
-
Creation and Deletion
- How Do I Select Instance Specifications and Nodes?
- Why Is an Instance Not Displayed on the Console After It Is Created?
- Can I Use a Template to Create DDS DB Instances?
- Why Is Data Missing from My Database?
- Will My Backups Be Deleted If I Delete My Cloud Account?
- What Are the Differences Between Instance Deletion and Unsubscription?
-
Database Connection
- What Should I Do If I Fail to Connect to a DDS Instance?
- What Can I Do If the Number of Connections of an Instance Reaches Its Maximum?
- How Do I Query and Limit the Number of Connections?
- What Should I Do If the ECS and DDS Are Deployed in Different VPCs and They Cannot Communicate with Each Other?
- Do Applications Need to Support Automatic Reconnecting to the DDS Database?
- How Do I Create and Log In to an ECS?
- Installing a Client
- Database Usage
- Database Migration
- Database Storage
- Database Parameters
- Backup and Restoration
- Network Security
- Monitoring and Alarm
- Change History (FAQs) Europe Site
-
Product Consulting
-
Troubleshooting
- DDS Instance Node Fault Handling Mechanism
- Connection Failure Message: network error while attempting to run command 'isMaster'
- Connection Failure Messages: No route to host and connection attempt failed
- Connection Failure Message: Authentication failed
- Connection Failure Message: couldn't connect to server
- Connection Failure Message: cannot list multiple servers in URL without 'replicaSet' option
- Connection Failure Message: Timeout while receiving message
- Connection Failure Message: exception: login failed and U_STRINGPREP_PROHIBITED_ERROR
- Change History (Troubleshooting) European Sites
- Videos
Security White Paper
Document Database Service (DDS) is a secure and reliable document-oriented database service provided by HUAWEI CLOUD.
HUAWEI CLOUD DDS complies with security regulations and adheres to service boundaries without touching tenants' data, adopting target industry applications to local markets, or making entity investment, all while maintaining service neutrality when operating cloud platforms and offering cloud services. DDS allows tenants to quickly provision different types of databases and supports auto scaling of compute and storage resources based on service requirements. DDS provides functions such as automated backup, manual backup, and database restoration to prevent data loss. In addition, DDS parameter groups allow tenants to optimize their databases based on their service requirements.
DDS also provides multiple features to ensure the reliability and security of tenants' databases, such as VPC, security group, permission setting, SSL connection, automated backup, manual backup, point-in-time recovery (PITR), and cross-AZ deployment.
Network Isolation
Tenants can manage IP addresses to access their databases in a VPC. DDS DB instances run in independent VPCs. Tenants can create a cross-AZ subnet group and deploy DDS high availability (HA) DB instance in this subnet group based on service requirements. After a DB instance is created, DDS will assign a subnet IP address to the DB instance. After DDS DB instances are deployed in a VPC, tenants in other VPCs can access the DB instances through a VPN. The tenants can also create an ECS in the VPC to connect the database through a private IP address. Subnet groups and security groups can be configured in combination to isolate DDS DB instances, enhancing instance security.
Access Control
DDS creates a master database account when a tenant is creating a DDS DB instance. The tenant sets the password of the master database account. This account allows tenants to operate databases on their DB instance. The master account allows tenants to operate the DDS instance databases that they have created and connect to the DDS instance databases. Tenants can also create DB instances and database subaccounts based on service plans to grant database objects to subaccounts to separate permissions. Tenants can select security groups when creating DDS DB instances and deploy instance service NICs in the target security groups. You can set inbound and outbound security group rules to control the access to and from DB instances within a VPC. Database security groups only allow database listening ports to be connected. Tenants do no need to restart DDS DB instances when configuring security groups.
Transmission Encryption
DDS DB instances support using TLS to encrypt transmission between database clients and servers. When DDS provisions DB instances, the specified Certificate Chain (CA) will generate a unique service certificate for each instance. Database clients can download the CA root certificate from the management console and provide the certificate when connecting to the database to authenticate the database server and encrypt data during transmission.
Storage Encryption
DDS supports data encryption before storage. KMS manages encryption keys.
Automated Backup and Manual Backup
DDS provides two backup and restoration methods: automated backup and manual backup. The automated backup policy is enabled by default and the backup retention period is a maximum of 732 days. After automated backup is enabled, data can be restored to a specified point in time. DDS automatically backs up data and incrementally backups operations logs every five minutes. Therefore, tenants can restore data to the status of any time before the latest incremental backup. Manual backup is a full backup of the database. These backups are stored in Huawei OBS buckets. When a tenant deletes a DB instance, the backups of the DB instance are retained in the OBS buckets. Tenants can restore data to new instances from existing backups.
Data Replication
DDS supports deployment of HA instances (clusters and replica sets). Tenants can deploy HA DB instances in a single AZ or multiple AZs. When tenants deploy HA DB instances, DDS establishes and maintains database synchronization. If the primary node fails, DDS will automatically promote the secondary node to the primary to achieve high availability.
Data Deletion
When you delete a DDS DB instance, all data stored in it will be deleted and cannot be restored.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.