You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/includes/nginx-one/add-file/existing-ssl-bundle.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
docs:
3
3
---
4
4
5
-
With this option, You can incorporate [Managed certificates]({{< ref "/nginx-one/how-to/certificates/manage-certificates.md#managed-and-unmanaged-certificates" >}}).
5
+
With this option, you can incorporate [Managed certificates]({{< ref "/nginx-one/nginx-configs/certificates/manage-certificates.md#managed-and-unmanaged-certificates" >}}).
6
6
In the **Choose Certificate** drop-down, select the managed certificate of your choice, and select **Add**. You can then:
7
7
8
8
1. Review details of the certificate. The next steps depend on whether the certificate is a CA bundle or a certificate / key pair.
You can add an instance to NGINX One Console in the following ways:
9
+
10
+
- Directly, under **Instances**
11
+
- Indirectly, by selecting a Config Sync Group, and selecting **Add Instance to Config Sync Group**
12
+
13
+
In either case, NGINX One Console gives you a choice for data plane keys:
14
+
15
+
- Create a new key
16
+
- Use an existing key
17
+
18
+
NGINX One Console takes the option you use, and adds the data plane key to a command that you'd use to register your target instance. You should see the command in the **Add Instance** screen in the console.
19
+
20
+
Connect to the host where your NGINX instance is running. Run the provided command to [install NGINX Agent]({{< ref "/nginx-one/getting-started#install-nginx-agent" >}}) dependencies and packages on that host.
21
+
22
+
```bash
23
+
curl https://agent.connect.nginx.com/nginx-agent/install | DATA_PLANE_KEY="<data_plane_key>" sh -s -- -y
24
+
```
25
+
26
+
Once the process is complete, you can configure that instance in your NGINX One Console.
-**Drill down into specifics**: For in-depth information on a specific metric, like expiring certificates, click on the relevant link in the metric's card to go to a detailed overview page.
11
+
-**Refine metric timeframe**: Metrics show the last hour's data by default. To view data from a different period, select the time interval you want from the drop-down menu.
| <iclass="fas fa-heartbeat"></i> **Instance availability**| Understand the operational status of your NGINX instances. | - **Online**: The NGINX instance is actively connected and functioning properly. <br> - **Offline**: NGINX Agent is connected but the NGINX instance isn't running, isn't installed, or can't communicate with NGINX Agent. <br> - **Unavailable**: The connection between NGINX Agent and NGINX One has been lost or the instance has been decommissioned. <br> - **Unknown**: The current state can't be determined at the moment. |
22
+
| <iclass="fas fa-code-branch"></i> **NGINX versions by instance**| See which NGINX versions are in use across your instances. ||
23
+
| <iclass="fas fa-desktop"></i> **Operating systems**| Find out which operating systems your instances are running on. ||
24
+
| <iclass="fas fa-certificate"></i> **Certificates**| Monitor the status of your SSL certificates to know which are expiring soon and which are still valid. ||
25
+
| <iclass="fas fa-cogs"></i> **Config recommendations**| Get configuration recommendations to optimize your instances' settings. ||
26
+
| <iclass="fas fa-shield-alt"></i> **CVEs (Common Vulnerabilities and Exposures)**| Evaluate the severity and number of potential security threats in your instances. | - **Major**: Indicates a high-severity threat that needs immediate attention. <br> - **Medium**: Implies a moderate threat level. <br> - **Minor** and **Low**: Represent less critical issues that still require monitoring. <br> - **Other**: Encompasses any threats that don't fit the standard categories. |
27
+
| <iclass="fas fa-microchip"></i> **CPU utilization**| Track CPU usage trends and pinpoint instances with high CPU demand. ||
28
+
| <iclass="fas fa-memory"></i> **Memory utilization**| Watch memory usage patterns to identify instances using significant memory. ||
29
+
| <iclass="fas fa-hdd"></i> **Disk space utilization**| Monitor how much disk space your instances are using and identify those nearing capacity. ||
30
+
| <iclass="fas fa-exclamation-triangle"></i> **Unsuccessful response codes**| Look for instances with a high number of HTTP server errors and investigate their error codes. ||
31
+
| <iclass="fas fa-tachometer-alt"></i> **Top network usage**| Review the network usage and bandwidth consumption of your instances. ||
@@ -108,15 +108,15 @@ From the NGINX One Console you can now:
108
108
- Ensure that your certificates are current and correct.
109
109
- Manage your certificates from a central location. This can help you simplify operations and remotely update, rotate, and deploy those certificates.
110
110
111
-
For more information, see the full documentation on how you can [Manage Certificates]({{< ref "/nginx-one/how-to/certificates/manage-certificates.md" >}}).
111
+
For more information, see the full documentation on how you can [Manage Certificates]({{< ref "/nginx-one/nginx-configs/certificates/manage-certificates.md" >}}).
112
112
113
113
## August 22, 2024
114
114
115
115
### Config Sync Groups
116
116
117
117
Config Sync Groups are now available in the F5 NGINX One Console. This feature allows you to manage and synchronize NGINX configurations across multiple instances as a single entity, ensuring consistency and simplifying the management of your NGINX environment.
118
118
119
-
For more information, see the full documentation on [Managing Config Sync Groups]({{< ref "/nginx-one/how-to/config-sync-groups/manage-config-sync-groups.md" >}}).
119
+
For more information, see the full documentation on [Managing Config Sync Groups]({{< ref "/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md" >}}).
120
120
121
121
## August 8, 2024
122
122
@@ -136,7 +136,7 @@ Select the link for each CVE to see the details, including the CVE's publish dat
136
136
137
137
### Edit NGINX configurations
138
138
139
-
You can now make configuration changes to your NGINX instances. For more details, see [View and edit NGINX configurations]({{< ref "/nginx-one/how-to/nginx-configs/view-edit-nginx-configurations.md" >}}).
139
+
You can now make configuration changes to your NGINX instances. For more details, see [View and edit NGINX configurations]({{< ref "/nginx-one/nginx-configs/view-edit-nginx-configurations.md" >}}).
Copy file name to clipboardExpand all lines: content/nginx-one/connect-instances/add-instance.md
+7-25Lines changed: 7 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,34 +16,16 @@ to set up a data plane key to connect your instances to NGINX One.
16
16
17
17
Before you add an instance to NGINX One Console, ensure:
18
18
19
-
- You have administrator access to NGINX One Console.
20
-
- You have configured instances of NGINX that you want to manage through NGINX One Console.
21
-
- You have or are ready to configure a data plane key.
22
-
- You have or are ready to set up managed certificates.
19
+
- You have [administrator access]({{< ref "/nginx-one/rbac/roles.md" >}}) to NGINX One Console.
20
+
- You have [configured instances of NGINX]({{< ref "/nginx-one/getting-started.md#add-your-nginx-instances-to-nginx-one" >}}) that you want to manage through NGINX One Console.
21
+
- You have or are ready to configure a [data plane key]({{< ref "/nginx-one/getting-started.md#generate-data-plane-key" >}}).
22
+
- You have or are ready to set up [managed certificates]({{< ref "/nginx-one/nginx-configs/certificates/manage-certificates.md" >}}).
23
23
24
-
{{< note >}}If this is the first time an instance is being added to a Config Sync Group, and you have not yet defined the configuration for that Config Sync Group, that instance provides the template for that group. For more information, see [Configuration management]({{< ref "nginx-one/how-to/config-sync-groups/manage-config-sync-groups#configuration-management" >}}).{{< /note >}}
24
+
{{< note >}}If this is the first time an instance is being added to a Config Sync Group, and you have not yet defined the configuration for that Config Sync Group, that instance provides the template for that group. For more information, see [Configuration management]({{< ref "nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups#configuration-management" >}}).{{< /note >}}
25
25
26
26
## Add an instance
27
27
28
-
You can add an instance to NGINX One Console in the following ways:
29
-
30
-
- Directly, under **Instances**
31
-
- Indirectly, by selecting a Config Sync Group, and selecting **Add Instance to Config Sync Group**
32
-
33
-
In either case, NGINX One Console gives you a choice for data plane keys:
34
-
35
-
- Create a new key
36
-
- Use an existing key
37
-
38
-
NGINX One Console takes the option you use, and adds the data plane key to a command that you'd use to register your target instance. You should see the command in the **Add Instance** screen in the console.
39
-
40
-
Connect to the host where your NGINX instance is running. Run the provided command to [install NGINX Agent]({{< ref "/nginx-one/getting-started#install-nginx-agent" >}}) dependencies and packages on that host.
41
-
42
-
```bash
43
-
curl https://agent.connect.nginx.com/nginx-agent/install | DATA_PLANE_KEY="<data_plane_key>" sh -s -- -y
44
-
```
45
-
46
-
Once the process is complete, you can configure that instance in your NGINX One Console.
28
+
{{< include "/nginx-one/how-to/add-instance.md" >}}
47
29
48
30
## Managed and Unmanaged Certificates
49
31
@@ -71,5 +53,5 @@ Once you've completed the process, NGINX One reassigns this as a managed certifi
71
53
72
54
## Add an instance to a Config Sync Group
73
55
74
-
When you [Manage Config Sync Group membership]({{< ref "nginx-one/how-to/config-sync-groups/manage-config-sync-groups#manage-config-sync-group-membership" >}}), you can add an existing or new instance to the group of your choice.
56
+
When you [Manage Config Sync Group membership]({{< ref "nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups#manage-config-sync-group-membership" >}}), you can add an existing or new instance to the group of your choice.
75
57
That instance inherits the setup of that Config Sync Group.
0 commit comments