@@ -16,7 +16,7 @@ Your design includes the following workflow Client -> RE -> CE -> Protected appl
16
16
17
17
18
18
Task 1. Create Private Origin Pool
19
- ---------------------------
19
+ ----------------------------------
20
20
21
21
In Lab #1 we created an origin pool that was accessible via the Public Internet.
22
22
This lab exercise will create an origin pool that is also accessible via the Public Internet; in this case the application is local to the deployed
@@ -132,7 +132,7 @@ Now we will deploy a Load Balancer on the CE node that was deployed in the AWS V
132
132
+-----------------------------------------------------------------------------------------------------------------------------------+
133
133
134
134
Task 3: Configure WAF Policy
135
- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
135
+ ----------------------------
136
136
Now that we have our load balancer and orign server configured we want to make sure we are protecting the origin server. Here we
137
137
are easily applying a pre-existing shared WAF policy to our loadbalancer. The shared WAF policy is available for all namespaces
138
138
under this tenant.
@@ -163,7 +163,7 @@ under this tenant.
163
163
+-----------------------------------------------------------------------------------------------------------------------------------+
164
164
165
165
Task 4: Verify Configuration
166
- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
166
+ -----------------------------
167
167
168
168
You should now be able to go to the DNS name that you created in this Load Balancer configuration.
169
169
The FQDN we used in our example is http://[NAMESPACE]-2.lab-sec.f5demos.com/.
@@ -178,7 +178,7 @@ The FQDN we used in our example is http://[NAMESPACE]-2.lab-sec.f5demos.com/.
178
178
179
179
180
180
Task 5: Verify WAF Protection
181
- ^^^^^^^^^^^^^^^^^^^^^^
181
+ ------------------------------
182
182
183
183
In this topology we are sending traffic to the application via the public IP advertised on *XC *, which then sends to the application
184
184
in AWS via the connection to the CE node in AWS.
@@ -197,8 +197,7 @@ in AWS via the connection to the CE node in AWS.
197
197
+-----------------------------------------------------------------------------------------------------------------------------------+
198
198
199
199
+-----------------------------------------------------------------------------------------------------------------------------------+
200
- | |
201
- | This concludes lab 2. In this lab you configured a global load balancer with a WAF policy on a CE node running in AWS for a |
200
+ | **End of Lab 2 **. In this lab you configured a global load balancer with a WAF policy on a CE node running in AWS for a |
202
201
| private end point. That private end point was only accessible via the global load balancer. |
203
202
| |
204
203
| |labend | |
@@ -226,7 +225,7 @@ in AWS via the connection to the CE node in AWS.
226
225
:width: 800px
227
226
.. |lab310 | image :: _static/lab3-appworld2025-waf-block-message.png
228
227
:width: 800px
229
- .. |lab311 | image :: _static/lab3 -appworld2025-task2-lb-updated .png
228
+ .. |lab311 | image :: _static/lab2 -appworld2025-task2-lb.png
230
229
:width: 800px
231
230
.. |lab312 | image :: _static/screenshot-global-vip-private.png
232
231
:width: 800px
0 commit comments