Epic 472 port nginx one labs

content/includes/config-snippets/enable-nplus-api-dashboard.md

@@ -34,4 +34,4 @@ server {
         root /usr/share/nginx/html;
     }
 }
-```
+```

content/includes/nginx-one/cloud-access-nginx.md

@@ -1,11 +1,12 @@
 ---
 files:
-  - content/nginx-one/secure-your-fleet/set-up-security-alerts.md
   - content/nginx-one/getting-started.md
 ---
 
-Once you've logged in with your password, you should be able to see and select the NGINX One tile. 
+1. Go to `https://<TENANT_NAME>.console.ves.volterra.io/` to access F5 Distributed Cloud, and sign in.
 
-1. Select the **NGINX One** tile
-1. If needed, select **Enable Service**
-1. After the service has been enables, select **Visit Service** to load NGINX One Console
+   After you sign in, you should see the **NGINX One** tile.
+
+1. Select the **NGINX One** tile.
+1. If needed, select **Enable Service**.
+1. After the service is enabled, select **Visit Service** to open NGINX One Console.

content/includes/nginx-one/cloud-access.md

@@ -4,8 +4,15 @@ files:
   - content/nginx-one/getting-started.md
 ---
 
-Confirm an F5 Distributed Cloud tenant has been provisioned for you. Log in to MyF5 and review your subscriptions. You should see within one of your subscriptions "Distributed Cloud". This could be in either an NGINX subscription or a Distributed Cloud. If the above does not appear in any of your subscriptions, reach out to either your F5 Account Team or Customer Success Manager.
+Confirm that an F5 Distributed Cloud tenant has been provisioned for you.
 
