Skip to content

Commit 7fc0462

Browse files
authored
Merge branch 'main' into fix-deployed-managed-cert-sections
2 parents 9580fc1 + a1fc2a8 commit 7fc0462

File tree

3 files changed

+16
-16
lines changed

3 files changed

+16
-16
lines changed

content/agent/configuration/configure-nginx-agent-group.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ doctypes: ["task"]
1313

1414
During installation, NGINX Agent detects the NGINX user (typically `nginx`) for the master and worker processes and adds this user to a group called `nginx-agent`.
1515

16-
If you change the NGINX username after installing the NGINX Agent, you'll need to add the new username to the `nginx-agent` group so that the NGINX socket has the proper permissions.
16+
If you change the NGINX username after installing NGINX Agent, you'll need to add the new username to the `nginx-agent` group so that the NGINX socket has the proper permissions.
1717

1818
A failure to update the `nginx-agent` group when the NGINX username changes may result in non-compliance errors for NGINX Plus.
1919

content/nginx-one/how-to/data-plane-keys/create-manage-data-plane-keys.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ If you need to deactivate a data plane key before its expiration date, follow th
6262

6363
## Delete a data plane key
6464

65-
Before you can delete a key, it must be expired or revoked. You can revoke a key either through the NGINX One console, as explained above, or by using the REST API. Once deleted, all information about the data plane key is permanently removed.
65+
Before you can delete a key, it must be expired or revoked. You can revoke a key either through the NGINX One Console, as explained above, or by using the REST API. Once deleted, all information about the data plane key is permanently removed.
6666

6767
1. On the left menu, select **Data Plane Keys**.
6868
2. Find the key you want to revoke in the list of expired or revoked keys.

content/nms/nginx-agent/install-nginx-agent.md

+14-14
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ This section lists the prerequisites for installing and configuring NGINX Agent.
1717

1818
1. [F5 NGINX Management Suite is installed on a server]({{< relref "/nim/deploy/_index.md" >}}).
1919

20-
{{<note>}} When installing and configuring NGINX Management Suite, take note of the fully qualified domain name (FQDN) and gRPC port number. You'll need this information to properly configure the NGINX Agent to communicate with NGINX Management Suite.
20+
{{<note>}} When installing and configuring NGINX Management Suite, take note of the fully qualified domain name (FQDN) and gRPC port number. You'll need this information to properly configure NGINX Agent to communicate with NGINX Management Suite.
2121
{{</note>}}
2222

2323
2. Make sure NGINX is running on your instance:
@@ -58,7 +58,7 @@ To see if `nginx_agent_selinux` is installed, run the following command:
5858

5959
## Install NGINX Agent
6060

61-
You can choose one of the following two methods to install the NGINX Agent on your data plane host:
61+
You can choose one of the following two methods to install NGINX Agent on your data plane host:
6262

