Updates from internal changes, thru Jan 6 (#47)

Author: mjang

content/amplify/faq/nginx-amplify-agent.md

@@ -13,16 +13,16 @@ The F5 NGINX Amplify Agent is currently officially packaged and supported for th
 
   * Ubuntu 22.04 "jammy" (amd64/arm64)
   * Ubuntu 20.04 "focal" (amd64/arm64)
-  * Ubuntu 18.04 "bionic" (amd64/arm64)
   * Debian 12 "bookworm" (amd64/arm64)
   * Debian 11 "bullseye" (amd64/arm64)
-  * Debian 10 "buster" (amd64/arm64)
   * RHEL/CentOS/OEL 9 (amd64/arm64)
   * Amazon Linux 2 LTS (amd64/arm64)
 
 The following platforms are no longer supported but still can be used with older agent packages powered by Python 3:
 
   * RHEL/CentOS/OEL 8 (amd64/arm64)
+  * Ubuntu 18.04 "bionic" (amd64/arm64)
+  * Debian 10 "buster" (amd64/arm64)
 
 The following platforms are no longer supported but still can be used with older agent packages powered by Python 2:
 

content/amplify/nginx-amplify-agent/install/installing-amplify-agent.md

@@ -9,7 +9,7 @@ docs: "DOCS-968"
 
 To use F5 NGINX Amplify to monitor your infrastructure, you need to install NGINX Amplify Agent on each system you wish to monitor.
 
-{{< note >}} NGINX Amplify Agent will drop *root* privileges on startup. It will then use the user ID of the user `nginx` to set its effective user ID. The package install procedure will add the `nginx` user automatically unless it's already found in the system. If the [user](http://nginx.org/en/docs/ngx_core_module.html#user) directive appears in the NGINX configuration, NGINX Amplify Agent will pick up the user specified in the NGINX config for its effective user ID (e.g. `www-data`). {{< /note >}}
+{{< note >}} NGINX Amplify Agent will drop *root* privileges on startup. It will then use the user ID of the user `nginx` to set its effective user ID. The package install procedure will add the `nginx` user automatically unless it's already found in the system. If the [user](https://nginx.org/en/docs/ngx_core_module.html#user) directive appears in the NGINX configuration, NGINX Amplify Agent will pick up the user specified in the NGINX config for its effective user ID (e.g. `www-data`). {{< /note >}}
 
 ## Using the Install Script
 
@@ -39,30 +39,30 @@ Take the following steps to install NGINX Amplify Agent:
 1. Add the NGINX public key.
 
    ```bash
-   curl -fs http://nginx.org/keys/nginx_signing.key | apt-key add -
+   curl -fs https://nginx.org/keys/nginx_signing.key | apt-key add -
    ```
 
    or
 
    ```bash
    wget -q -O - \
-   http://nginx.org/keys/nginx_signing.key | apt-key add -
+   https://nginx.org/keys/nginx_signing.key | apt-key add -
    ```
 
 2. Configure the repository as follows.
 
     ```bash
     codename=`lsb_release -cs` && \
     os=`lsb_release -is | tr '[:upper:]' '[:lower:]'` && \
-    echo "deb http://packages.amplify.nginx.com/${os}/ ${codename} amplify-agent" > \
+    echo "deb https://packages.amplify.nginx.com/py3/${os} ${codename} amplify-agent" > \
     /etc/apt/sources.list.d/nginx-amplify.list
     ```
 
-3. Verify the repository config file (Ubuntu 14.04 example follows).
+3. Verify the repository config file (Ubuntu 22.04 example follows).
 
     ```bash
     cat /etc/apt/sources.list.d/nginx-amplify.list
-    deb http://packages.amplify.nginx.com/ubuntu/ trusty amplify-agent
+    deb https://packages.amplify.nginx.com/py3/ubuntu jammy amplify-agent
     ```
 
 4. Update the package index files.
@@ -82,14 +82,14 @@ Take the following steps to install NGINX Amplify Agent:
 1. Add the NGINX public key.
 
     ```bash
-    curl -sS -L -O http://nginx.org/keys/nginx_signing.key && \
+    curl -sS -L -O https://nginx.org/keys/nginx_signing.key && \
     rpm --import nginx_signing.key
     ```
 
    or
 
     ```bash
-    wget -q -O nginx_signing.key http://nginx.org/keys/nginx_signing.key && \
+    wget -q -O nginx_signing.key https://nginx.org/keys/nginx_signing.key && \
     rpm --import nginx_signing.key
     ```
 
@@ -99,23 +99,23 @@ Take the following steps to install NGINX Amplify Agent:
 
     ```bash
     release="7" && \
-    printf "[nginx-amplify]\nname=nginx amplify repo\nbaseurl=http://packages.amplify.nginx.com/centos/${release}/\$basearch\ngpgcheck=1\nenabled=1\n" > \
+    printf "[nginx-amplify]\nname=nginx amplify repo\nbaseurl=https://packages.amplify.nginx.com/py3/centos/${release}/\$basearch\ngpgcheck=1\nenabled=1\n" > \
     /etc/yum.repos.d/nginx-amplify.repo
     ```
 
     ```bash
     release="latest" && \
-    printf "[nginx-amplify]\nname=nginx amplify repo\nbaseurl=http://packages.amplify.nginx.com/amzn/${release}/\$basearch\ngpgcheck=1\nenabled=1\n" > \
+    printf "[nginx-amplify]\nname=nginx amplify repo\nbaseurl=https://packages.amplify.nginx.com/py3/amzn/${release}/\$basearch\ngpgcheck=1\nenabled=1\n" > \
     /etc/yum.repos.d/nginx-amplify.repo
     ```
 
-3. Verify the repository config file (RHEL 7.1 example follows).
+3. Verify the repository config file (RHEL 9.5 example follows).
 
     ```bash
     cat /etc/yum.repos.d/nginx-amplify.repo
     [nginx-amplify]
     name=nginx repo
-    baseurl=http://packages.amplify.nginx.com/centos/7/$basearch
+    baseurl=https://packages.amplify.nginx.com/centos/9/$basearch
     gpgcheck=1
     enabled=1
     ```

content/nap-waf/v4/logging-overview/security-log.md

@@ -274,7 +274,6 @@ The table below lists attributes that are generated in the security logs. When u
 | enforced_bot_anomalies | Comma-separated list of anomalies that caused the request to be blocked. | default, grpc |
 | grpc_method | The method name of the gRPC request (derived from the URI). Not to be confused with `http_method`. Applicable only to requests that are processed by a gRPC Content Profile. The value is `N/A` in other cases. | grpc |
 | grpc_service | The service name of the gRPC request (derived from the URI). Applicable only to requests that are processed by a gRPC Content Profile. The value is `N/A` in other cases. | grpc |
-| grpc_message | The value of the `grpc-message` header | grpc |
 | compression_method | The compression algorithm used for the present message. Currently one of: <ul><li>gzip</li><li>deflate</li><li>none</li><li>n/a</li></ul> | grpc |
 |headers | The headers part of the request including the query string but not the body. | grpc |
 |ip_client | The source IP of the client initiating the request<br>       Note: if a proxy is being used, this may differ from the IP in the `X-Forwarded-For` header. | default, grpc |

content/nap-waf/v5/logging-overview/security-log.md

@@ -256,7 +256,6 @@ The table below lists attributes that are generated in the security logs. When u
 | enforced_bot_anomalies | Comma-separated list of anomalies that caused the request to be blocked. | default, grpc |
 | grpc_method | The method name of the gRPC request (derived from the URI). Not to be confused with 'http_method`. Applicable only to requests that are processed by a gRPC Content Profile. The value is `N/A` in other cases. | grpc |
 | grpc_service | The service name of the gRPC request (derived from the URI). Applicable only to requests that are processed by a gRPC Content Profile. The value is `N/A` in other cases. | grpc |
-| grpc_message | The value of the `grpc-message` header | grpc |
 | compression_method | The compression algorithm used for the present message. Currently one of: <ul><li>gzip</li><li>deflate</li><li>none</li><li>n/a</li></ul> | grpc |
 |headers | The headers part of the request including the query string but not the body. | grpc |
 |ip_client | The source IP of the client initiating the request<br>       Note: if a proxy is being used, this may differ from the IP in the `X-Forwarded-For` header. | default, grpc |