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..5bfead3 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,23 @@ 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. Disk encryption will not encrypt backup data stored in OBS. | + | | | + | | - 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 disk encryption is enabled but backup data encryption is not enabled, you can :ref:`restore data to a new instance from backups `. | + | | | + | | 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..f03a820 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,23 @@ 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. Disk encryption will not encrypt backup data stored in OBS. | + | | | + | | - 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 disk encryption is enabled but backup data encryption is not enabled, you can :ref:`restore data to a new instance from backups `. | + | | | + | | 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..530a834 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,23 @@ 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. Disk encryption will not encrypt backup data stored in OBS. | + | | | + | | - 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 disk encryption is enabled but backup data encryption is not enabled, you can :ref:`restore data to a new instance from backups `. | + | | | + | | 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..c928e2c 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,23 @@ 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. Disk encryption will not encrypt backup data stored in OBS. | + | | | + | | - 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 disk encryption is enabled but backup data encryption is not enabled, you can :ref:`restore data to a new instance from backups `. | + | | | + | | 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..0d31958 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,16 @@ 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. Disk encryption will not encrypt backup data stored in OBS. | + | | | + | | - 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 disk encryption is enabled but backup data encryption is not enabled, you can :ref:`restore data to a new instance from backups `. | + | | | + | | 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..a894cec 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,16 @@ 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. Disk encryption will not encrypt backup data stored in OBS. | + | | | + | | - 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 disk encryption is enabled but backup data encryption is not enabled, you can :ref:`restore data to a new instance from backups `. | + | | | + | | 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*. | +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+