Pre OSS commit

Author: nginx

content/amplify/faq/user-interface.md

@@ -28,6 +28,6 @@ To completely delete a previously monitored object follow these steps:
   2. Delete objects from the web interface
   3. Delete alarms
 
-To delete a system using the web interface — find it in the [Inventory](/user-interface/inventory), and select the [i] icon. You can delete objects from the popup window that appears next.
+To delete a system using the web interface — find it in the [Inventory]({{< relref "/amplify/user-interface/inventory" >}}), and select the [i] icon. You can delete objects from the popup window that appears next.
 
 {{< important >}}Deleting objects in the User Interface will not stop NGINX Amplify Agent. To completely remove a system from monitoring, please stop or uninstall NGINX Amplify Agent, clean it up in the web interface, and clean up any alerts.{{< /important >}}

content/amplify/nginx-amplify-agent/troubleshooting-metrics-collection.md

@@ -20,7 +20,7 @@ If you don't see the new system or NGINX instance in the web interface, or (some
   7. `stub_status` is [configured correctly]({{< relref "/amplify/nginx-amplify-agent/configuring-metric-collection" >}}), and the `stub_status module` is included in the NGINX build (this can be confirmed with `nginx -V`).
   8. NGINX [access.log](http://nginx.org/en/docs/http/ngx_http_log_module.html) and [error.log](http://nginx.org/en/docs/ngx_core_module.html#error_log) files are readable by the user `nginx` (or by the [user](http://nginx.org/en/docs/ngx_core_module.html#user) set in NGINX config).
   9. All NGINX configuration files are readable by NGINX Amplify Agent user ID (check owner, group, and permissions).
-  10. Extra [configuration steps have been performed as required](/metrics-metadata/nginx-metrics#additional-nginx-metrics) for the additional metrics to be collected.
+  10. Extra [configuration steps have been performed as required]({{< relref "/amplify/metrics-metadata/nginx-metrics#additional-nginx-metrics" >}}) for the additional metrics to be collected.
   11. The system DNS resolver is correctly configured, and *receiver.amplify.nginx.com* can be successfully resolved.
   12. Outbound TLS/SSL from the system to *receiver.amplify.nginx.com* is not restricted. This can be confirmed with `curl(1)`. [Configure a proxy server]({{< relref "/amplify/nginx-amplify-agent/install/configuring-amplify-agent#setting-up-a-proxy" >}}) for NGINX Amplify Agent if required.
   13. *selinux(8)*, *apparmor(7)* or [grsecurity](https://grsecurity.net) are not interfering with the metric collection. E.g., for _selinux_(8)* review **/etc/selinux/config**. Try `setenforce 0` temporarily and see if it improves the situation for certain metrics.

content/controller/admin-guides/install/try-nginx-controller.md

@@ -157,7 +157,7 @@ To add a license using the [NGINX Controller REST API]({{< relref "/controller/a
 ### Prerequisites
 
 - Make sure to review the [NGINX Plus Technical Specifications Guide](https://docs.nginx.com/nginx/technical-specs/) for the requirements for your distribution and desired configuration.
-- You'll need the NGINX Plus certificate and public key files (`nginx-repo.crt` and `nginx-repo.key`) that were provided when you signed up for the trial license. If you don't have these files, you can use the [NGINX Controller REST API](https://docs.nginx.com/nginx-controller/api/reference/ctlr-v1) to download them.
+- You'll need the NGINX Plus certificate and public key files (`nginx-repo.crt` and `nginx-repo.key`) that were provided when you signed up for the trial license. If you don't have these files, you can use the [NGINX Controller REST API]({{< relref "/controller/api/_index.md" >}}) to download them.
 
 #### How to Download the NGINX Plus Cert and Key using the NGINX Controller API
 

content/nginx/admin-guide/load-balancer/http-health-check.md

@@ -106,7 +106,7 @@ To enable active health checks:
    }
    ```
 
-   The zone is shared among all worker processes and stores the configuration of the upstream group. This [enables](../http-load-balancer/#shared) the worker processes to use the same set of counters to keep track of responses from the servers in the group.
+   The zone is shared among all worker processes and stores the configuration of the upstream group. This [enables]({{< relref "/nginx/admin-guide/load-balancer/http-load-balancer.md#sharing-data-with-multiple-worker-processes" >}}) the worker processes to use the same set of counters to keep track of responses from the servers in the group.
 
    The defaults for active health checks can be overridden with parameters to the `health_check` directive:
 

content/solutions/connectivity-stack-kubernetes.md

@@ -33,7 +33,7 @@ NGINX Ingress Controller manages app connectivity at the edge of a Kubernetes cl
     - [Installation with Manifests](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/)
     - [Installation with Helm](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-helm/)
     - [Installation with NGINX Ingress Operator (Red Hat OpenShift)](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-operator/)
-    - [Using NGINX Ingress Controller in AWS Marketplace](https://docs.nginx.com/nginx-ingress-controller/installation/using-aws-marketplace-image/)
+    - [Using NGINX Ingress Controller in AWS Marketplace](https://docs.nginx.com/nginx-ingress-controller/installation/nic-images/using-aws-marketplace-image/)
 3. For additional installation options, including building custom container images, refer to the [documentation for NGINX Ingress Controller](https://docs.nginx.com/nginx-ingress-controller/installation/)
 
 ### Install NGINX Ingress Controller with NGINX App Protect WAF