Merge from Dev to appword2025

.devcontainer/Dockerfile

@@ -0,0 +1,11 @@
+FROM mcr.microsoft.com/devcontainers/anaconda:1-3
+
+# Copy environment.yml (if found) to a temp location so we update the environment. Also
+# copy "noop.txt" so the COPY instruction does not fail if no environment.yml exists.
+COPY environment.yml* .devcontainer/noop.txt /tmp/conda-tmp/
+RUN if [ -f "/tmp/conda-tmp/environment.yml" ]; then umask 0002 && /opt/conda/bin/conda env update -n base -f /tmp/conda-tmp/environment.yml; fi \
+    && rm -rf /tmp/conda-tmp
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>

.devcontainer/devcontainer.json

@@ -0,0 +1,24 @@
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
+// README at: https://github.com/devcontainers/templates/tree/main/src/anaconda
+{
+	"name": "Anaconda (Python 3)",
+	"build": {
+		"context": "..",
+		"dockerfile": "Dockerfile"
+	},
+
+	// Features to add to the dev container. More info: https://containers.dev/features.
+	// "features": {},
+
+	// Use 'forwardPorts' to make a list of ports inside the container available locally.
+	// "forwardPorts": [],
+
+	// Use 'postCreateCommand' to run commands after the container is created.
+	"postCreateCommand": "pip install -r requirements.txt -U"
+
+	// Configure tool-specific properties.
+	// "customizations": {},
+
+	// Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
+	// "remoteUser": "root"
+}

.devcontainer/noop.txt

@@ -0,0 +1,3 @@
+This file copied into the container along with environment.yml* from the parent
+folder. This file is included to prevents the Dockerfile COPY instruction from 
+failing if no environment.yml is found.

docs/class1/class1.rst

@@ -1,4 +1,4 @@
-F5 Distributed Cloud - Introduction to Deployment Models and Services
+F5 Distributed Cloud - Foundations of Delivery & Security
 =========================================================================
 
 Welcome
@@ -13,8 +13,6 @@ Objectives:
 - Gain an understanding of deploying proxy services to securely deliver an application with a public endpoint
 - Gain an understanding of viewing telemetry data and utilizing it to tune WAAP policies
 - Gain an understanding of how to deploy a site for providing connectivity to a private endpoint
-- Gain an understanding of DNS, Observability, and CDN
-- Gain an understanding of Multi-Cloud Networking (MCN) connectivity features (i.e. AWS, Azure, and Google)
 
 Lab & Tasks:
 ------------

docs/class1/lab1.rst

@@ -1,21 +1,25 @@
 Lab 1: Deploying F5 Distributed Cloud Proxy Services to Securely Deliver a Public Endpoint
 ==========================================================================================
 
-This lab will focus on the deployment and security of an existing hosted application using F5
-Distributed Cloud Platform and Services.  This lab will be deployed in a SaaS only
-configuration with no on-premises (public or private cloud) elements.  All configuration
-will be made via the F5 Distributed Cloud Console and within the F5 Distributed Cloud Global
-Network services architecture.
+You just landed a new role and your company needs you to deploy an application. They want to use F5 Distributed Cloud (F5 XC) for its access and availability globally. The developers inform you that the application lives in both AWS and in Azure.
+
+In this lab you will be creating a global application load balancer with an ingress endpoint on a F5 XC Regional Edge (RE) and will configure it with an origin server using the application's public IP in Azure. Additionally, as you test the application, you'll use the F5 XC Console to view telemetry data. The final task will be to add a Web Application Firewall (WAF) policy to protect the application from malicious attacks, and then observe the security events generated by the WAF.
+
+This lab focuses on the deployment and security of an existing hosted application using F5 XC Platform and Services. This lab will be deployed in a SaaS-only
+configuration with no on-premises (public or private datacenter) elements.  All configuration
+will be made via the F5 XC Console.
 
 For the tasks that follow, you should have already noted your individual **namespace**. If you
-failed to note it, return to the **Introduction** section of this lab, follow the instructions
-provided and note your **namespace** accordingly. The **Delegated Domain** and the F5
-Distributed Cloud **Tenant** are listed below for your convenience as they will be the same for
+failed to note it, return to the **Introduction** section of this lab, and follow the instructions
+provided and note your **namespace** accordingly. The **DNS Domain** and the F5
+XC **Tenant** are listed below for your convenience as they will be the same for
 all lab attendees.
 
-* **Delegated Domain:** *.lab-sec.f5demos.com*
+* **DNS Domain:** *\*.lab-sec.f5demos.com*
 * **F5 Distributed Cloud Tenant:** https://f5-xc-lab-sec.console.ves.volterra.io
 
+|lab000|
+
 Following the tasks in the prior **Introduction** Section, you should now be able to access the
 F5 Distributed Cloud Console, having set your Work Domain Roles and Skill levels. If you have
 not done so already, please login to your tenant for this lab and proceed to Task 1.
@@ -326,9 +330,9 @@ Monitoring dashboard, and gather security event details.
 +---------------------------------------------------------------------------------------------------------------+
 
 +---------------------------------------------------------------------------------------------------------------+
-| 7. From the **Dashboard** view, using the horizontal navigation, click **Security Analytics**.                |
+| 6. From the **Dashboard** view, using the horizontal navigation, click **Security Analytics**.                |
 |                                                                                                               |
-| 8. Note the **Chart** shows a graphical representation of all of the response codes for the selected time     |
+| 7. Note the **Chart** shows a graphical representation of all of the response codes for the selected time     |
 |                                                                                                               |
 |    frame.                                                                                                     |
 |                                                                                                               |
@@ -341,15 +345,15 @@ Monitoring dashboard, and gather security event details.
 +---------------------------------------------------------------------------------------------------------------+
 
 +---------------------------------------------------------------------------------------------------------------+
-| 9. Click the **Hide Chart** link to free up space in the browser window.                                      |
+| 8. Click the **Hide Chart** link to free up space in the browser window.                                      |
 |                                                                                                               |
-| 10. Expand your latest security event as shown.                                                               |
+| 9. Expand your latest security event as shown.                                                               |
 |                                                                                                               |
-| 11. Note the summary detail provided in the **Information** link.  The **req_id** which is synonymous with    |
+| 10. Note the summary detail provided in the **Information** link.  The **req_id** which is synonymous with    |
 |                                                                                                               |
 |    **Support ID** (filterable) from the block page.                                                           |
 |                                                                                                               |
-| 12. Scroll to the bottom of the information screen to see specific signatures detected and actions taken      |
+| 11. Scroll to the bottom of the information screen to see specific signatures detected and actions taken      |
 |                                                                                                               |
 |     during the security event.                                                                                |
 |                                                                                                               |
@@ -375,11 +379,12 @@ Monitoring dashboard, and gather security event details.
 | policy was assigned to protect the application.  Finally a sample attack was run against the application and  |
 | the security event data was reviewed within the Distributed Cloud Console.                                    |
 |                                                                                                               |
-| A brief presentation will be shared prior to the beginning of Lab 2.                                          |
 +---------------------------------------------------------------------------------------------------------------+
 | |labend|                                                                                                      |
 +---------------------------------------------------------------------------------------------------------------+
 
+.. |lab000| image:: _static/lab1-000.png
+   :width: 800px
 .. |lab001| image:: _static/lab1-001.png
    :width: 800px
 .. |lab002| image:: _static/lab1-002.png