Skip to content

Commit a073201

Browse files
vvnginxmjang
andauthored
Update content/nim/fundamentals/tech-specs.md
Co-authored-by: Mike Jang <[email protected]>
1 parent 7e1dd93 commit a073201

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

content/nim/fundamentals/tech-specs.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,8 @@ The table below shows the estimated storage requirements for **NGINX OSS**, base
132132
| | 250 | 14 | 4 GiB |
133133
{{</bootstrap-table>}}
134134

135-
## Directory Requirements for NGINX Instance Manager ##
135+
## Directory Requirements for NGINX Instance Manager
136+
136137
Below are the directory requirements and storage recommendations for fresh, minimal, and moderate usage (<100 instances) of NGINX Instance Manager (NIM).
137138
Important Note: These recommendations apply if you are using NGINX Agent to connect NGINX instances to NIM for full management capabilities (e.g., managing configurations, viewing metrics, applying WAF policies, managing certificates, etc.). If the use case is solely usage reporting, as introduced in R33+, the Agent is not required, and resources needed are significantly reduced. For usage reporting-only deployments, NIM simply receives and stores usage data sent directly from the instances, which does not require the same resource allocation outlined below.
138139

0 commit comments

Comments
 (0)