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
Egress from an Azure Spring Apps application can be customized to fit specific scenarios. By default, Azure Spring Apps provisions a Standard SKU Load Balancer that you can set up and use for egress. However, the default setup may not meet the requirements of all scenarios. For example, public IPs may not be allowed, or more hops may be required for egress.
19
19
20
-
This article describes how to customize an instance's egress route to support custom network scenarios, including networks that disallow public IPs and require the instance to sit behind a network virtual appliance (NVA).
20
+
This article describes how to customize an instance's egress route to support custom network scenarios. For example, you might want to customize an instance's egress route for networks that disallow public IPs and require the instance to sit behind a network virtual appliance (NVA).
Copy file name to clipboardExpand all lines: articles/spring-apps/how-to-create-udr-instance.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: Control egress traffic for an Azure Spring Apps (ASA) instance
3
-
description: Learn how to control egress traffic for an Azure Spring Apps (ASA) instance
2
+
title: Control egress traffic for an Azure Spring Apps instance
3
+
description: Learn how to control egress traffic for an Azure Spring Apps instance
4
4
author: karlerickson
5
5
ms.author: yinglzh
6
6
ms.service: spring-apps
@@ -9,7 +9,7 @@ ms.date: 09/25/2021
9
9
ms.custom: devx-track-java, devx-track-azurecli
10
10
---
11
11
12
-
# Control egress traffic for an Azure Spring Apps (ASA) instance
12
+
# Control egress traffic for an Azure Spring Apps instance
13
13
14
14
**This article applies to:** ✔️ Java ✔️ C#
15
15
@@ -100,7 +100,7 @@ az network vnet subnet create \
100
100
101
101
### Create and set up an Azure Firewall with a user-defined route
102
102
103
-
To create and set up an Azure Firewall with a user-defined route, configure Azure Firewall outbound rules. The firewall lets you configure granular egress traffic rules from a Azure Spring Apps instance.
103
+
To create and set up an Azure Firewall with a user-defined route, configure Azure Firewall outbound rules. The firewall lets you configure granular egress traffic rules from an Azure Spring Apps instance.
104
104
105
105
> [!IMPORTANT]
106
106
> If your cluster or application creates a large number of outbound connections directed to the same or small subset of destinations, you might require more firewall frontend IPs to avoid reaching the maximum ports per front-end IP. For more information on how to create an Azure firewall with multiple IPs, see [Quickstart: Create an Azure Firewall with multiple public IP addresses - ARM template](../firewall/quick-create-multiple-ip-template.md). Create a standard SKU public IP resource that will be used as the Azure Firewall front-end address.
Azure automatically routes traffic between Azure subnets, virtual networks, and on-premises networks. If you want to change Azure's default routing, create a route table.
147
147
148
-
The following example shows how to create a route table to be associated with a specified subnet. The route table defines the next hop, as in the Azure Firewall you created. Each subnet can one route table associated with it, or could have no associated route table.
148
+
The following example shows how to create a route table to be associated with a specified subnet. The route table defines the next hop, as in the Azure Firewall you created. Each subnet can have one route table associated with it, or could have no associated route table.
0 commit comments