It is important for the database user to ensure data security. Data security includes data recovery without loss and database access control with confidentiality. This document introduces the specific methods to ensure data security the DocDB for MongoDB.

Cross-host Disaster Recovery

The DocDB for MongoDB adopts the three-replica structure, which includes: 1. Primary node that can provide read/write services; 2. Read-only service secondary nodes; and 3. Hidden nodes that are invisible to the user. These three nodes are located on different physical hosts.

When a single point of failure occurs in the Primary or Secondary physical machine, the system automatically switches the healthy node to the new Primary or Secondary node. Thus, it can continue to provide services, ensuring the high availability of services.

Network Isolation

The DocDB for MongoDB, created in the user's virtual network VPC, can only access the host within the same VPC by default. The network between each user's VPCs is isolated from each other, thus avoiding illegal access by other users and public network users.

Access Password

When creating a DocDB for MongoDB instance, the user needs to set the database access password that you can reset after creation. The access password is the access proof for authorized access to the database. Only by submitting the correct access password can you connect to the DocDB for MongoDB instance.

When you set the password, pay attention to the following conditions: a. Avoid a weak password: Simple combination of numbers, combination of numbers with the same account number, and proximity keys on the keyboard; b. Use a long password: Password more than 16 digits improves the database access security; c. Change the password regularly, for example, change the password once every 90 days; d. Avoid sharing the password with others, use a password not used anywhere else;

Identity and access management and Enterprise Organization and Management

• Identity and Access Management, IAM

  The identity and access management is mainly to help the user manage the privileges of access to resources under the Baidu AI Cloud account. It applies to different roles in the enterprise. Also, it can grant privileges to different staff for the use of products.

The DocDB for MongoDB supports system policy and customized policy, respectively realizing product- and instance-level access control of the DocDB for MongoDB. For specific operation methods, see the Introduction of Identity and Access Management in the operation guide.

• Enterprises organization

  If your company needs multiple separate accounts with multiple organizational hierarchies, the upper-layer account needs to control the operating privilege of the lower account. See the Enterprise Organization.

Data Backup and Restoration

Recommend you to use the mongodump for database backup and the mongorestore for restoring the backup state of the database at a certain time. Thus, it is possible to avoid the data security threat caused by the misoperation in the creation and deletion process of the DocDB for MongoDB. This backup is an off-line backup. In the backup and restoration process, the database stops providing read/write services. So, recommend you to operate at a lower peak of the business.

See Best Practices/Best Practices for MongoDB Data Backup and Restoration for more information.