docs: Publish NGINXaaS for GC pre-release docs

content/_index.md

@@ -43,7 +43,7 @@ Learn how to deliver, manage, and protect your applications using F5 NGINX produ
 {{</card-section>}}
 
 {{<card-section showAsCards="true" title="F5 NGINX as a Service">}}
-  {{<card title="F5 NGINXaaS for Azure" titleUrl="/nginxaas/azure/" brandIcon="NGINX-for-Azure-product-icon.svg" isLanding="true">}}
+  {{<card title="F5 NGINXaaS for Azure" titleUrl="/nginxaas/azure/" brandIcon="F5-NGINXaaS-icon.svg" isLanding="true">}}
     Infrastructure-as-a-Service (IaaS) version of NGINX Plus for your Microsoft Azure application stack.
   {{</card >}}
 {{</card-section>}}

content/includes/nginxaas-google/access-console.md

@@ -0,0 +1,6 @@
+---
+nd-docs: DOCS-000
+---
+
+- Visit [https://console.nginxaas.net/](https://console.nginxaas.net/) to access the NGINXaaS Console.
+- Log in to the console with your Google credentials.

content/includes/nginxaas-google/create-or-import-nginx-config.md

@@ -0,0 +1,24 @@
+---
+nd-docs: DOCS-000
+---
+
+In the NGINXaaS Console,
+
+1. On the left menu, select **Configurations**.
+1. Select **Add Configuration** to add a new NGINX configuration.
+1. You can either create a new configuration from scratch or copy an existing configuration:
+
+   - Select **New configuration** to create a new config.
+      - Provide a name for your configuration and an optional description.
+      - Change the configuration path if needed.
+      - Select to start with the "NGINXaaS Default" (a basic NGINX setup) or an empty configuration file.
+      - Select **Next**.
+   - Select **Copy existing configuration** to use one of the existing configuration files in your account as template.
+      - Provide a name for your configuration and an optional description.
+      - Change the configuration path if needed.
+      - Use the **Choose configuration to copy** list to select the configuration file you want to copy.
+      - Use the **Choose configuration version to copy** list to select the version of the configuration file you want to copy.
+      - Select **Next**.
+
+1. Modify the configuration file as needed and select **Save**.
+   - You can import certificates using the **Add file** option.

content/includes/nginxaas-google/logging-config-access-logs.md

@@ -0,0 +1,39 @@
+---
+nd-docs: DOCS-000
+---
+
+NGINX access logs are disabled by default. You can enable access logs by adding **access_log** directives to your NGINX configuration to specify the location of the logs and formats. The log path should always be configured to be inside **/var/log/nginx**.
+
+```nginx
+http {
+	log_format myfmt '$remote_addr - $remote_user [$time_local] '
+						   '"$request" $status $body_bytes_sent '
+						   '"$http_referer" "$http_user_agent" "$gzip_ratio"';
+
+	access_log /var/log/nginx/nginx-access.log myfmt;
+	# ...
+}
+```
+
+{{< call-out "note" >}} The **$time_local** variable includes the date and time for each log. It helps with ordering logs after export. {{< /call-out >}}
+
+To explicitly disable access logs, apply the following config:
+
+```nginx
+http {
+	access_log off;
+}
+```
+
+or
+
+```nginx
+http {
+	access_log /dev/null;
+}
+```
+
+To learn more about how to specify `access_log` in different configuration levels and their effect, see [access_log](https://nginx.org/en/docs/http/ngx_http_log_module.html#access_log)
+
+{{< call-out "warning" >}}Keep NGINX logs in the **/var/log/nginx** directory. Otherwise, you may lose data from your logs.
+{{< /call-out >}}

content/includes/nginxaas-google/logging-config-error-logs.md

@@ -0,0 +1,19 @@
+---
+nd-docs: DOCS-000
+---
+
+NGINX error logs are disabled by default. You can enable error logs by adding **error_log** directives to your NGINX configuration to specify the location of the logs and formats. The log path should always be configured to be inside **/var/log/nginx**.
+
+While you should configure log files in the **/var/log/nginx** directory, you can change the filename and severity level. For example, the following line in the NGINX configuration sends errors to the `nginx-error.log` file, and limits messages to a severity level of **emerg**:
+
+```nginx
+error_log /var/log/nginx/nginx-error.log emerg;
+```
+
+Alternatively, you can disable error logs completely with the following line:
+
+```nginx
+error_log /dev/null;
+```
+
+To learn more about how to specify `error_log` in different configuration levels, see the documentation of the [error_log](https://nginx.org/en/docs/ngx_core_module.html?#error_log) directive.

content/includes/nginxaas-google/ncu-description.md

@@ -0,0 +1,11 @@
+---
+nd-docs: "DOCS-1476"
+---
+
+An NGINX Capacity Unit (NCU) quantifies the capacity of an NGINX instance based on the underlying compute resources. This abstraction allows you to specify the desired capacity in NCUs without having to consider the regional hardware differences.
+
+An NGINX Capacity Unit consists of the following parameters:
+
+* CPU: an NCU provides 20 [Azure Compute Units](https://learn.microsoft.com/en-us/azure/virtual-machines/acu) (ACUs)
+* Bandwidth: an NCU provides 60 Mbps of network throughput
+* Concurrent connections: an NCU provides 400 concurrent connections. This performance is not guaranteed when NGINX App Protect WAF is used with NGINXaaS

content/includes/nginxaas-google/ssl-tls-prerequisites.md

@@ -0,0 +1,5 @@
+---
+nd-docs: DOCS-000
+---
+
+TBD SSL Prerequisites for NGINXaaS for Google Cloud

content/includes/nginxaas-google/terraform-prerequisites.md

@@ -0,0 +1,6 @@
+---
+nd-docs: DOCS-000
+---
+
+- Confirm that you meet the [NGINXaaS Prerequisites]({{< ref "/nginxaas-google/getting-started/prerequisites.md" >}}).
+

content/includes/nginxaas-google/terraform-resources.md

@@ -0,0 +1,5 @@
+---
+nd-docs: DOCS-000
+---
+
+TBD NGINXaaS for Google Cloud Terraform resources

content/includes/nginxaas-google/update-nginx-config.md

@@ -0,0 +1,14 @@
+---
+nd-docs: DOCS-000
+---
+
+1. On the left menu, select **Configurations**.
+1. On the list of configurations, select the ellipses (three dots) icon next to the configuration you want to update.
+1. Select **Edit**.
+1. Update the "Description" field as needed and select **Next**.
+1. Select the file you want to update in the file tree.
+   - Certificates can only be copied, moved, or renamed.
+1. Modify the configuration file(s) as needed and select **Next**.
+1. Review the changes using the "Inline" or "Side-by-side"  views and select **Save**.
+
+You will see a notification confirming that the configuration was updated successfully.

content/nginxaas-azure/_index.md

@@ -4,7 +4,7 @@ nd-subtitle: Infrastructure-as-a-Service (IaaS) version of NGINX Plus for your M
 url: /nginxaas/azure/
 nd-landing-page: true
 cascade:
-  logo: NGINX-for-Azure-icon.svg
+  logo: F5-NGINXaaS-icon.svg
 nd-content-type: landing-page
 nd-product: N4Azure
 ---

content/nginxaas-azure/get-help/support.md

@@ -14,25 +14,23 @@ To contact support about F5 NGINXaaS for Azure (NGINXaaS):
 
 1. Go to your NGINXaaS deployment.
 
-2. Select **New Support request** in the left menu.
+1. Select **New Support request** in the left menu.
 
-3. Select **Raise a Support ticket**.
+1. Select **Raise a Support ticket**.
 
    {{< img src="nginxaas-azure/raise-ticket.png" alt="Screenshot of the Azure portal showing the Raise support ticket button" >}}
 
-4. You will be redirected to **MyF5** to create a new case. Log in to MyF5 with your F5 account.
+1. You will be redirected to **MyF5** to create a new case. Log in to MyF5 with your F5 account.
 
 {{< call-out "note" >}}If you can't complete a deployment successfully, the "New support request" option won't be available on the left-hand navigation menu. To raise a support ticket, go to the [MyF5 portal](https://my.f5.com). {{< /call-out >}}
 
-5. Go to the **Case Management** section and select **Create new case**.
-
-   {{< img src="nginxaas-azure/new-case.png" alt="Screenshot of the MyF5 portal showing the Create new case button" >}}
+1. Go to the **Support** section and select **Create a Case**.
 
-6. Select **NGINXaaS** in the Product dropdown.
+1. Select **NGINX Products** as the product family.
 
-   {{< img src="nginxaas-azure/create-case.png" alt="MyF5 Case form" >}}
+1. Select **NGINXaaS for Azure** in the Product dropdown.
 
-7. Complete the request with the relevant information about your issue, bug report, or feedback. If you are contacting us to report an issue, please include the following information, available in the **Properties** section of your deployment, for the support team to begin their investigation:
+1. Complete the request with the relevant information about your issue, bug report, or feedback. If you are contacting us to report an issue, please include the following information, available in the **Properties** section of your deployment, for the support team to begin their investigation:
 
 - Location
 - Date and time of the issue
@@ -45,7 +43,7 @@ If your deployment is configured to use F5 WAF for NGINX, please collect the fol
 
 {{< img src="nginxaas-azure/properties.png" alt="Screenshot of the Azure portal showing the Properties section" >}}
 
-8. Complete the **Additional information** and **Contact details** sections of your case and select **Submit**.
+1. Complete the **Additional information** and **Contact details** sections of your case and select **Submit**.
 
 ## Update support contact information
 

content/nginxaas-azure/getting-started/create-deployment/deploy-azure-portal.md

@@ -109,7 +109,7 @@ You can start the NGINXaaS deployment process by visiting the [Create NGINXaaS](
 
 1. To test your deployment, you can go to the IP address noted on the overview page. The default NGINX welcome screen should load.
 
-   {{< call-out "note" >}}You will not see the default NGINX welcome screen if you unchecked "Apply default NGINX configuration" in the [Networking Tab screen]({{< ref "create-deployment.md#networking-tab" >}}) above. You can proceed with providing your own NGINX configuration as outlined in the [NGINX configuration]({{< ref "nginx-configuration.md#networking-tab" >}}) section.{{< /call-out >}}
+   {{< call-out "note" >}}You will not see the default NGINX welcome screen if you unchecked "Apply default NGINX configuration" in the [Networking Tab screen]({{< ref "/nginxaas-azure/getting-started/create-deployment.md#networking-tab" >}}) above. You can proceed with providing your own NGINX configuration as outlined in the [NGINX configuration]({{< ref "/nginxaas-azure/getting-started/nginx-configuration.md#networking-tab" >}}) section.{{< /call-out >}}
 
    {{< img src="nginxaas-azure/test-deployment.png" alt="NGINXaaS Overview page showing the IP address of the deployment in the Essentials section." >}}
 

content/nginxaas-azure/quickstart/njs-support.md

@@ -40,4 +40,4 @@ NGINXaaS will not parse, evaluate, or run any provided njs scripts when validati
 
 ## "fs" module
 
-The njs [File System module](http://nginx.org/en/docs/njs/reference.html#njs_api_fs) provides operations with files. NGINXaaS only allows reading and writing from [specified directories]({{< ref "nginx-configuration.md#nginx-process-restrictions" >}}).
+The njs [File System module](http://nginx.org/en/docs/njs/reference.html#njs_api_fs) provides operations with files. NGINXaaS only allows reading and writing from [specified directories]({{< ref "/nginxaas-azure/getting-started/nginx-configuration.md#nginx-process-restrictions" >}}).

content/nginxaas-azure/quickstart/security-controls/oidc.md

@@ -260,7 +260,7 @@ Configuring NGINXaaS for Azure with OIDC is similar as [Configuring NGINX Plus](
         }
         ```
 
-        b. Set a proper path for `proxy_cache_path`, see [Enable content caching]({{< ref "basic-caching.md" >}}).
+        b. Set a proper path for `proxy_cache_path`, see [Enable content caching]({{< ref "/nginxaas-azure/quickstart/basic-caching.md" >}}).
 
         ```nginx
         proxy_cache_path /var/cache/nginx/jwt levels=1 keys_zone=jwk:64k max_size=1m;

content/nginxaas-google/_index.md

@@ -0,0 +1,39 @@
+---
+title: F5 NGINXaaS for Google Cloud
+nd-subtitle: Managed NGINX service for your Google Cloud application stack
+url: /nginxaas/google/
+nd-landing-page: true
+cascade:
+  logo: F5-NGINXaaS-icon.svg
+nd-content-type: landing-page
+nd-product: N4GC
+---
+
+## About
+
+F5 NGINXaaS for Google Cloud is an IaaS offering that is tightly integrated
+into Google Cloud platform and its ecosystem, making applications fast, efficient,
+and reliable with full lifecycle management of advanced NGINX traffic services.
+
+## Featured content
+
+{{<card-section showAsCards="true" isFeaturedSection="true">}}
+  {{<card title="Prerequisites" titleUrl="/nginxaas/google/getting-started/prerequisites/" icon="power">}}
+    Follow these steps to prepare for your NGINXaaS deployment
+  {{</card>}}
+  {{<card title="Create a deployment" titleUrl="/nginxaas/google/getting-started/create-deployment/deploy-console/" icon="cloud-upload">}}
+    Step-by-step instructions to deploy NGINXaaS using the NGINXaaS Console
+  {{</card>}}
+  {{<card title="Add certificates" titleUrl="/nginxaas/google/getting-started/ssl-tls-certificates/ssl-tls-certificates-console/" icon="lock">}}
+    Instructions to add SSL/TLS certificates to your NGINXaaS deployment using the NGINXaaS Console
+  {{</card>}}
+{{</card-section>}}
+
+### Get help
+
+
+{{<card-section showAsCards="true" >}}
+  {{<card title="Get help" titleUrl="/nginxaas/google/get-help/" icon="wallet">}}
+    Get in touch with the NGINX support team for assistance
+  {{</card>}}
+{{</card-section>}}

content/nginxaas-google/billing/_index.md

@@ -0,0 +1,6 @@
+---
+title: Marketplace billing
+weight: 400
+url: /nginxaas/google/billing/
+draft: false
+---

content/nginxaas-google/billing/overview.md

@@ -0,0 +1,55 @@
+---
+title: Billing overview
+weight: 100
+toc: true
+nd-docs: DOCS-000
+url: /nginxaas/google/billing/overview/
+type:
+- concept
+---
+
+F5 NGINXaaS for Google Cloud is deployed into your Google Cloud subscription, where your deployment resource is visible and integrated with Google Cloud’s ecosystem. The underlying infrastructure, software maintenance, availability, and scaling are fully managed by F5, abstracting operational complexities. Billing occurs hourly and is tracked in the Google Cloud Cost Management Dashboard.
+
+## Pricing plans
+
+F5 NGINXaaS for Google Cloud is offered on an Enterprise plan, delivering enterprise-grade performance, scalability, and security backed by a 99.95% uptime SLA. The pricing model consists of three billing components, ensuring transparent and predictable costs based on resource usage.
+
+### Pricing components
+{{< table >}}
+
+| Component                   | Cost                          |
+|---------------------------- | ----------------------------- |
+| Fixed price                 | $0.10 per hour                |
+| NGINX Capacity Units (NCU)  | $0.008 per NCU per hour       |
+| Data processing             | $0.0096 per GB processed      |
+
+{{< /table >}}
+
+## NGINX Capacity Unit (NCU)
+
+An NGINX Capacity Unit (NCU) quantifies the capacity for a deployment. Resources are metered hourly based on the capacity utilized, enabling customers to scale up or down dynamically. The minimum billing interval is 5 min, ensuring accurate alignment of cost and usage. A single NCU consists of:
+
+   - Bandwidth – 2.2 Mbps
+   - Connections – 3000
+
+## Billing examples
+
+### Deployment with 20 NCUs processing 100 GB of data for 1 hour
+
+- Fixed price: $0.10/hour
+- NCU usage: 20 NCUs * $0.008/hour = $0.16/hour
+- Data processing: 100 GB * $0.0096/GB = $0.96
+
+**Total cost for 1 hour: $0.10 + $0.16 + $0.96 = $1.22**
+
+### Deployment using 30 NCUs for 2 hours and scaled to 50 NCUs for another hour, processing 200 GB of data
+
+- Fixed price: $0.10/hour * 3 hours = $0.30
+- NCU usage: (30 NCUs * $0.008/hour * 2 hours) + (50 NCUs * $0.008/hour * 1 hour) = $0.88
+- Data processing: 200 GB * $0.0096/GB = $1.92
+
+**Total cost for 3 hours: $0.30 + $0.88 + $1.92 = $3.10**
+
+## Review billing data
+
+Billing data for F5 NGINXaaS for Google Cloud is reported per deployment and can be accessed through the Google Cloud Cost Management Dashboard. Usage metrics and costs are updated hourly, allowing customers to monitor and optimize resource allocation effectively.