You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/redis/scripts/create-manage-cache.md
+9-10Lines changed: 9 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,9 @@ The scripts in this article use the following commands. Select the links in the
21
21
22
22
::: zone pivot="azure-managed-redis"
23
23
24
+
>[!NOTE]
25
+
>The [az redisenterprise](/cli/azure/redisenterprise) commands are part of the `redisenterprise` extension for the Azure CLI, version 2.61.0 or higher. The extension automatically installs the first time you run an `az redisenterprise` command.
26
+
24
27
| Command | Description |
25
28
|---|---|
26
29
|[az group create](/cli/azure/group)| Creates a resource group to store all resources in. |
@@ -29,9 +32,6 @@ The scripts in this article use the following commands. Select the links in the
29
32
|[az redisenterprise list-keys](/cli/azure/redis)| Lists access keys for an Azure Managed Redis instance. |
30
33
|[az redisenterprise delete](/cli/azure/redis)| Deletes an Azure Managed Redis instance. |
31
34
32
-
>[!NOTE]
33
-
>The [az redisenterprise](/cli/azure/redisenterprise) commands are part of the `redisenterprise` extension for the Azure CLI, version 2.61.0 or higher. The extension automatically installs the first time you run an `az redisenterprise` command.
34
-
35
35
::: zone-end
36
36
37
37
::: zone pivot="azure-cache-redis"
@@ -60,8 +60,6 @@ The scripts in this article use the following commands. Select the links in the
60
60
This sample is broken. When it is fixed, we can fix this include.
61
61
-->
62
62
63
-
The following example script sets variables, then creates a resource group and an Azure Managed Redis cache in the resource group. Putting all your app resources in the same resource group lets you easily manage or delete them together.
64
-
65
63
The cache `name` must be a string of 1-63 characters that's unique in the region. The name can contain only numbers, letters, and hyphens, must start and end with a number or letter, and can't contain consecutive hyphens.
66
64
67
65
The `location` should be an [Azure region](https://azure.microsoft.com/regions/) near other services that use your cache. Use a cache [sku](https://azure.microsoft.com/pricing/details/cache/) and `size` that have the appropriate features and performance for your cache.
@@ -74,11 +72,13 @@ The `location` should be an [Azure region](https://azure.microsoft.com/regions/)
74
72
>- If you're using the cache in a geo-replication group, you can't change eviction policies after the cache is created.
75
73
>- If you're using the [RediSearch](../redis-modules.md#redisearch) module, the Enterprise cluster policy is required, and No Eviction is the only eviction policy supported.
76
74
77
-
For security reasons, Microsoft Entra authentication and Transport Layer Security (TLS) encryption are enabled by default for new caches. Access keys authentication is disabled. You can choose to to enable access key authentication or non-TLS connections during or after cache creation, but disabling TLS isn't recommended.
75
+
For security reasons, Microsoft Entra authentication and Transport Layer Security (TLS) encryption are enabled by default for new caches. Access keys authentication is disabled. You can choose to to enable access key authentication or non-TLS connections during or after cache creation.
78
76
79
77
>[!IMPORTANT]
80
78
>Use Microsoft Entra ID with managed identities to authorize requests against your cache if possible. Authorization using Microsoft Entra ID and managed identity provides better security and is easier to use than shared access key authorization. For more information about using managed identities with your cache, see [Use Microsoft Entra ID for cache authentication](../../azure-cache-for-redis/cache-azure-active-directory-for-authentication.md).
81
79
80
+
The following example script sets variables, then creates a resource group and an Azure Managed Redis cache in the resource group. Putting all your app resources in the same resource group lets you easily manage or delete them together.
81
+
82
82
```azurecli
83
83
84
84
# Variable block
@@ -148,17 +148,16 @@ az group delete --resource-group $resourceGroup -y
148
148
This sample is broken. When it is fixed, we can fix this include.
149
149
-->
150
150
151
-
The following example script sets variables, then creates a resource group and an Azure Cache for Redis cache in the resource group. Putting all your app resources in the same resource group lets you easily manage or delete them together.
152
-
153
151
The cache `name` must be a string of 1-63 characters that's unique in the region. It can contain only numbers, letters, and hyphens, must start and end with a number or letter, and can't contain consecutive hyphens.
154
152
155
153
The `location` should be an [Azure region](https://azure.microsoft.com/regions/) near other services that use your cache. Use a cache [sku](https://azure.microsoft.com/pricing/details/cache/) and `size` that have the appropriate features and performance for your cache.
156
154
157
155
For security reasons, Microsoft Entra Authentication and TLS encryption are enabled by default for new caches. You can choose to enable access key authentication or non-TLS connections during or after cache creation.
158
156
159
157
>[!IMPORTANT]
160
-
>
161
-
Use Microsoft Entra ID with managed identities to authorize requests against your cache if possible. Authorization using Microsoft Entra ID and managed identity provides better security and is easier to use than shared access key authorization. For more information about using managed identities with your cache, see [Use Microsoft Entra ID for cache authentication](../../azure-cache-for-redis/cache-azure-active-directory-for-authentication.md).
158
+
>Use Microsoft Entra ID with managed identities to authorize requests against your cache if possible. Authorization using Microsoft Entra ID and managed identity provides better security and is easier to use than shared access key authorization. For more information about using managed identities with your cache, see [Use Microsoft Entra ID for cache authentication](../../azure-cache-for-redis/cache-azure-active-directory-for-authentication.md).
159
+
160
+
The following example script sets variables, then creates a resource group and an Azure Cache for Redis cache in the resource group. Putting all your app resources in the same resource group lets you easily manage or delete them together.
0 commit comments