diff --git a/umn/source/_static/images/en-us_image_0000001835388741.png b/umn/source/_static/images/en-us_image_0000001835388741.png new file mode 100644 index 0000000..f9b1781 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001835388741.png differ diff --git a/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_private_networks/creating_a_cluster_instance.rst b/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_private_networks/creating_a_cluster_instance.rst index 25899db..3bdf5a0 100644 --- a/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_private_networks/creating_a_cluster_instance.rst +++ b/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_private_networks/creating_a_cluster_instance.rst @@ -60,15 +60,21 @@ Procedure +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Disk Encryption | - **Disabled**: Disable the encryption function. | | | | - | | - **Enabled**: Enable the encryption function. This feature improves data security but slightly affects read/write performance. | + | | - **Enabled**: Enable encryption. This feature improves data security but slightly affects read/write performance. | | | | | | **Key Name**: Select or create a private key, which is the tenant key. | | | | - | | .. note:: | + | | .. note:: | | | | - | | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. | - | | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. | - | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | + | | - After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted. | + | | | + | | - To check whether the disk is encrypted, you can view **Disk Encrypted** in the DB instance list. | + | | | + | | - If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored. | + | | | + | | If both disk encryption and backup data encryption are enabled, data cannot be restored. | + | | | + | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ .. table:: **Table 2** Specifications diff --git a/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_public_networks/creating_a_cluster_instance.rst b/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_public_networks/creating_a_cluster_instance.rst index 4033bcf..9743d00 100644 --- a/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_public_networks/creating_a_cluster_instance.rst +++ b/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_public_networks/creating_a_cluster_instance.rst @@ -60,15 +60,21 @@ Procedure +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Disk Encryption | - **Disabled**: Disable the encryption function. | | | | - | | - **Enabled**: Enable the encryption function. This feature improves data security but slightly affects read/write performance. | + | | - **Enabled**: Enable encryption. This feature improves data security but slightly affects read/write performance. | | | | | | **Key Name**: Select or create a private key, which is the tenant key. | | | | - | | .. note:: | + | | .. note:: | | | | - | | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. | - | | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. | - | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | + | | - After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted. | + | | | + | | - To check whether the disk is encrypted, you can view **Disk Encrypted** in the DB instance list. | + | | | + | | - If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored. | + | | | + | | If both disk encryption and backup data encryption are enabled, data cannot be restored. | + | | | + | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ .. table:: **Table 2** Specifications diff --git a/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_private_networks/creating_a_replica_set_instance.rst b/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_private_networks/creating_a_replica_set_instance.rst index 75f0f2c..e408149 100644 --- a/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_private_networks/creating_a_replica_set_instance.rst +++ b/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_private_networks/creating_a_replica_set_instance.rst @@ -62,15 +62,21 @@ You can use your account to create up to 50 replica set instances. To create mor +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Disk Encryption | - **Disabled**: Disable the encryption function. | | | | - | | - **Enabled**: Enable the encryption function. This feature improves data security but slightly affects read/write performance. | + | | - **Enabled**: Enable encryption. This feature improves data security but slightly affects read/write performance. | | | | | | **Key Name**: Select or create a private key, which is the tenant key. | | | | - | | .. note:: | + | | .. note:: | | | | - | | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. | - | | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. | - | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | + | | - After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted. | + | | | + | | - To check whether the disk is encrypted, you can view **Disk Encrypted** in the DB instance list. | + | | | + | | - If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored. | + | | | + | | If both disk encryption and backup data encryption are enabled, data cannot be restored. | + | | | + | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ .. table:: **Table 2** Specifications diff --git a/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_public_networks/creating_a_replica_set_instance.rst b/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_public_networks/creating_a_replica_set_instance.rst index 0ccf108..3ac95ff 100644 --- a/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_public_networks/creating_a_replica_set_instance.rst +++ b/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_public_networks/creating_a_replica_set_instance.rst @@ -62,15 +62,21 @@ You can use your account to create up to 50 replica set instances. To create mor +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Disk Encryption | - **Disabled**: Disable the encryption function. | | | | - | | - **Enabled**: Enable the encryption function. This feature improves data security but slightly affects read/write performance. | + | | - **Enabled**: Enable encryption. This feature improves data security but slightly affects read/write performance. | | | | | | **Key Name**: Select or create a private key, which is the tenant key. | | | | - | | .. note:: | + | | .. note:: | | | | - | | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. | - | | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. | - | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | + | | - After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted. | + | | | + | | - To check whether the disk is encrypted, you can view **Disk Encrypted** in the DB instance list. | + | | | + | | - If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored. | + | | | + | | If both disk encryption and backup data encryption are enabled, data cannot be restored. | + | | | + | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ .. table:: **Table 2** Specifications diff --git a/umn/source/getting_started_with_single_nodes/connecting_to_a_single-node_instance_over_private_networks/creating_a_single_node_instance.rst b/umn/source/getting_started_with_single_nodes/connecting_to_a_single-node_instance_over_private_networks/creating_a_single_node_instance.rst index 3890a94..606c3a7 100644 --- a/umn/source/getting_started_with_single_nodes/connecting_to_a_single-node_instance_over_private_networks/creating_a_single_node_instance.rst +++ b/umn/source/getting_started_with_single_nodes/connecting_to_a_single-node_instance_over_private_networks/creating_a_single_node_instance.rst @@ -66,8 +66,14 @@ Procedure | | | | | .. note:: | | | | - | | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. | - | | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. | + | | - After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted. | + | | | + | | - To check whether the disk is encrypted, you can view **Disk Encrypted** in the DB instance list. | + | | | + | | - If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored. | + | | | + | | If both disk encryption and backup data encryption are enabled, data cannot be restored. | + | | | | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/getting_started_with_single_nodes/connecting_to_a_single_node_instance_over_public_networks/creating_a_single_node_instance.rst b/umn/source/getting_started_with_single_nodes/connecting_to_a_single_node_instance_over_public_networks/creating_a_single_node_instance.rst index b8e5324..1d06c09 100644 --- a/umn/source/getting_started_with_single_nodes/connecting_to_a_single_node_instance_over_public_networks/creating_a_single_node_instance.rst +++ b/umn/source/getting_started_with_single_nodes/connecting_to_a_single_node_instance_over_public_networks/creating_a_single_node_instance.rst @@ -66,8 +66,14 @@ Procedure | | | | | .. note:: | | | | - | | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. | - | | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. | + | | - After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted. | + | | | + | | - To check whether the disk is encrypted, you can view **Disk Encrypted** in the DB instance list. | + | | | + | | - If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored. | + | | | + | | If both disk encryption and backup data encryption are enabled, data cannot be restored. | + | | | | | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/introduction/index.rst b/umn/source/introduction/index.rst index e479a6d..1b9346b 100644 --- a/umn/source/introduction/index.rst +++ b/umn/source/introduction/index.rst @@ -15,6 +15,7 @@ Introduction - :ref:`User Permissions ` - :ref:`Permissions Management ` - :ref:`Related Services ` +- :ref:`Mapping Between DDS Versions and Community Versions ` .. toctree:: :maxdepth: 1 @@ -30,3 +31,4 @@ Introduction user_permissions permissions_management related_services + mapping_between_dds_versions_and_community_versions diff --git a/umn/source/introduction/mapping_between_dds_versions_and_community_versions.rst b/umn/source/introduction/mapping_between_dds_versions_and_community_versions.rst new file mode 100644 index 0000000..0d36e51 --- /dev/null +++ b/umn/source/introduction/mapping_between_dds_versions_and_community_versions.rst @@ -0,0 +1,20 @@ +:original_name: dds_01_0060.html + +.. _dds_01_0060: + +Mapping Between DDS Versions and Community Versions +=================================================== + +Document Database Service (DDS) is a cloud database service compatible with MongoDB. DDS major versions select community versions that have not reached EOL and have new major functions as candidate versions for compatibility. The DDS version does not correspond to the community version. To help you understand the mapping between DDS versions and community versions, DDS uses compatible community versions. For details, see :ref:`Figure 1 `. + +.. _dds_01_0060__fig12011574199: + +.. figure:: /_static/images/en-us_image_0000001835388741.png + :alt: **Figure 1** Mapping between DDS versions and community versions + + **Figure 1** Mapping between DDS versions and community versions + +- DDS 3.4 and 4.0 are developed based on the corresponding community versions. The implementation of the same interface is consistent with that in the community. Compared with a community version, DDS has higher security and more O&M functions. DDS can better meet commercial application requirements. +- After October 16, 2018, DDS 4.0 uses the community version 4.0.3 as the baseline version. New features are independently developed and evolved. +- DDS 4.2 and later versions use the community version 4.0.3 as the baseline version. New features are independently developed and evolved. The storage engine is switched to RocksDB to provide better user experience. +- DDS source code has been opened in the GitHub community. For details, see https://github.com/hwCloudDBSDDS/dds.