Skip to content

Commit ad0cbaf

Browse files
authored
Merge pull request #235 from curtkersey/dev
Updated lab 2 - diagram; more to come.
2 parents 8e2d4d1 + 18ba17e commit ad0cbaf

File tree

2 files changed

+6
-7
lines changed

2 files changed

+6
-7
lines changed
53.8 KB
Loading

docs/class1/lab2.rst

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Your design includes the following workflow Client -> RE -> CE -> Protected appl
1616

1717

1818
Task 1. Create Private Origin Pool
19-
---------------------------
19+
----------------------------------
2020

2121
In Lab #1 we created an origin pool that was accessible via the Public Internet.
2222
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
132132
+-----------------------------------------------------------------------------------------------------------------------------------+
133133

134134
Task 3: Configure WAF Policy
135-
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
135+
----------------------------
136136
Now that we have our load balancer and orign server configured we want to make sure we are protecting the origin server. Here we
137137
are easily applying a pre-existing shared WAF policy to our loadbalancer. The shared WAF policy is available for all namespaces
138138
under this tenant.
@@ -163,7 +163,7 @@ under this tenant.
163163
+-----------------------------------------------------------------------------------------------------------------------------------+
164164

165165
Task 4: Verify Configuration
166-
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
166+
-----------------------------
167167

168168
You should now be able to go to the DNS name that you created in this Load Balancer configuration.
169169
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/.
178178

179179

180180
Task 5: Verify WAF Protection
181-
^^^^^^^^^^^^^^^^^^^^^^
181+
------------------------------
182182

183183
In this topology we are sending traffic to the application via the public IP advertised on *XC*, which then sends to the application
184184
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.
197197
+-----------------------------------------------------------------------------------------------------------------------------------+
198198

199199
+-----------------------------------------------------------------------------------------------------------------------------------+
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 |
202201
| private end point. That private end point was only accessible via the global load balancer. |
203202
| |
204203
| |labend| |
@@ -226,7 +225,7 @@ in AWS via the connection to the CE node in AWS.
226225
:width: 800px
227226
.. |lab310| image:: _static/lab3-appworld2025-waf-block-message.png
228227
:width: 800px
229-
.. |lab311| image:: _static/lab3-appworld2025-task2-lb-updated.png
228+
.. |lab311| image:: _static/lab2-appworld2025-task2-lb.png
230229
:width: 800px
231230
.. |lab312| image:: _static/screenshot-global-vip-private.png
232231
:width: 800px

0 commit comments

Comments
 (0)