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/container-apps/waf-app-gateway.md
+22-5Lines changed: 22 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,13 +5,13 @@ services: container-apps
5
5
author: cachai2
6
6
ms.service: azure-container-apps
7
7
ms.topic: how-to
8
-
ms.date: 03/31/2023
8
+
ms.date: 03/06/2025
9
9
ms.author: cachai
10
10
---
11
11
12
12
# Protect Azure Container Apps with Web Application Firewall on Application Gateway
13
13
14
-
When you host your apps or microservices in Azure Container Apps, you may not always want to publish them directly to the internet. Instead, you may want to expose them through a reverse proxy.
14
+
When you host your apps or microservices in Azure Container Apps, you might not always want to publish them directly to the internet. Instead, you might want to expose them through a reverse proxy.
15
15
16
16
A reverse proxy is a service that sits in front of one or more services, intercepting and directing incoming traffic to the appropriate destination.
17
17
@@ -48,6 +48,8 @@ Use the following steps to retrieve the values of the **default domain** and the
48
48
49
49
## Create and configure an Azure Private DNS zone
50
50
51
+
To create and configure an Azure Private DNS zone, perform the following steps:
52
+
51
53
1. On the Azure portal menu or the *Home* page, select **Create a resource**.
52
54
53
55
1. Search for *Private DNS Zone*, and select **Private DNS Zone** from the search results.
@@ -110,8 +112,17 @@ Use the following steps to retrieve the values of the **default domain** and the
110
112
111
113
## Create and configure Azure Application Gateway
112
114
115
+
To create and configure an Azure Application Gateway, perform the following steps:
116
+
117
+
1. On the Azure portal menu or the *Home* page, select **Create a resource**.
118
+
1. Search for *Application Gateway*, and select **Application Gateway** from the search results.
119
+
120
+
Now, enter the required details under the *Basics* tab, *Frontends* tab, *Backends* tab, and *Configuration* tab.
121
+
113
122
### Basics tab
114
123
124
+
Perform the following steps:
125
+
115
126
1. Enter the following values in the *Project details* section.
116
127
117
128
| Setting | Action |
@@ -151,6 +162,8 @@ Use the following steps to retrieve the values of the **default domain** and the
151
162
152
163
### Frontends tab
153
164
165
+
Perform the following steps:
166
+
154
167
1. On the *Frontends* tab, enter the following values:
155
168
156
169
| Setting | Action |
@@ -174,7 +187,9 @@ The backend pool is used to route requests to the appropriate backend servers. B
174
187
- Fully qualified domain names (FQDN)
175
188
- Multi-tenant back-ends like Azure App Service and Container Apps
176
189
177
-
In this example, you create a backend pool that targets your container app.
190
+
In this example, you create a backend pool that targets your container app.
191
+
192
+
To create a backend pool, perform the following steps:
178
193
179
194
1. Select **Add a backend pool**.
180
195
@@ -197,7 +212,9 @@ In this example, you create a backend pool that targets your container app.
197
212
198
213
### Configuration tab
199
214
200
-
On the *Configuration* tab, you connect the frontend and backend pool you created using a routing rule.
215
+
On the *Configuration* tab, you connect the frontend and backend pool you created using a routing rule.
216
+
217
+
To connect the frontend and backend pool, perform the following steps:
201
218
202
219
1. Select **Add a routing rule**. Enter the following values:
203
220
@@ -266,7 +283,7 @@ On the *Configuration* tab, you connect the frontend and backend pool you create
266
283
267
284
## Add private link to your Application Gateway
268
285
269
-
You can establish a secured connection to internal-only container app environments by leveraging private link, as it allows your Application Gateway to communicate with your Container App on the backend through the virtual network.
286
+
You can establish a secured connection to internal-only container app environments using private link. Private link allows your Application Gateway to communicate with your Container App on the backend through the virtual network.
270
287
271
288
1. Once the Application Gateway is created, select **Go to resource**.
0 commit comments