Skip to content

Commit f33505a

Browse files
committed
CLI documentation for Data encryption
1 parent 250a45d commit f33505a

File tree

2 files changed

+10
-10
lines changed

2 files changed

+10
-10
lines changed

articles/mysql/howto-data-encryption-cli.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Learn how to use the Azure CLI to set up and manage data encryption for your Azu
4343
* The key must have the following attributes to use as a customer-managed key:
4444
* No expiration date
4545
* Not disabled
46-
* Able to perform get, wrap key, unwrap key operations
46+
* Perform **get**, **wrap**, **unwrap** operations
4747
4848
## Set the right permissions for key operations
4949
@@ -75,7 +75,7 @@ Learn how to use the Azure CLI to set up and manage data encryption for your Azu
7575
az mysql server key create –name <server name> -g <resource_group> --kid <key url>
7676
```
7777
78-
Key url : https://YourVaultName.vault.azure.net/keys/YourKeyName/01234567890123456789012345678901>
78+
Key url: https://YourVaultName.vault.azure.net/keys/YourKeyName/01234567890123456789012345678901>
7979
8080
## Restore or create a replica of the server
8181
@@ -86,7 +86,7 @@ After Azure Database for MySQL is encrypted with a customer's managed key stored
8686
* [Create a restore server](howto-restore-server-cli.md)
8787
* [Create a replica server](howto-read-replica-cli.md)
8888
89-
### Once the server is restored re-validate data encryption the restored server
89+
### Once the server is restored, revalidate data encryption the restored server
9090
9191
```azurecli-interactive
9292
az mysql server key create –name <server name> -g <resource_group> --kid <key url>
@@ -100,7 +100,7 @@ After Azure Database for MySQL is encrypted with a customer's managed key stored
100100
az mysql server key show --name <server name> -g <resource_group> --kid <key url>
101101
```
102102
103-
Key url : https://YourVaultName.vault.azure.net/keys/YourKeyName/01234567890123456789012345678901>
103+
Key url: https://YourVaultName.vault.azure.net/keys/YourKeyName/01234567890123456789012345678901>
104104
105105
### List the Key used
106106
@@ -123,7 +123,7 @@ Apart from the Azure portal, you can also enable data encryption on your Azure D
123123
Use one of the pre-created Azure Resource Manager templates to provision the server with data encryption enabled:
124124
[Example with Data encryption](https://github.com/Azure/azure-mysql/tree/master/arm-templates/ExampleWithDataEncryption)
125125
126-
This Azure Resource Manager template creates a Azure Database for MySQL server and uses the **KeyVault** and **Key** passed as parameters to enable data encryption on the server.
126+
This Azure Resource Manager template creates an Azure Database for MySQL server and uses the **KeyVault** and **Key** passed as parameters to enable data encryption on the server.
127127
128128
### For an existing server
129129
Additionally, you can use Azure Resource Manager templates to enable data encryption on your existing Azure Database for MySQL servers.

articles/postgresql/howto-data-encryption-cli.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Learn how to use the Azure CLI to set up and manage data encryption for your Azu
4343
* The key must have the following attributes to use as a customer-managed key:
4444
* No expiration date
4545
* Not disabled
46-
* Able to perform get, wrap key, unwrap key operations
46+
* Perform **get**, **wrap** and **unwrap** operations
4747
4848
## Set the right permissions for key operations
4949
@@ -75,7 +75,7 @@ Learn how to use the Azure CLI to set up and manage data encryption for your Azu
7575
az postgres server key create –name <server name> -g <resource_group> --kid <key url>
7676
```
7777
78-
Key url : https://YourVaultName.vault.azure.net/keys/YourKeyName/01234567890123456789012345678901>
78+
Key url: https://YourVaultName.vault.azure.net/keys/YourKeyName/01234567890123456789012345678901>
7979
8080
## Restore or create a replica of the server
8181
@@ -86,7 +86,7 @@ After Azure Database for PostgreSQL Single server is encrypted with a customer's
8686
* [Create a restore server](howto-restore-server-cli.md)
8787
* [Create a replica server](howto-read-replica-cli.md)
8888
89-
### Once the server is restored re-validate data encryption the restored server
89+
### Once the server is restored, revalidate data encryption the restored server
9090
9191
```azurecli-interactive
9292
az postgres server key create –name <server name> -g <resource_group> --kid <key url>
@@ -100,7 +100,7 @@ After Azure Database for PostgreSQL Single server is encrypted with a customer's
100100
az postgres server key show --name <server name> -g <resource_group> --kid <key url>
101101
```
102102
103-
Key url : https://YourVaultName.vault.azure.net/keys/YourKeyName/01234567890123456789012345678901>
103+
Key url: https://YourVaultName.vault.azure.net/keys/YourKeyName/01234567890123456789012345678901>
104104
105105
### List the Key used
106106
@@ -122,7 +122,7 @@ Apart from Azure portal, you can also enable data encryption on your Azure Datab
122122
Use one of the pre-created Azure Resource Manager templates to provision the server with data encryption enabled:
123123
[Example with Data encryption](https://github.com/Azure/azure-postgresql/tree/master/arm-templates/ExampleWithDataEncryption)
124124
125-
This Azure Resource Manager template creates a Azure Database for PostgreSQL Single server and uses the **KeyVault** and **Key** passed as parameters to enable data encryption on the server.
125+
This Azure Resource Manager template creates an Azure Database for PostgreSQL Single server and uses the **KeyVault** and **Key** passed as parameters to enable data encryption on the server.
126126
127127
### For an existing server
128128
Additionally, you can use Azure Resource Manager templates to enable data encryption on your existing Azure Database for PostgreSQL Single servers.

0 commit comments

Comments
 (0)