From 8d36ff92261e62de4366852497ffb3f3d748f8b4 Mon Sep 17 00:00:00 2001 From: Kafeel Hasan Date: Mon, 1 Sep 2025 14:32:21 +0530 Subject: [PATCH 1/5] =?UTF-8?q?Update=20NAP=20Docs=20This=20commit=20updat?= =?UTF-8?q?es=20the=20NAP=20user=20facing=20documentation=20with=20the=20f?= =?UTF-8?q?ollowing=20change:=20Based=20on=20this=20issue=20:=20https://gi?= =?UTF-8?q?thub.com/nginxinc/nalb-shared/issues/1695,=20updated=20the=20Co?= =?UTF-8?q?nfigure=20App=20Protect=20WAF=20with=20the=20following=20text?= =?UTF-8?q?=20-=20The=20File=20path=20is=20not=20optional=20and=20is=20aut?= =?UTF-8?q?omatically=20generated=20in=20the=20portal,=20defaulting=20to?= =?UTF-8?q?=20the=20path=20=E2=80=9C/etc/app=5Fprotect/conf/=E2=80=9D=20pl?= =?UTF-8?q?us=20the=20policy=20Name=20with=20a=20=E2=80=9C.json=E2=80=9D?= =?UTF-8?q?=20extension?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- content/nginxaas-azure/app-protect/configure-waf.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/nginxaas-azure/app-protect/configure-waf.md b/content/nginxaas-azure/app-protect/configure-waf.md index 8a461317c..77690f99c 100644 --- a/content/nginxaas-azure/app-protect/configure-waf.md +++ b/content/nginxaas-azure/app-protect/configure-waf.md @@ -114,7 +114,7 @@ To create a custom security policy in the Azure Portal: 3. Select **Custom Policies** 4. Select **Add Custom Security Policy** to open the policy editor -In the policy editor, enter the **Name**, **File path**, your policy content, and then select **Save**. The **File path** is optional and will default to the path "/etc/app_protect/conf/" plus the policy **Name** with a ".json" extension. After your policy has been saved, you can then reference it in your NGINX configuration. For more information on policy configuration and syntax, refer to the NGINX App Protect [configuration guide](https://docs.nginx.com/nginx-app-protect-waf/v5/configuration-guide/configuration/). +In the policy editor, enter the **Name**, **File path**, your policy content, and then select **Save**. The **File path** is not optional and is automatically generated in the portal, defaulting to the path "/etc/app_protect/conf/" plus the policy **Name** with a ".json" extension. After your policy has been saved, you can then reference it in your NGINX configuration. For more information on policy configuration and syntax, refer to the NGINX App Protect [configuration guide](https://docs.nginx.com/nginx-app-protect-waf/v5/configuration-guide/configuration/). {{< call-out "note" >}}The **name** field within the security policy must be unique among the policies referenced in your NGINX configuration.{{< /call-out >}} @@ -129,3 +129,4 @@ It is highly recommended to use logging to monitor the performance of NGINX App ## What's next [Enable App Protect WAF Logs]({{< ref "/nginxaas-azure/app-protect/enable-logging.md" >}}) + \ No newline at end of file From 03f121d19f79532ca9fb7404f527b8c6d151b4b7 Mon Sep 17 00:00:00 2001 From: Kafeel Hasan Date: Mon, 1 Sep 2025 14:35:38 +0530 Subject: [PATCH 2/5] Removed Extra Space --- content/nginxaas-azure/app-protect/configure-waf.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/nginxaas-azure/app-protect/configure-waf.md b/content/nginxaas-azure/app-protect/configure-waf.md index 77690f99c..bf40ad67e 100644 --- a/content/nginxaas-azure/app-protect/configure-waf.md +++ b/content/nginxaas-azure/app-protect/configure-waf.md @@ -128,5 +128,4 @@ It is highly recommended to use logging to monitor the performance of NGINX App ## What's next -[Enable App Protect WAF Logs]({{< ref "/nginxaas-azure/app-protect/enable-logging.md" >}}) - \ No newline at end of file +[Enable App Protect WAF Logs]({{< ref "/nginxaas-azure/app-protect/enable-logging.md" >}}) \ No newline at end of file From eb3be3bd4ab3ce04a1432f964f5ce948f48b4fd6 Mon Sep 17 00:00:00 2001 From: Kafeel Hasan Date: Tue, 23 Sep 2025 17:39:22 +0530 Subject: [PATCH 3/5] Update external documentation to inform customers about f5cloudstatus --- content/nginxaas-azure/disaster-recovery.md | 2 +- content/nginxaas-azure/service-health.md | 12 ++++++++++++ 2 files changed, 13 insertions(+), 1 deletion(-) create mode 100644 content/nginxaas-azure/service-health.md diff --git a/content/nginxaas-azure/disaster-recovery.md b/content/nginxaas-azure/disaster-recovery.md index eb378a3b2..afa5d8927 100644 --- a/content/nginxaas-azure/disaster-recovery.md +++ b/content/nginxaas-azure/disaster-recovery.md @@ -1,6 +1,6 @@ --- title: Disaster recovery -weight: 750 +weight: 650 toc: true url: /nginxaas/azure/disaster-recovery/ type: diff --git a/content/nginxaas-azure/service-health.md b/content/nginxaas-azure/service-health.md new file mode 100644 index 000000000..aff05a54f --- /dev/null +++ b/content/nginxaas-azure/service-health.md @@ -0,0 +1,12 @@ +--- +title: Service Health +weight: 710 +toc: true +url: /nginxaas/azure/service-health/ +type: +- how-to +--- + +The health status of the F5 NGINXaaS service can be monitored at the [F5 Cloud Status page](https://www.f5cloudstatus.com/history?filter=88pmy2nlbd01). This website will provide regional impacts to the service, including service degradation and unscheduled downtime. When appropriate, mitigation actions will be suggested to minimize the impact to your deployments. + +You may also subscribe to receive emails, webhooks, and RSS feeds when an incident related to NGINXaaS is created, updated, or resolved. \ No newline at end of file From f64faec3c9a0e3cafb2dfb3d595922707b09ec91 Mon Sep 17 00:00:00 2001 From: Kafeel Hasan Date: Tue, 23 Sep 2025 23:26:43 +0530 Subject: [PATCH 4/5] Addressed PR Comments --- .../nginxaas-azure/{service-health.md => service-status.md} | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename content/nginxaas-azure/{service-health.md => service-status.md} (51%) diff --git a/content/nginxaas-azure/service-health.md b/content/nginxaas-azure/service-status.md similarity index 51% rename from content/nginxaas-azure/service-health.md rename to content/nginxaas-azure/service-status.md index aff05a54f..1781929d6 100644 --- a/content/nginxaas-azure/service-health.md +++ b/content/nginxaas-azure/service-status.md @@ -1,12 +1,12 @@ --- -title: Service Health +title: Service Status weight: 710 toc: true -url: /nginxaas/azure/service-health/ +url: /nginxaas/azure/service-status/ type: - how-to --- -The health status of the F5 NGINXaaS service can be monitored at the [F5 Cloud Status page](https://www.f5cloudstatus.com/history?filter=88pmy2nlbd01). This website will provide regional impacts to the service, including service degradation and unscheduled downtime. When appropriate, mitigation actions will be suggested to minimize the impact to your deployments. +The health status of the F5 NGINXaaS service can be monitored at the [F5 Cloud Status page](https://www.f5cloudstatus.com/history?filter=88pmy2nlbd01). The status page provides information related to service degradation and unscheduled downtime. When appropiate, mitigation actions will be provided to minimize the impact to your deployments. You may also subscribe to receive emails, webhooks, and RSS feeds when an incident related to NGINXaaS is created, updated, or resolved. \ No newline at end of file From e55e44966b25bd54bda0537d219aa3eabf380cbc Mon Sep 17 00:00:00 2001 From: Kafeel Hasan Date: Tue, 23 Sep 2025 23:53:46 +0530 Subject: [PATCH 5/5] Addressed PR comments --- content/nginxaas-azure/service-status.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/nginxaas-azure/service-status.md b/content/nginxaas-azure/service-status.md index 1781929d6..7f7cba6f2 100644 --- a/content/nginxaas-azure/service-status.md +++ b/content/nginxaas-azure/service-status.md @@ -1,5 +1,5 @@ --- -title: Service Status +title: Service status weight: 710 toc: true url: /nginxaas/azure/service-status/ @@ -7,6 +7,6 @@ type: - how-to --- -The health status of the F5 NGINXaaS service can be monitored at the [F5 Cloud Status page](https://www.f5cloudstatus.com/history?filter=88pmy2nlbd01). The status page provides information related to service degradation and unscheduled downtime. When appropiate, mitigation actions will be provided to minimize the impact to your deployments. +You can monitor the health status of the F5 NGINXaaS service at the [F5 Cloud Status page](https://www.f5cloudstatus.com/history?filter=88pmy2nlbd01). The status page provides information related to service degradation and unscheduled downtime. When appropriate, we provide mitigations to minimize the impact to your deployments. You may also subscribe to receive emails, webhooks, and RSS feeds when an incident related to NGINXaaS is created, updated, or resolved. \ No newline at end of file