From 1ae2d773f1d239544e284f68988d188714835f6e Mon Sep 17 00:00:00 2001 From: Micheal Kingston <44472403+mkingst@users.noreply.github.com> Date: Wed, 15 Jan 2025 10:27:05 +0000 Subject: [PATCH 1/3] Update tech-specs.md to include NAP --- content/nim/fundamentals/tech-specs.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/content/nim/fundamentals/tech-specs.md b/content/nim/fundamentals/tech-specs.md index 3db28325b..224c1af0e 100644 --- a/content/nim/fundamentals/tech-specs.md +++ b/content/nim/fundamentals/tech-specs.md @@ -29,13 +29,13 @@ You can deploy NGINX Instance Manager in the following environments: ## Sizing recommendations for Managing NGINX Instances {#system-sizing} -The following recommendations provide the minimum guidelines for NGINX Instance Manager. These guidelines ensure adequate performance, but for optimal results, we strongly recommend using solid-state drives (SSDs) for storage. +The following recommendations provide the minimum guidelines for NGINX Instance Manager. These guidelines ensure adequate performance, but for optimal results, we strongly recommend using solid-state drives (SSDs) for storage. See further down for requirements when NGINX App Protect us being used, as this requires additional memory and cpu. ### Standard NGINX configuration deployments -This section outlines the recommendations for NGINX Instance Manager deployments with data plane instances using standard configurations. **Standard configurations** typically support up to **40 upstream servers** with associated location and server blocks, and up to **350 certificates**. This is ideal for medium-sized environments or applications with moderate traffic. +This section outlines the recommendations for NGINX Instance Manager deployments with data plane instances using standard configurations, without NGINX App Protect. **Standard configurations** typically support up to **40 upstream servers** with associated location and server blocks, and up to **350 certificates**. This is ideal for medium-sized environments or applications with moderate traffic. -We recommend using SSDs to enhance storage performance. +We recommend using SSDs to enhance storage performance. {{}} | Number of Data Plane Instances | CPU | Memory | Network | Storage | @@ -49,7 +49,7 @@ These values represent the minimum resources needed for deployments that fall un ### Large NGINX configuration deployments -For environments requiring more resources, **large configurations** are suitable. These configurations can support up to **300 upstream servers** and are designed for enterprise environments or applications handling high traffic and complex configurations. +For environments requiring more resources, **large configurations** are suitable. These configurations can support up to **300 upstream servers** and are designed for enterprise environments or applications handling high traffic and complex configurations, without NGINX App Protect. {{}} | Number of Data Plane Instances | CPU | Memory | Network | Storage | @@ -58,6 +58,10 @@ For environments requiring more resources, **large configurations** are suitable | 250 | 4 vCPU | 8 GB RAM | 1 GbE NIC | 2 TB | {{}} +### NGINX configuration deployments with NGINX App Protect + +If using NGINX App Protect features in NGINX Instance Manager, this requires additional CPU and Memory for policy compilation and security monitoring features. At a minimum, 8gb Memory and 4 CPUs are required for a standard NGINX App Protect use case (under 20 NGINX Plus instances). The requirements are heavily dependent on the number of policies being managed, the frequency of updates and the number of events being that occur in the security monitoring feature. + ### License and usage reporting only {#reporting-sizing} This section assumes you've configured NGINX Instance Manager to manage your NGINX instances for licensing and usage reporting only. NGINX commercial license and usage reporting is done in an “unmanaged” way, where NGINX sends a request periodically to NGINX Instance Manager solely for counting purposes. For more information, see how you would [Prepare your environment for reporting]({{< relref "/solutions/about-subscription-licenses.md#set-up-environment" >}}). From ad2f53a1155ea0ece93acef8c84a8b694979bd73 Mon Sep 17 00:00:00 2001 From: Alan Dooley Date: Wed, 15 Jan 2025 15:06:03 +0000 Subject: [PATCH 2/3] Apply suggestions from code review Co-authored-by: Daniel Edgar --- content/nim/fundamentals/tech-specs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/nim/fundamentals/tech-specs.md b/content/nim/fundamentals/tech-specs.md index 224c1af0e..facfc5918 100644 --- a/content/nim/fundamentals/tech-specs.md +++ b/content/nim/fundamentals/tech-specs.md @@ -29,7 +29,7 @@ You can deploy NGINX Instance Manager in the following environments: ## Sizing recommendations for Managing NGINX Instances {#system-sizing} -The following recommendations provide the minimum guidelines for NGINX Instance Manager. These guidelines ensure adequate performance, but for optimal results, we strongly recommend using solid-state drives (SSDs) for storage. See further down for requirements when NGINX App Protect us being used, as this requires additional memory and cpu. +The following recommendations provide the minimum guidelines for NGINX Instance Manager. These guidelines ensure adequate performance, but for optimal results, we strongly recommend using solid-state drives (SSDs) for storage. See further down for requirements when NGINX App Protect is being used, as this requires additional memory and cpu. ### Standard NGINX configuration deployments From 5236f20dc625f4d119acb5509ec17d6d18b62caf Mon Sep 17 00:00:00 2001 From: Mike Jang <3287976+mjang@users.noreply.github.com> Date: Fri, 24 Jan 2025 07:30:15 -0800 Subject: [PATCH 3/3] Apply suggestions from code review --- content/nim/fundamentals/tech-specs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/nim/fundamentals/tech-specs.md b/content/nim/fundamentals/tech-specs.md index facfc5918..22b91d7ca 100644 --- a/content/nim/fundamentals/tech-specs.md +++ b/content/nim/fundamentals/tech-specs.md @@ -29,7 +29,7 @@ You can deploy NGINX Instance Manager in the following environments: ## Sizing recommendations for Managing NGINX Instances {#system-sizing} -The following recommendations provide the minimum guidelines for NGINX Instance Manager. These guidelines ensure adequate performance, but for optimal results, we strongly recommend using solid-state drives (SSDs) for storage. See further down for requirements when NGINX App Protect is being used, as this requires additional memory and cpu. +The following recommendations provide the minimum guidelines for NGINX Instance Manager. These guidelines ensure adequate performance, but for optimal results, we strongly recommend using solid-state drives (SSDs) for storage. If you set up [deployments with NGINX App Protect](#system-sizing-app-protect), you may need additional memory and CPU. ### Standard NGINX configuration deployments @@ -58,7 +58,7 @@ For environments requiring more resources, **large configurations** are suitable | 250 | 4 vCPU | 8 GB RAM | 1 GbE NIC | 2 TB | {{}} -### NGINX configuration deployments with NGINX App Protect +### NGINX configuration deployments with NGINX App Protect {#system-sizing-app-protect} If using NGINX App Protect features in NGINX Instance Manager, this requires additional CPU and Memory for policy compilation and security monitoring features. At a minimum, 8gb Memory and 4 CPUs are required for a standard NGINX App Protect use case (under 20 NGINX Plus instances). The requirements are heavily dependent on the number of policies being managed, the frequency of updates and the number of events being that occur in the security monitoring feature.