-With access, you or someone in your organization should have an email from no-reply@cloud.f5.com asking you to update your password when the tenant was created. The account name referenced in the E-Mail in bold is the tenant name.
+1. Log in to [MyF5](https://my.f5.com/manage/s/) and review your subscriptions.
+2. Look for **Distributed Cloud** in one of your subscriptions. This could appear under an NGINX subscription or a Distributed Cloud subscription.
 
-Navigate to https://INSERT_YOUR_TENANT_NAME.console.ves.volterra.io/ to access F5 Distributed Cloud. If you have never logged in, select the **Forgot Password?** option in the log in screen. Alternatively, if someone within your organization has access, ask them to add you as a user within your tenant with a role providing permissions for NGINX One.
+If you don’t see **Distributed Cloud** in any subscription, contact your F5 account team or Customer Success Manager.
+
+When your tenant is created, you or someone in your organization should receive an email from **no-reply@cloud.f5.com** asking you to set your password. The account name in bold in the email is your tenant name.
+
+Go to `https://<TENANT_NAME>.console.ves.volterra.io/` to access F5 Distributed Cloud.  
+If you have never signed in, select **Forgot Password?** on the sign-in page.  
+Alternatively, ask someone in your organization with access to add you as a user in your tenant with a role that includes permissions for NGINX One Console.

content/includes/use-cases/monitoring/enable-nginx-plus-api-with-config-sync-group.md

@@ -0,0 +1,18 @@
+---
+docs:
+files:
+-
+-
+---
+
+1. In the NGINX One Console, select **Manage > Config Sync Groups**, then pick your config sync group's name.  
+2. Select the **Configuration** tab, then select **Edit Configuration**.  
+3. Select **Add File**.  
+4. Select **New Configuration File**.  
+5. In the **File name** box, enter `/etc/nginx/conf.d/dashboard.conf`, then select **Add**.  
+6. Paste the following into the new file workspace:
+
+{{< include "config-snippets/enable-nplus-api-dashboard.md" >}}
+
+7. Select **Next**, review the diff, then select **Save and Publish**.
+8. Open your browser to `http://<instance-ip>:9000/dashboard.html` (replace `<instance-ip>` with the IP or hostname of one of your group members). You should see the NGINX Plus dashboard.

content/includes/use-cases/monitoring/enable-nginx-plus-api.md

@@ -15,4 +15,4 @@ To collect comprehensive metrics for NGINX Plus, including bytes streamed, infor
 - To restrict write methods (`POST`, `PATCH`, `DELETE`), uncomment and configure the `limit_except GET` block and set up [HTTP basic authentication](https://nginx.org/en/docs/http/ngx_http_auth_basic_module.html).  
 {{</ call-out >}}
 
-For more details, see the [NGINX Plus API module](https://nginx.org/en/docs/http/ngx_http_api_module.html) documentation and [Configuring the NGINX Plus API]({{< ref "/nginx/admin-guide/monitoring/live-activity-monitoring.md#configuring-the-api" >}}).
+For more details, see the [NGINX Plus API module](https://nginx.org/en/docs/http/ngx_http_api_module.html) documentation and [Configuring the NGINX Plus API]({{< ref "/nginx/admin-guide/monitoring/live-activity-monitoring.md#configuring-the-api" >}}).

content/includes/workshops/nginx-one-env-variables.md

@@ -0,0 +1,27 @@
+---
+docs:
+files:
+- content/nginx-one/workshops/lab4/config-sync-groups.md
+- content/nginx-one/workshops/lab5/upgrade-nginx-plus-to-r34.md
+
+---
+
+Set these environment variables:
+
+- **TOKEN**: your data plane key, for example:
+
+   ```shell
+   export TOKEN="your-data-plane-key"
+   ```
+
+- **JWT**: your NGINX Plus license JWT. Save it as `nginx-repo.jwt`, then run:
+
+   ```shell
+   export JWT=$(cat path/to/nginx-repo.jwt)
+   ```
+
+- **NAME**: a unique ID for your workshop (for example, `s.jobs`):
+
+   ```shell
+   export NAME="s.jobs"
+   ```

content/nginx-one/_index.md

@@ -25,12 +25,6 @@ F5 NGINX One Console makes it easy to manage NGINX instances across locations an
     {{<card title="Get started" titleUrl="/nginx-one/getting-started/" icon="unplug" isFullSize="true">}}
       Get up and running with NGINX One Console
     {{</card >}}
-  {{</card-section>}}
-{{</card-layout>}}
-
-
-{{<card-layout>}}
-  {{<card-section showAsCards="true" >}}
     {{<card title="Connect more NGINX instances" titleUrl="/nginx-one/connect-instances/" >}}
       Work with data plane keys, containers, and proxy servers
     {{</card>}}
@@ -46,6 +40,16 @@ F5 NGINX One Console makes it easy to manage NGINX instances across locations an
   {{</card-section>}}
 {{</card-layout>}}
 
+### Workshops
+
+{{<card-layout>}}
+  {{<card-section showAsCards="true">}}
+    {{<card title="NGINX One Console workshops" titleUrl="/nginx-one/workshops/" icon="wrench" >}}
+      Learn how to register and manage NGINX instances in NGINX One Console. View CVE and configuration recommendations. Use Config Sync Groups to deploy JWT licenses and upgrade to the latest NGINX Plus.
+    {{</card>}}
+  {{</card-section>}}
+{{</card-layout>}}
+
 ### More information
 
 {{<card-layout>}}

content/nginx-one/nginx-configs/metrics/enable-metrics.md

@@ -14,10 +14,16 @@ nd-product: NGINX-One
 
 The NGINX One Console dashboard relies on APIs for NGINX Plus and NGINX Open Source Stub Status to report traffic and system metrics. The following sections show you how to enable those metrics.
 
-### Enable NGINX Plus API
+## Enable NGINX Plus API and dashboard
 
 {{< include "/use-cases/monitoring/enable-nginx-plus-api.md" >}}
 
-### Enable NGINX Open Source Stub Status API 
+## Enable NGINX Plus API and dashboard with Config Sync Groups
+
+To enable the NGINX Plus API and dashboard with [Config Sync Groups]({{< ref "nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md" >}}), add a file named `/etc/nginx/conf.d/dashboard.conf` to your shared group config. Any instance you add to that group automatically uses those settings.
+
+{{< include "use-cases/monitoring/enable-nginx-plus-api-with-config-sync-group.md" >}}
+
+## Enable NGINX Open Source Stub Status API 
 
 {{< include "/use-cases/monitoring/enable-nginx-oss-stub-status.md" >}}

content/nginx-one/workshops/_index.md

@@ -0,0 +1,6 @@
+---
+title: Workshops
+description:
+weight: 750
+url: /nginx-one/workshops
+---

content/nginx-one/workshops/lab1/getting-started-with-nginx-one.md

@@ -0,0 +1,121 @@
+---
+title: "Lab 1: Get started with NGINX One Console"
+weight: 100
+toc: true
+nd-content-type: tutorial
+nd-product: NGINX-ONE
+---
+
+## Introduction
+
+In this lab, you’ll log in to NGINX One Console, explore its main features, and create a data plane key to register NGINX instances.
+
+NGINX One Console is a cloud service in the F5 Distributed Cloud platform. It lets you:
+
+- Manage all NGINX instances in one place
+- Monitor performance and health metrics
+- Detect security risks like expired SSL certificates or known vulnerabilities
+- Track software versions
+- Get performance tips
+
+Instead of switching between tools, you get one dashboard with real-time data and alerts.
+
+---
+
+## What you’ll learn
+
+By the end of this tutorial, you can:
+
+- Open and use NGINX One Console
+- Understand how NGINX One Console works
+- Create, copy, and store a data plane key
+- Revoke or delete a data plane key
+
+---
+
+## Before you begin
+
+You need:
+
+- An F5 Distributed Cloud (XC) account
+- NGINX One service enabled
+- Basic Linux and NGINX knowledge
+
+{{< include "/nginx-one/cloud-access.md" >}}
+
+---
+
+## How NGINX One Console works
+
+NGINX One Console connects to each NGINX instance through **NGINX Agent**, a lightweight process that enables secure communication between the instance and NGINX One Console.  
+NGINX Agent applies configuration updates from NGINX One Console, collects performance and operating system metrics, and sends event notifications from the instance.
+
+You can install NGINX Agent in several ways:
+
+- Use public Docker images of NGINX Open Source with NGINX Agent preinstalled
+- Use public Docker images of NGINX Plus with NGINX Agent preinstalled
+- Install manually with `apt` or `yum`
+- Use the one-line `curl` command provided during registration
+
+When you register a new instance, NGINX One Console gives you a `curl` command that downloads and installs NGINX Agent on your target system.
+
+A data plane key is required to connect an instance to NGINX One Console. Once connected, you can monitor and manage the instance from the NGINX One Console dashboard.
+
+For more about NGINX Agent, see the [NGINX Agent overview]({{< ref "/nginx-one/agent/overview/about.md" >}}).
+
+---
+
+## Open NGINX One Console
+
+{{< include "/nginx-one/cloud-access-nginx.md" >}}
+
+
+Until you add NGINX instances are connected, the NGINX One Console dashboard remains empty. After you add instances, the dashboard shows metrics like availability, version, and usage trends.
+
+---
+
+## Create a data plane key
+
+1. In NGINX One Console, go to **Manage > Data Plane Keys**.
+2. Select **Add Data Plane Key**.
+3. Enter a name for the data plane key.
+4. Set an expiration date, or use the one-year default.
+5. Select **Generate**.
+6. Copy the data plane key — **you can’t view it again**.
+7. Store the data plane key in a safe place.
+
+You can use the same data plane key to register multiple instances. If you lose the data plane key, create a new one.
+
+---
+
+## Revoke a data plane key
+
+1. In NGINX One Console, go to **Manage > Data Plane Keys**.
+2. Find the data plane key you want to revoke.
+3. Select the data plane key.
+4. Choose **Revoke**, and confirm.
+
+---
+
+## Delete a revoked data plane key
+
+You can only delete a data plane key after you revoke it.
+
+1. In NGINX One Console, go to the **Revoked Keys** tab.
+2. Find the data plane key you want to delete.
+3. Select the data plane key.
+4. Choose **Delete Selected**, and confirm.
+
+---
+
+## Next steps
+
+You’re ready to connect your first NGINX instance to NGINX One Console.  
+Go to [Lab 2: Run workshop components with Docker]({{< ref "nginx-one/workshops/lab2/run-workshop-components-with-docker.md" >}})
+
+---
+
+## References
+
+- [Create and manage data plane keys]({{< ref "nginx-one/connect-instances/create-manage-data-plane-keys.md" >}})
+- [NGINX Agent overview]({{< ref "/nginx-one/agent/overview/about.md" >}})