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/azure-cache-for-redis/cache-how-to-premium-vnet.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,13 @@ ms.date: 07/22/2022
22
22
> Azure Cache for Redis now supports Azure Private Link, which simplifies the network architecture and secures the connection between endpoints in Azure. You can connect to an Azure Cache instance from your virtual network via a private endpoint, which is assigned a private IP address in a subnet within the virtual network. Azure Private Links is offered on all our tiers, includes Azure Policy support, and simplified NSG rule management. To learn more, see [Private Link Documentation](cache-private-link.md). To migrate your VNet injected caches to Private Link, see [here](cache-vnet-migration.md).
23
23
>
24
24
25
+
### Limitations of VNet injection
26
+
27
+
- Due to fragile nature network configuration, creating and maintaining virtual network configurations is often error prone and troubleshooting is challenging. Incorrect virtual network configurations can lead to various issues like obstructed metrics transmission from your cache instances, failure of replica node to replicate data from primary node, potential data loss, failure of management operations like scaling, and in the most severe scenarios, loss of availability.
28
+
- VNet injected caches are only available for Premium Azure Cache for Redis.
29
+
- When using a VNet injected cache, you must change your VNet to cache dependencies such as CRLs/PKI, AKV, Azure Storage, Azure Monitor, and more.
30
+
- You can't inject an existing Azure Cache for Redis instance into a Virtual Network. You can only select this option when you _create_ the cache.
31
+
25
32
## Set up virtual network support
26
33
27
34
Virtual network support is configured on the **New Azure Cache for Redis** pane during cache creation.
Copy file name to clipboardExpand all lines: articles/azure-cache-for-redis/cache-network-isolation.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,9 +12,9 @@ ms.date: 06/21/2023
12
12
13
13
# Azure Cache for Redis network isolation options
14
14
15
-
In this article, you’ll learn how to determine the best network isolation solution for your needs. We’ll discuss the basics of Azure Private Link, Azure Virtual Network (VNet) injection, and Azure Firewall Rules. We'll discuss their advantages and limitations.
15
+
In this article, you’ll learn how to determine the best network isolation solution for your needs. We’ll discuss the basics of Azure Private Link (recommended), Azure Virtual Network (VNet) injection, and Firewall Rules. We'll discuss their advantages and limitations.
16
16
17
-
## Azure Private Link
17
+
## Azure Private Link (recommended)
18
18
19
19
Azure Private Link provides private connectivity from a virtual network to Azure PaaS services. Private Link simplifies the network architecture and secures the connection between endpoints in Azure. Private Link also secures the connection by eliminating data exposure to the public internet.
20
20
@@ -31,9 +31,7 @@ Azure Private Link provides private connectivity from a virtual network to Azure
31
31
32
32
### Limitations of Private Link
33
33
34
-
- Network security groups (NSG) are disabled for private endpoints. However, if there are other resources on the subnet, NSG enforcement will apply to those resources.
35
-
- Currently, portal console support, import/export and persistence to firewall storage accounts aren't supported.
36
-
- To connect to a clustered cache, `publicNetworkAccess` needs to be set to `Disabled`, and there can only be one private endpoint connection.
34
+
- Currently, portal console is not supported for caches with private link.
37
35
38
36
> [!NOTE]
39
37
> When adding a private endpoint to a cache instance, all Redis traffic is moved to the private endpoint because of the DNS.
@@ -52,13 +50,14 @@ VNet is the fundamental building block for your private network in Azure. VNet e
52
50
53
51
### Limitations of VNet injection
54
52
53
+
- Due to fragile nature network configuration, creating and maintaining virtual network configurations is often error prone and troubleshooting is challenging. Incorrect virtual network configurations can lead to various issues like obstructed metrics transmission from your cache instances, failure of replica node to replicate data from primary node, potential data loss, failure of management operations like scaling, and in the most severe scenarios, loss of availability.
55
54
- VNet injected caches are only available for Premium Azure Cache for Redis.
56
55
- When using a VNet injected cache, you must change your VNet to cache dependencies such as CRLs/PKI, AKV, Azure Storage, Azure Monitor, and more.
57
-
- You can't inject an Azure Cache for Redis instance into a Virtual Network. You can only select this option when you _create_ the cache.
56
+
- You can't inject an existing Azure Cache for Redis instance into a Virtual Network. You can only select this option when you _create_ the cache.
58
57
59
-
## Azure Firewall rules
58
+
## Firewall rules
60
59
61
-
[Azure Firewall](../firewall/overview.md) is a managed, cloud-based network security service that protects your Azure VNet resources. It’s a fully stateful firewall as a service with built-in high availability and unrestricted cloud scalability. You can centrally create, enforce, and log application and network connectivity policies across subscriptions and virtual networks.
60
+
Azure Cache for Redis allows configuring Firewall rules for specifying IP address that you want to allow to connect to your Azure Cache for Redis instance.
0 commit comments