From a1730356ffc186066bc9e2a805b57ce735d8ff67 Mon Sep 17 00:00:00 2001 From: Mike Jang <3287976+mjang@users.noreply.github.com> Date: Fri, 30 May 2025 13:47:29 -0700 Subject: [PATCH 1/5] feat: set up Secure Your Fleet use case --- content/nginx-one/_index.md | 5 +- content/nginx-one/secure-your-fleet/_index.md | 6 + content/nginx-one/secure-your-fleet/secure.md | 122 ++++++++++++++++++ 3 files changed, 132 insertions(+), 1 deletion(-) create mode 100644 content/nginx-one/secure-your-fleet/_index.md create mode 100644 content/nginx-one/secure-your-fleet/secure.md diff --git a/content/nginx-one/_index.md b/content/nginx-one/_index.md index d5f57a9a6..9e6a40e1a 100644 --- a/content/nginx-one/_index.md +++ b/content/nginx-one/_index.md @@ -23,6 +23,9 @@ cascade: {{< card title="Draft new configurations" >}} Work with Staged Configurations {{}} + {{< card title="Secure your fleet" >}} + Configure alerts that match your security policies + {{}} {{< card title="Set up metrics" >}} Review your deployments in a dashboard {{}} @@ -70,4 +73,4 @@ cascade: Defend, adapt, and mitigate against Layer 7 denial-of-service attacks on your apps and APIs. {{}} {{}} -{{}} \ No newline at end of file +{{}} diff --git a/content/nginx-one/secure-your-fleet/_index.md b/content/nginx-one/secure-your-fleet/_index.md new file mode 100644 index 000000000..d9fea82ff --- /dev/null +++ b/content/nginx-one/secure-your-fleet/_index.md @@ -0,0 +1,6 @@ +--- +title: Secure your fleet +description: +weight: 450 +url: /nginx-one/secure-your-fleet +--- diff --git a/content/nginx-one/secure-your-fleet/secure.md b/content/nginx-one/secure-your-fleet/secure.md new file mode 100644 index 000000000..6f56d335d --- /dev/null +++ b/content/nginx-one/secure-your-fleet/secure.md @@ -0,0 +1,122 @@ +--- +title: "Set up security alerts" +weight: 500 +toc: true +type: how-to +product: NGINX One +docs: DOCS-000 +--- + +In this tutorial, you'll learn how to set up Alerts in F5 Distributed Cloud for CVEs or insecure configurations impacting your NGINX fleet. This tutorial is intended for those who operate NGINX and are resposible for keeping their infrastructure and application traffic secure. It assumes you have basic knowledge of: + +- Installing Linux programs or running containers + +By the end of this tutorial, you'll be able to: + +- Access the NGINX One Console in F5 Distributed Cloud +- Connect NGINX instances to the NGINX One Console +- Review Security Risks associated with your NGINX fleet +- Configure Alert Policies in F5 Distributed Cloud + +## Background + +The NGINX One Console is a service for monitoring and managing NGINX. The Console is in the F5 Distributed Cloud and is included with all NGINX and F5 Distributed Cloud subscriptions. While NGINX is built to be secure and stable, critical vulnerabilities can occasionally emerge – and misconfigurations may leave your application or API exposed to attacks. + +## Before you begin + +If you already have accessed F5 Distributed Cloud and have NGINX instances available, you can skip these steps. + +### Confirm access to the F5 Distributed Cloud + +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 "F5 Distributed Cloud Services". 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. + +You or someone in your organization should have received 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. + +Navigate to https://INSERT_YOUR_TENANT_NAME.console.ves.volterra.io/ to access the F5 Distributed Cloud. If you have never logged in, select the Forgot Password option. Alternatively,Iif 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. + +### Install an instance of NGINX + +Ensure you have an instance of NGINX Open Source or NGINX Plus installed and available. This guide will provide instructions for connecting an instance installed in a Linux environment (VM or bare metal hardware) where you have command line access. However, we also have instructions for creating a Docker container with NGINX and the NGINX Agent installed and can connect using environment variables. + +## Navigate to the NGINX One Console in the F5 Distributed Cloud + +If you already have accessed the NGINX One Console, skip this section. + +1. Navigate to https://INSERT_YOUR_TENANT_NAME.console.ves.volterra.io/, using the tenant name described earlier. +1. Log in to the F5 Distributed Cloud Console. + 1. If it is your first time logging in, you may ned to reset your password by selecting Forgot Password. +1. Select the NGINX One tile +1. Select Visit Service + +## Connect at least one NGINX instance to the NGINX One Console + +If you already have connected instances to the NGINX One Console, you can skip this section. + +There are multiple ways to connect and NGINX instance depending on the environment. The instructions below walk you through using a `curl` command and installation script. We assume this is the first time you are connecting an instance. + +You can also install NGINX Agent from our repositories and configure it manually. Alternatively you can use our official Docker images. + +1. On the welcome screen, select Add Instance. +1. Generate a data plane key. + A data plane key is a security token that ensures only trusted NGINX instances can register and communicate with NGINX One. + 1. In the Add Instance pane, select Generate Data Plane Key. + Data plane keys are displayed only once and cannot be retrieved later. Be sure to copy and store this key securely. + Data plane keys expire after one year. You can change this expiration date later by editing the key. + +1. Install NGINX Agent + After you enter your data plane key, you’ll see a `curl` command similar to the one below. Copy and run this command on each NGINX instance to install NGINX Agent. Once installed, NGINX Agent typically registers with NGINX One within a few seconds. + +NGINX Agent must be able to establish a connection to NGINX One Console’s Agent endpoint (agent.connect.nginx.com). Ensure that any firewall rules you have in place for your NGINX hosts allows network traffic to port 443 for all of the following IPs: + +- 3.135.72.139 +- 3.133.232.50 +- 52.14.85.249 + +The NGINX One Console monitors all connected NGINX instances for CVEs and insecure configurations. Using the F5 Distributed Cloud's Alert Policies you can receive alerts for these risks in a manner of your choosing; for the purposes of this guide we will show you how to configure E-Mail alerts. + +## Configure an active alert policy + +The F5 Distributed Cloud generates alerts from all its services including NGINX One. You can configure rules to send those alerts to a receiver of your choice. These instructions walk you through how to configure an email notification when we see new CVEs or detect security issues with your NGINX instances. + +This page describes basic steps to set up an email alert. For authoritative documentation, see +[Alerts - Email & SMS](https://flatrender.tora.reviews/docs-v2/shared-configuration/how-tos/alerting/alerts-email-sms). + +## Configure alerts to be sent to your email + +To configure security-related alerts, follow these steps: + +1. Navigate to the F5 Distributed Cloud Console at https://INSERT_YOUR_TENANT_NAME.console.ves.volterra.io. +1. Find **Audit Logs & Alerts** > **Alerts Management**. +1. Select **Add Alert Receiver**. +1. Configure the **Alert Receivers** + 1. Enter the name of your choice + 1. (Optional) Specify a label and description +1. Under **Receiver**, select Email and enter your email address. +1. Select **Save and Exit**. +1. Your Email receiver should now appear on the list of Alert Receivers. +1. Under the Actions column, select Verify Email. +1. Select **Send email** to confirm. +1. You should receive a verification code in the email provided. Copy that code. +1. Under the Actions column, select **Enter verification code**. +1. Paste the code and select **Verify receiver**. + +## Configure Alert Policy + +Next, configure the policy that identifies when you'll get an alert. + +1. Navigate to **Alerts Management > Alert Policies**. +1. Select **Add Alert Policy**. + 1. Enter the name of your choice + 1. (Optional) Specify a label and description +1. Under Alert Reciever Configuration > Alert Receivers, select the Alert Receiver you just created +1. Under Policy Rules select Configure. +1. Select Add Item. +1. Under Select Alerts (TBD) +1. Set the Action as Send and select Apply + +Now set a second alert related to Common Vulnerabilities and Exposures (CVEs). + +1. Select Add Item. +1. Under Select Alerts {adding additional Alert type for CVE). +1. Set the Action as Send and select Apply. +1. Select **Save and Exit**. From 814398a7fcbd37907057058a0c824dc2f3f9eaca Mon Sep 17 00:00:00 2001 From: Mike Jang <3287976+mjang@users.noreply.github.com> Date: Sat, 14 Jun 2025 22:35:35 +0100 Subject: [PATCH 2/5] Update secure your fleet use case per stds --- .../how-to/generate-data-plane-key.md | 21 +++++ .../nginx-one/how-to/install-nginx-agent.md | 42 +++++++++ content/nginx-one/secure-your-fleet/secure.md | 85 +++++++++---------- 3 files changed, 105 insertions(+), 43 deletions(-) create mode 100644 content/includes/nginx-one/how-to/generate-data-plane-key.md create mode 100644 content/includes/nginx-one/how-to/install-nginx-agent.md diff --git a/content/includes/nginx-one/how-to/generate-data-plane-key.md b/content/includes/nginx-one/how-to/generate-data-plane-key.md new file mode 100644 index 000000000..3e69bedae --- /dev/null +++ b/content/includes/nginx-one/how-to/generate-data-plane-key.md @@ -0,0 +1,21 @@ +--- +docs: +files: + - content/nginx-one/secure-your-fleet/secure.md + - content/nginx-one/getting-started.md +--- + +A data plane key is a security token that ensures only trusted NGINX instances can register and communicate with NGINX One. + +To generate a data plane key: + +- **For a new key:** In the **Add Instance** pane, select **Generate Data Plane Key**. +- **To reuse an existing key:** If you already have a data plane key and want to use it again, select **Use existing key**. Then, enter the key's value in the **Data Plane Key** box. + +{{}} +Data plane keys are displayed only once and cannot be retrieved later. Be sure to copy and store this key securely. + +Data plane keys expire after one year. You can change this expiration date later by [editing the key]({{< ref "nginx-one/connect-instances/create-manage-data-plane-keys.md#change-expiration-date" >}}). + +If you [Revoke a data plane key]({{< ref "nginx-one/connect-instances/create-manage-data-plane-keys.md#revoke-data-plane-key" >}}) you disconnect all instances registered with that key. +{{}} diff --git a/content/includes/nginx-one/how-to/install-nginx-agent.md b/content/includes/nginx-one/how-to/install-nginx-agent.md new file mode 100644 index 000000000..bccedc67a --- /dev/null +++ b/content/includes/nginx-one/how-to/install-nginx-agent.md @@ -0,0 +1,42 @@ +--- +docs: +files: + - content/nginx-one/secure-your-fleet/secure.md + - content/nginx-one/getting-started.md +--- + +After entering your data plane key, you'll see a `curl` command similar to the one below. Copy and run this command on each NGINX instance to install NGINX Agent. Once installed, NGINX Agent typically registers with NGINX One within a few seconds. + +{{}} +NGINX Agent must be able to establish a connection to NGINX One Console's Agent endpoint (`agent.connect.nginx.com`). Ensure that any firewall rules you have in place for your NGINX hosts allows network traffic to port `443` for all of the following IPs: + +- `3.135.72.139` +- `3.133.232.50` +- `52.14.85.249` +{{}} + +To install NGINX Agent on an NGINX instance: + +1. **Check if NGINX is running and start it if it's not:** + + First, see if NGINX is running: + + ```shell + sudo systemctl status nginx + ``` + + If the status isn't `Active`, go ahead and start NGINX: + + ```shell + sudo systemctl start nginx + ``` + +2. **Install NGINX Agent:** + + Next, use the `curl` command provided to you to install NGINX Agent: + + ``` shell + curl https://agent.connect.nginx.com/nginx-agent/install | DATA_PLANE_KEY="YOUR_DATA_PLANE_KEY" sh -s -- -y + ``` + + - Replace `YOUR_DATA_PLANE_KEY` with your actual data plane key. diff --git a/content/nginx-one/secure-your-fleet/secure.md b/content/nginx-one/secure-your-fleet/secure.md index 6f56d335d..fde9e7e21 100644 --- a/content/nginx-one/secure-your-fleet/secure.md +++ b/content/nginx-one/secure-your-fleet/secure.md @@ -7,9 +7,9 @@ product: NGINX One docs: DOCS-000 --- -In this tutorial, you'll learn how to set up Alerts in F5 Distributed Cloud for CVEs or insecure configurations impacting your NGINX fleet. This tutorial is intended for those who operate NGINX and are resposible for keeping their infrastructure and application traffic secure. It assumes you have basic knowledge of: +In this tutorial, you'll learn how to set up alerts in F5 Distributed Cloud. Once configured, you'll see the CVEs and insecure configurations associated with your NGINX fleet. This tutorial is intended for those resposible for keeping their NGINX infrastructure and application traffic secure. It assumes you know how to: -- Installing Linux programs or running containers +- Install Linux programs or run Docker containers By the end of this tutorial, you'll be able to: @@ -20,66 +20,63 @@ By the end of this tutorial, you'll be able to: ## Background -The NGINX One Console is a service for monitoring and managing NGINX. The Console is in the F5 Distributed Cloud and is included with all NGINX and F5 Distributed Cloud subscriptions. While NGINX is built to be secure and stable, critical vulnerabilities can occasionally emerge – and misconfigurations may leave your application or API exposed to attacks. +NGINX One Console is a service to monitor and manage NGINX. It's a part of the F5 Distributed Cloud and is included with all NGINX and F5 Distributed Cloud subscriptions. While NGINX is built to be secure and stable, critical vulnerabilities can occasionally emerge – and misconfigurations may leave your applications or APIs exposed to attacks. ## Before you begin -If you already have accessed F5 Distributed Cloud and have NGINX instances available, you can skip these steps. +If you already have accessed F5 Distributed Cloud and have NGINX instances available, you can skip these steps and start to connect instances to the NGINX One Console.. ### Confirm access to the F5 Distributed Cloud -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 "F5 Distributed Cloud Services". 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 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. -You or someone in your organization should have received 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. +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. -Navigate to https://INSERT_YOUR_TENANT_NAME.console.ves.volterra.io/ to access the F5 Distributed Cloud. If you have never logged in, select the Forgot Password option. Alternatively,Iif 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. +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. -### Install an instance of NGINX +### Confirm access to NGINX One Console in the F5 Distributed Cloud + +Once you've logged in with your password, you should be able to see and select the NGINX One tile. -Ensure you have an instance of NGINX Open Source or NGINX Plus installed and available. This guide will provide instructions for connecting an instance installed in a Linux environment (VM or bare metal hardware) where you have command line access. However, we also have instructions for creating a Docker container with NGINX and the NGINX Agent installed and can connect using environment variables. +1. Select the **NGINX One** tile +1. Select **Visit Service** -## Navigate to the NGINX One Console in the F5 Distributed Cloud +### Install an instance of NGINX -If you already have accessed the NGINX One Console, skip this section. +Ensure you have an instance of NGINX Open Source or NGINX Plus installed and available. This guide will provide instructions for connecting an instance installed in a Linux environment (VM or bare metal hardware) where you have command line access. +You can then connect that instance with the help of NGINX Agent and a data plane key. + + ## Connect at least one NGINX instance to the NGINX One Console -If you already have connected instances to the NGINX One Console, you can skip this section. +If you already have connected instances to the NGINX One Console, you can start to [Configure an active alert policy]({{< ref "/nginx-one/secure-your-fleet.md/#configure-an-active-alert-policy" >}}). +Otherwise, you need to generate a data plane key, add an instance, and install NGINX Agent. We assume this is the first time you are connecting an instance. -There are multiple ways to connect and NGINX instance depending on the environment. The instructions below walk you through using a `curl` command and installation script. We assume this is the first time you are connecting an instance. +### Add an instance -You can also install NGINX Agent from our repositories and configure it manually. Alternatively you can use our official Docker images. +{{< include "/nginx-one/how-to/add-instance.md" >}} -1. On the welcome screen, select Add Instance. -1. Generate a data plane key. - A data plane key is a security token that ensures only trusted NGINX instances can register and communicate with NGINX One. - 1. In the Add Instance pane, select Generate Data Plane Key. - Data plane keys are displayed only once and cannot be retrieved later. Be sure to copy and store this key securely. - Data plane keys expire after one year. You can change this expiration date later by editing the key. +### Generate a data plane key -1. Install NGINX Agent - After you enter your data plane key, you’ll see a `curl` command similar to the one below. Copy and run this command on each NGINX instance to install NGINX Agent. Once installed, NGINX Agent typically registers with NGINX One within a few seconds. +{{< include "/nginx-one/how-to/generate-data-plane-key.md" >}} -NGINX Agent must be able to establish a connection to NGINX One Console’s Agent endpoint (agent.connect.nginx.com). Ensure that any firewall rules you have in place for your NGINX hosts allows network traffic to port 443 for all of the following IPs: +### Install NGINX Agent -- 3.135.72.139 -- 3.133.232.50 -- 52.14.85.249 +{{< include "/nginx-one/how-to/install-nginx-agent.md" >}} -The NGINX One Console monitors all connected NGINX instances for CVEs and insecure configurations. Using the F5 Distributed Cloud's Alert Policies you can receive alerts for these risks in a manner of your choosing; for the purposes of this guide we will show you how to configure E-Mail alerts. +You can also install NGINX Agent from our repositories and configure it manually. Alternatively you can use our official NGINX Docker images, pre-configured with NGINX Agent. ## Configure an active alert policy +The NGINX One Console monitors all connected NGINX instances for CVEs and insecure configurations. Using the F5 Distributed Cloud's Alert Policies you can receive alerts for these risks in a manner of your choosing; for the purposes of this guide we will show you how to configure E-Mail alerts. + The F5 Distributed Cloud generates alerts from all its services including NGINX One. You can configure rules to send those alerts to a receiver of your choice. These instructions walk you through how to configure an email notification when we see new CVEs or detect security issues with your NGINX instances. This page describes basic steps to set up an email alert. For authoritative documentation, see -[Alerts - Email & SMS](https://flatrender.tora.reviews/docs-v2/shared-configuration/how-tos/alerting/alerts-email-sms). +[Alerts - Email & SMS](https://docs.cloud.f5.com/docs-v2/shared-configuration/how-tos/alerting/alerts-email-sms). ## Configure alerts to be sent to your email @@ -89,8 +86,8 @@ To configure security-related alerts, follow these steps: 1. Find **Audit Logs & Alerts** > **Alerts Management**. 1. Select **Add Alert Receiver**. 1. Configure the **Alert Receivers** - 1. Enter the name of your choice - 1. (Optional) Specify a label and description + 1. Enter the name of your choice. + 1. (Optional) Specify a label and description. 1. Under **Receiver**, select Email and enter your email address. 1. Select **Save and Exit**. 1. Your Email receiver should now appear on the list of Alert Receivers. @@ -104,19 +101,21 @@ To configure security-related alerts, follow these steps: Next, configure the policy that identifies when you'll get an alert. -1. Navigate to **Alerts Management > Alert Policies**. -1. Select **Add Alert Policy**. +1. Navigate to **Alerts Management > Alert Policies** +1. Select **Add Alert Policy** 1. Enter the name of your choice 1. (Optional) Specify a label and description 1. Under Alert Reciever Configuration > Alert Receivers, select the Alert Receiver you just created -1. Under Policy Rules select Configure. -1. Select Add Item. +1. Under Policy Rules select Configure +1. Select Add Item 1. Under Select Alerts (TBD) 1. Set the Action as Send and select Apply Now set a second alert related to Common Vulnerabilities and Exposures (CVEs). -1. Select Add Item. -1. Under Select Alerts {adding additional Alert type for CVE). -1. Set the Action as Send and select Apply. -1. Select **Save and Exit**. +1. Select Add Item +1. Under Select Alerts {adding additional Alert type for CVE) +1. Set the Action as Send and select Apply +1. Select **Save and Exit** + +You've now set up F5 Distributed Cloud to send you security-related alerts from NGINX One Console. From c05f272616a84eedd8ff20d973018dda17b69159 Mon Sep 17 00:00:00 2001 From: Mike Jang <3287976+mjang@users.noreply.github.com> Date: Sun, 22 Jun 2025 08:28:35 -0700 Subject: [PATCH 3/5] Update secure your fleet --- content/nginx-one/secure-your-fleet/secure.md | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/content/nginx-one/secure-your-fleet/secure.md b/content/nginx-one/secure-your-fleet/secure.md index fde9e7e21..91b9fe8b5 100644 --- a/content/nginx-one/secure-your-fleet/secure.md +++ b/content/nginx-one/secure-your-fleet/secure.md @@ -52,7 +52,7 @@ You can then connect that instance with the help of NGINX Agent and a data plane ## Connect at least one NGINX instance to the NGINX One Console -If you already have connected instances to the NGINX One Console, you can start to [Configure an active alert policy]({{< ref "/nginx-one/secure-your-fleet.md/#configure-an-active-alert-policy" >}}). +If you already have connected instances to the NGINX One Console, you can start to [Configure an active alert policy]({{< ref "/nginx-one/secure-your-fleet/secure.md#configure-an-active-alert-policy" >}}). Otherwise, you need to generate a data plane key, add an instance, and install NGINX Agent. We assume this is the first time you are connecting an instance. ### Add an instance @@ -119,3 +119,18 @@ Now set a second alert related to Common Vulnerabilities and Exposures (CVEs). 1. Select **Save and Exit** You've now set up F5 Distributed Cloud to send you security-related alerts from NGINX One Console. + +## Summary + +In this tutorial, you learned how to: + +- Access the NGINX One Console +- Connect an NGINX instance +- Configure an Alert + +You will now receive an email any time the NGINX One Console recognizes one of your connected instances has a configuration that is insecure or an NGINX CVE impacts it. + +## Next steps + +Now that you have NGINX instances connected to the Console, consider reviewing our [use cases]({{< ref "/nginx-one/" >}}) to see how you can easily manage your NGINX instances, draft new configurations, and more. +Additionally, you can review how to add additional Alert Receivers such as [SMS](https://docs.cloud.f5.com/docs-v2/shared-configuration/how-tos/alerting/alerts-email-sms), [Slack](https://docs.cloud.f5.com/docs-v2/shared-configuration/how-tos/alerting/alerts-slack), [PagerDuty](https://docs.cloud.f5.com/docs-v2/shared-configuration/how-tos/alerting/alerts-pagerduty), or with a [webhook](https://docs.cloud.f5.com/docs-v2/shared-configuration/how-tos/alerting/alerts-webhook). From fa43039fb2d28dbb3d0cf6bdfdddc4d63dbceaeb Mon Sep 17 00:00:00 2001 From: Mike Jang <3287976+mjang@users.noreply.github.com> Date: Mon, 23 Jun 2025 07:49:42 -0600 Subject: [PATCH 4/5] updates after review --- content/nginx-one/secure-your-fleet/secure.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/content/nginx-one/secure-your-fleet/secure.md b/content/nginx-one/secure-your-fleet/secure.md index 91b9fe8b5..9812700e2 100644 --- a/content/nginx-one/secure-your-fleet/secure.md +++ b/content/nginx-one/secure-your-fleet/secure.md @@ -43,12 +43,8 @@ Once you've logged in with your password, you should be able to see and select t ### Install an instance of NGINX -Ensure you have an instance of NGINX Open Source or NGINX Plus installed and available. This guide will provide instructions for connecting an instance installed in a Linux environment (VM or bare metal hardware) where you have command line access. -You can then connect that instance with the help of NGINX Agent and a data plane key. - - +Ensure you have an instance of [NGINX Open Source or NGINX Plus]({{< ref "/nginx/admin-guide/installing-nginx/" >}}) installed and available. This guide will provide instructions for connecting an instance installed in a Linux environment (VM or bare metal hardware) where you have command line access. +Alternatively, we also have instructions for [Deploying NGINX and NGINX Plus with Docker]({{< ref "/nginx/admin-guide/installing-nginx/installing-nginx-docker.md" >}}) with NGINX and the NGINX Agent installed. That deployment can connect with environment variables ## Connect at least one NGINX instance to the NGINX One Console From 1df7f71a78c3c9bd3486e7d6fabdf684c1214be3 Mon Sep 17 00:00:00 2001 From: Mike Jang <3287976+mjang@users.noreply.github.com> Date: Mon, 23 Jun 2025 07:56:48 -0600 Subject: [PATCH 5/5] update hugo --- go.mod | 2 +- go.sum | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/go.mod b/go.mod index eab95ad43..ccf6b67e1 100644 --- a/go.mod +++ b/go.mod @@ -2,4 +2,4 @@ module github.com/nginxinc/docs go 1.19 -require github.com/nginxinc/nginx-hugo-theme v0.42.37 // indirect +require github.com/nginxinc/nginx-hugo-theme v0.42.39 // indirect diff --git a/go.sum b/go.sum index 2f4bc5017..b265b7a58 100644 --- a/go.sum +++ b/go.sum @@ -1,2 +1,2 @@ -github.com/nginxinc/nginx-hugo-theme v0.42.37 h1:KtESjG1VG6ioSQBWfwgIiDVEmq9mylpunV2NENM8XvI= -github.com/nginxinc/nginx-hugo-theme v0.42.37/go.mod h1:DPNgSS5QYxkjH/BfH4uPDiTfODqWJ50NKZdorguom8M= +github.com/nginxinc/nginx-hugo-theme v0.42.39 h1:1BZzotl+MHO3b3F91U15eyuD7hapbjlrbgfLQlHm+Vo= +github.com/nginxinc/nginx-hugo-theme v0.42.39/go.mod h1:DPNgSS5QYxkjH/BfH4uPDiTfODqWJ50NKZdorguom8M=