6363
- Install via the NGINX Management Suite API Gateway
6464
- Install from packages downloaded from [MyF5 Customer Portal](https://account.f5.com/myf5) or from your NGINX/F5 sales team.
@@ -102,7 +102,7 @@ root 293850 109 1.1 1240056 23536 ? Ssl 22:00 0:07 /usr/local/bi
102102
vagrant 293866 0.0 0.0 8160 736 pts/0 S+ 22:00 0:00 grep --color=auto nginx-agent
103103
```
104104

105-
Once you've verified the NGINX Agent is running on your data plane, you should confirm it's registered with NGINX Management Suite. You can do this two ways:
105+
Once you've verified NGINX Agent is running on your data plane, you should confirm it's registered with NGINX Management Suite. You can do this two ways:
106106

107107
{{<tabs name="verify-nginx">}}
108108

@@ -138,25 +138,25 @@ If you need to remove the instance, ensure that the NGINX Agent service is stopp
138138
139139
## Configuring the NGINX Agent
140140
141-
The following sections explain how to configure the NGINX Agent using configuration files, CLI flags, and environment variables.
141+
The following sections explain how to configure NGINX Agent using configuration files, CLI flags, and environment variables.
142142
143143
{{<note>}}
144144
145-
- The NGINX Agent interprets configuration values set by configuration files, CLI flags, and environment variables in the following priorities:
145+
- NGINX Agent interprets configuration values set by configuration files, CLI flags, and environment variables in the following priorities:
146146
147147
1. CLI flags overwrite configuration files and environment variable values.
148148
2. Environment variables overwrite configuration file values.
149149
3. Config files are the lowest priority and config settings are superseded if either of the other options is used.
150150
151-
- The NGINX Agent is configured by default to connect to the NGINX Management Suite on port 443 based on the address used to download the install script. If this setting doesn't work, you can change the `server` fields in the `nginx-agent.conf` file. Instructions are provided in the following sections.
151+
- NGINX Agent is configured by default to connect to the NGINX Management Suite on port 443 based on the address used to download the install script. If this setting doesn't work, you can change the `server` fields in the `nginx-agent.conf` file. Instructions are provided in the following sections.
152152

153153
- Open any required firewall ports or SELinux/AppArmor rules for the ports and IPs you want to use.
154154

155155
{{</note>}}
156156

157157
### Configure with Config Files
158158

159-
The configuration files for the NGINX Agent are `/etc/nginx-agent/nginx-agent.conf` and `/var/lib/nginx-agent/agent-dynamic.conf`. These files have comments at the top indicating their purpose.
159+
The configuration files for NGINX Agent are `/etc/nginx-agent/nginx-agent.conf` and `/var/lib/nginx-agent/agent-dynamic.conf`. These files have comments at the top indicating their purpose.
160160

161161
{{<note>}}If you're running Instance Manager 2.10.1 or earlier or NGINX Agent 2.25.1 or earlier, the `agent-dynamic.conf` file is located in `/etc/nginx-agent/`.{{</note>}}
162162
@@ -231,7 +231,7 @@ extensions:
231231

232232
# Enable reporting NGINX App Protect details to the control plane.
233233
nginx_app_protect:
234-
# Report interval for NGINX App Protect details - the frequency the NGINX Agent checks NGINX App Protect for changes.
234+
# Report interval for NGINX App Protect details - the frequency NGINX Agent checks NGINX App Protect for changes.
235235
report_interval: 15s
236236
# Enable precompiled publication from the NGINX Management Suite (true) or perform compilation on the data plane host (false).
237237
precompiled_publication: true
@@ -271,7 +271,7 @@ tags:
271271
272272
## CLI Flags & Environment Variables
273273
274-
This section details the CLI flags and corresponding environment variables used to configure the NGINX Agent.
274+
This section details the CLI flags and corresponding environment variables used to configure NGINX Agent.
275275
276276
### Usage
277277
@@ -402,7 +402,7 @@ Additionally, you can use the agent installation script to add these fields:
402402
403403
## SELinux for NGINX Agent
404404
405-
This section explains how to install and configure the SELinux policy for the NGINX Agent.
405+
This section explains how to install and configure the SELinux policy for NGINX Agent.
406406
407407
### Installing NGINX Agent SELinux Policy Module
408408
@@ -418,7 +418,7 @@ To load the NGINX Agent policy, run the following commands:
418418
419419
### Adding Ports for NGINX Agent SELinux Context
420420
421-
You can configure the NGINX Agent to work with SELinux. Make sure you add external ports to the firewall exception list.
421+
You can configure NGINX Agent to work with SELinux. Make sure you add external ports to the firewall exception list.
422422
423423
The following example shows how to allow external ports outside the HTTPD context. You may need to enable NGINX to connect to these ports.
424424
@@ -430,11 +430,11 @@ For additional information on using NGINX with SELinux, refer to the guide [Usin
430430
431431
---
432432
433-
## Secure the NGINX Agent with mTLS
433+
## Secure NGINX Agent with mTLS
434434
435-
{{< important >}}By default, communication between the NGINX Agent and NGINX Management Suite is unsecured.{{< /important >}}
435+
{{< important >}}By default, communication between NGINX Agent and NGINX Management Suite is unsecured.{{< /important >}}
436436
437-
For instructions on how configure mTLS to secure communication between the NGINX Agent and NGINX Management Suite, see [NGINX Agent TLS Settings](https://docs.nginx.com/nginx-agent/configuration/encrypt-communication/).
437+
For instructions on how configure mTLS to secure communication between NGINX Agent and NGINX Management Suite, see [NGINX Agent TLS Settings](https://docs.nginx.com/nginx-agent/configuration/encrypt-communication/).
438438
439439
---
440440

0 commit comments

Comments
 (0)